solid-astro

<objective> Enforces SOLID and DRY architecture on Astro projects: files under 100 lines (split at 90), all TypeScript types moved to `src/interfaces/` (never in component files), mandatory JSDoc on exported functions, no business logic in `src/pages/`, and mandatory grepping for existing logic/utilities in `src/lib/` and `src/components/` before writing new code. Provides ready-to-copy templates for components, layouts, services, and interfaces that already follow these rules. This is a cross-cutting code-quality skill, not a feature skill — it doesn't teach Astro APIs themselves (see astro-7, astro-content, astro-i18n, astro-styling for that), only how to structure the code that uses them. </objective> # SOLID Astro — Modular Architecture ## Agent Workflow (MANDATORY) Before ANY implementation, spawn 3 agents in parallel, one `Agent` call each with a `name`: 1. **fuse-ai-pilot:explore-codebase** - Analyze project structure, naming, and existing patterns 2. **fuse-ai-pilot:research-expert** - Verify Astro 7 architecture best practices via Context7/Exa 3. **mcp__context7__query-docs** - Check Astro component API and TypeScript integration After implementation, run **fuse-ai-pilot:sniper** for validation. --- ## Codebase Analysis (MANDATORY) Before ANY implementation: 1. Explore `src/` directory to understand existing architecture 2. Read existing similar files to follow established naming and patterns 3. Grep for similar function/component names before creating new ...