What problem does it solve? Astro projects built with a feature-slice architecture (paired src/features/ and src/content/ folders, Content Collections, no UI framework) drift into inconsistency when contributors write generic Astro code instead of matching the project's established patterns. This Skill ensures generated or reviewed code follows the project's actual conventions for pages, components, schemas, queries, styling, and interactivity. ## Core Features & Use Cases - Architecture enforcement: Keeps src/pages/ files as thin wrappers around features/ Page components, routes all data access through per-feature queries.ts files, and applies the folder-vs-singleton Content Collection pattern correctly. - Styling and interactivity conventions: Applies scoped BEM CSS with design tokens, :global() usage rules, and vanilla-JS-only interactivity (no client:* directives, no React/Vue/Svelte). - Use Case: When asked to add a blog detail page to an Astro site, the Skill produces a thin src/pages/blog/[slug].astro with getStaticPaths sourcing from blog.queries.ts, rendering a BlogDetailPage.astro that slots the Markdown Content — matching sibling files exactly. ## Quick Start Use the astro-webapp-conventions skill to add a new content-backed feature page to this Astro project following its existing folder and naming patterns.