What problem does it solve? Astro projects require repeated architectural decisions about hydration directives, content schema design, rendering modes, and deployment adapters, and wrong choices lead to bloated JavaScript bundles, broken type safety, or mismatched hosting setups. ## Core Features & Use Cases - Islands Architecture Guidance: Decision flowchart for choosing between client:load, client:idle, client:visible, client:media, and client:only hydration directives based on UX priority. - Content Collection Patterns: Schema-first design with Zod validation, discriminated unions, cross-collection references, and type-safe querying with getCollection and getEntry. - Rendering & Deployment Selection: Decision matrices for static, hybrid, and server rendering modes plus adapter selection for Vercel, Netlify, Cloudflare, and Node.js. - Use Case: When building a blog with an interactive comment section, use this Skill to decide that the comments should use client:idle, define a Zod schema with draft filtering, and deploy statically to Cloudflare without an adapter. ## Quick Start Ask the AI to read the astro-development skill and recommend the right hydration directive and rendering mode for your Astro page.