What problem does it solve?
It prevents slow, inaccessible, non-localized Astro lead generation sites by enforcing a high-performance, translation-ready architecture with strict boundaries between concerns.
Core Features & Use Cases
- Astro architecture guardrails: Keeps the project static/hybrid, avoids SPA routing, and bans UI component libraries, client-heavy patterns, and risky inline business logic.
- TypeScript strict, single source of truth: Requires TypeScript strict mode (no
any) and centralizes all site data in src/config/site.ts.
- End-to-end performance and quality targets: Enforces PageSpeed (mobile/desktop), load time, LCP, CLS, and “no JS required for page render” expectations suitable for marketing/lead-gen performance.
- Localization-first content: Requires all visible text to come from i18n dictionaries and supports multi-language page patterns with hreflang where applicable.
- Skill-based separation of responsibilities: Routes images, SEO, and forms through dedicated companion skills (astro-images, astro-seo, astro-forms) to reduce drift and inconsistencies.
Quick Start
Use this skill to design and validate a new Astro lead-gen site architecture for mobile-first performance with strict TypeScript and i18n-compliant pages.