How do I install the Astro 6 skill?

Run npx skillmds@latest add aibot88/astro-6 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Astro 6 safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Astro 6?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Astro 6 free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Astro 6?

aibot88 (@aibot88) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Astro 6 by aibot88 — Agent Skill

Name: Astro 6
Rating: 4.2 (5 reviews)
Author: aibot88

Astro 6

Expert Astro 6 framework — routing, output modes, middleware, Vite Environment API, Rust compiler, Content Security Policy, Live Collections, Fonts API. Use when building Astro sites, configuring output, or upgrading from Astro 5.

aibot88 Updated Sep 9, 2026 3 repo stars

File contents

Astro 6 Expert

Production-ready web framework for content-driven sites with unified dev runtime and Islands Architecture.

Agent Workflow (MANDATORY)

Before ANY implementation, use TeamCreate to spawn 3 agents:

fuse-ai-pilot:explore-codebase - Analyze existing routes, layouts, and config
fuse-ai-pilot:research-expert - Verify latest Astro 6 docs via Context7/Exa
mcp__context7__query-docs - Check breaking changes v5→v6

After implementation, run fuse-ai-pilot:sniper for validation.

Overview

When to Use

Building new content-driven websites or blogs
Migrating from Astro 5 to version 6
Configuring static, server, or hybrid output modes
Setting up middleware for auth or redirects
Leveraging the new Rust compiler for large sites
Implementing Content Security Policy (CSP) headers

Why Astro 6

Feature	Benefit
Unified Dev Runtime	Dev matches production — fewer "works in dev, breaks in prod" bugs
Vite Environment API	Exact production runtime during development
Rust Compiler	Faster `.astro` file compilation, replaces Go compiler
Live Content Collections	Real-time data from external sources
Built-in Fonts API	Zero-config font loading with performance optimization
CSP Support	Built-in Content Security Policy nonce management
Cloudflare Workers	First-class support with workerd runtime in dev

Core Concepts

Output Modes

Mode	Description	Use Case
`static` (default)	All pages prerendered at build	Blogs, docs, marketing
`server`	All pages rendered on demand	Apps, dashboards, auth
`hybrid`	Mix static + on-demand	Most production sites

Routing

File-based routing — src/pages/ maps directly to URLs
Dynamic routes — [slug].astro, [...all].astro
Per-route prerender — export const prerender = false/true
Endpoints — .ts/.js files in src/pages/ for API routes

Reference Guide

Need	Reference
Initial setup	installation.md
Routing patterns	routing.md
Output configuration	output-modes.md
Middleware setup	middleware.md
astro.config.ts	config.md
New Astro 6 features	new-features.md
Full project setup	templates/basic-setup.md
Config examples	templates/config-example.md

Best Practices

Use output: 'static' by default — Add server only when needed
Per-route prerender — Fine-grained control in hybrid mode
Middleware for cross-cutting concerns — Auth, redirects, headers
Opt into Rust compiler — Faster builds on large sites
CSP nonces — Use built-in support instead of custom headers

---name: astro-6description: Expert Astro 6 framework — routing, output modes, middleware, Vite Environment API, Rust compiler, Content Security Policy, Live Collections, Fonts API. Use when building Astro sites, configuring output, or upgrading from Astro 5.--- # Astro 6 Expert Production-ready web framework for content-driven sites with unified dev runtime and Islands Architecture. ## Agent Workflow (MANDATORY) Before ANY implementation, use `TeamCreate` to spawn 3 agents: 1. **fuse-ai-pilot:explore-codebase** - Analyze existing routes, layouts, and config 2. **fuse-ai-pilot:research-expert** - Verify latest Astro 6 docs via Context7/Exa 3. **mcp__context7__query-docs** - Check breaking changes v5→v6 After implementation, run **fuse-ai-pilot:sniper** for validation. --- ## Overview ### When to Use - Building new content-driven websites or blogs - Migrating from Astro 5 to version 6 - Configuring static, server, or hybrid output modes - Setting up middleware for auth or redirects - Leveraging the new Rust compiler for large sites - Implementing Content Security Policy (CSP) headers ### Why Astro 6 | Feature | Benefit | |---------|---------| | Unified Dev Runtime | Dev matches production — fewer "works in dev, breaks in prod" bugs | | Vite Environment API | Exact production runtime during development | | Rust Compiler | Faster `.astro` file compilation, replaces Go compiler | | Live Content Collections | Real-time data from external sources | | Built-in Fonts API | Zero-config font loading with performance optimization | | CSP Support | Built-in Content Security Policy nonce management | | Cloudflare Workers | First-class support with workerd runtime in dev | --- ## Core Concepts ### Output Modes | Mode | Description | Use Case | |------|-------------|----------| | `static` (default) | All pages prerendered at build | Blogs, docs, marketing | | `server` | All pages rendered on demand | Apps, dashboards, auth | | `hybrid` | Mix static + on-demand | Most production sites | ### Routing - **File-based routing** — `src/pages/` maps directly to URLs - **Dynamic routes** — `[slug].astro`, `[...all].astro` - **Per-route prerender** — `export const prerender = false/true` - **Endpoints** — `.ts`/`.js` files in `src/pages/` for API routes --- ## Reference Guide | Need | Reference | |------|-----------| | Initial setup | [installation.md](references/installation.md) | | Routing patterns | [routing.md](references/routing.md) | | Output configuration | [output-modes.md](references/output-modes.md) | | Middleware setup | [middleware.md](references/middleware.md) | | astro.config.ts | [config.md](references/config.md) | | New Astro 6 features | [new-features.md](references/new-features.md) | | Full project setup | [templates/basic-setup.md](references/templates/basic-setup.md) | | Config examples | [templates/config-example.md](references/templates/config-example.md) | --- ## Best Practices 1. **Use `output: 'static'` by default** — Add server only when needed 2. **Per-route `prerender`** — Fine-grained control in hybrid mode 3. **Middleware for cross-cutting concerns** — Auth, redirects, headers 4. **Opt into Rust compiler** — Faster builds on large sites 5. **CSP nonces** — Use built-in support instead of custom headers

Frequently asked questions