astro-sites-manager

# Astro Framework — v7 ## MCP Documentation Access This skill works alongside the **Astro Docs MCP server**. Before answering Astro questions, check if the `astro-docs` MCP tool is available and query it for the latest documentation. The MCP server provides real-time access to docs.astro.build and is the single source of truth for current APIs. ``` MCP Server: astro-docs Tool: search_astro_docs ``` If the MCP server is unavailable, fall back to the reference material in this skill and https://docs.astro.build. --- ## Best Practices ### Component Design - One `.astro` component per file. Keep components small and focused. - Use frontmatter (`---`) for data fetching and logic; template below for markup only. - Prefer Astro components over framework components unless client interactivity is needed. - Use `client:*` directives sparingly — each adds JavaScript to the bundle. - Directive hierarchy: `client:idle` > `client:visible` > `client:load` (prefer lazy). ### Routing & Pages - Use file-based routing in `src/pages/`. Dynamic routes: `[slug].astro`, `[...path].astro`. - Always export `getStaticPaths()` for prerendered dynamic routes. - For SSR pages: `export const prerender = false` at the top. - Use `src/fetch.ts` (v7) only when you need control beyond middleware — don't use it for simple auth. ### Content Collections - Define schemas in `content.config.ts` with Zod — never trust untyped content. - Use `getCollection()` for lists, `getEntry()` for single items. - Pref...