What problem does it solve? It enforces consistent Astro architecture in the CITEC frontend so routes, layouts, and page-owned components follow project conventions instead of drifting into duplicated shells, accidental public routes, or misplaced components. ## Core Features & Use Cases - Route and layout conventions: Keeps src/pages thin, centralizes metadata and shell logic in BaseLayout, and preserves trailing-slash and sitemap-friendly link behavior. - Component organization: Places page-owned components under src/page-modules/<page>/components and reserves React islands for stateful or browser-dependent UI. - Static-friendly dynamic routes: Uses typed getStaticPaths and typed Astro.props with data from src/data or integration adapters. - Use Case: When adding a new institutional page such as an eventos or directorio section, apply this skill to compose the route from existing sections, wire BaseLayout props correctly, and validate with bun run check and bun run build. ## Quick Start Use the citec-astro-routing skill to create a new Astro route for the CITEC agenda section with proper layout props and page-owned components.
