Frontend Astro Architecture

Use when the user asks about Astro, building a content site with Astro islands, .astro files, content collections, file-based routing, static vs server output or Astro adapters. Produces a zero-JS-by-default Astro project structure with typed content and deployment config. Not for client:* tuning, view transitions or integrations (use frontend-astro-patterns).

45 stars 6 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill frontend-astro-architecture
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/frontend/astro/architecture ~/.claude/skills/frontend-astro-architecture

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Astro Architecture

## Purpose
Build content-focused websites with Astro's zero-JS-by-default approach. Use islands for interactive parts, content collections for type-safe markdown, and adapters for deployment flexibility.

## Agent Protocol

### Trigger
Exact user phrases: "Astro", "Astro architecture", "Astro islands", "Astro component", "Astro page", "Astro content collection", "Astro SSG", "Astro SSR", ".astro file".

### Input Context
Before activating, verify:
- package.json has astro dependency.
- Whether the project uses SSG, SSR, or hybrid mode.
- Which framework integrations (React, Vue, Svelte, Solid) are configured.
- Content collection structure in src/content/.

### Output Artifact
No file output. Produces component patterns, island strategies, content collection schemas, and deployment config as text.

### Response Format
Component code: .astro file template. Island patterns: client directive usage. Content: Zod schema + query.

No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output — why use many token when few do trick.

### Completion Criteria
- [ ] Pages are .astro files with frontmatter separated by ---.
- [ ] Interactive components use client:* directives (load, idle, visible, media, only).
- [ ] Content collections have Zod schemas in src/content/config.ts.
- [ ] Images optimized via astro:assets Image/Picture components.
- [ ] Adapter configured for target deployment (node/deno/cloudflare/netlify).
Read the full skill on GitHub

Details

Skill name
frontend-astro-architecture
Path
skills/frontend/astro/architecture/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Frontend Astro Architecture skill do?

Use when the user asks about Astro, building a content site with Astro islands, .astro files, content collections, file-based routing, static vs server output or Astro adapters. Produces a zero-JS-by-default Astro project structure with typed content and deployment config. Not for client:* tuning, view transitions or integrations (use frontend-astro-patterns).

How do I install the Frontend Astro Architecture skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill frontend-astro-architecture. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Frontend Astro Architecture popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Frontend Qwik Architecture

45

j4flmao/agent-skills

Use when the user asks about Qwik, resumability vs hydration, Qwik City (Qwik Router in v2), the $ lazy boundary, Qwik project structure or Qwik vs React. Produces a Qwik app layout with routing, loaders/actions and bundle-splitting rules. Not for useSignal/useStore or prefetch tuning in an existing app (use frontend-qwik-patterns).

Software Development

Flask Backend

45

j4flmao/agent-skills

Use when the user asks about Flask, Flask application factory, blueprints, Flask extensions (init_app), Flask-SQLAlchemy, Alembic migrations or Flask testing. Produces modular Flask apps. Not for FastAPI (use python-fastapi-architecture) or Django (use python-django-architecture).

Software Development

Frontend Remix Architecture

45

j4flmao/agent-skills

Use when the user asks about Remix v2 or React Router v7 framework mode, Remix loaders and actions, nested routes with Outlet, sessions, Remix Vite setup, deployment adapters or upgrading Remix to React Router v7. Produces route structure, loader/action code and runtime config. Not for validation, optimistic UI or caching (use frontend-remix-patterns).

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.