What problem does it solve? When an Astro page builder section grows beyond a single file, developers must decide where companion files (client-side components, server actions, data, helpers) belong without breaking the project's conventions or the Sanity schema registry. ## Core Features & Use Cases - Scoped vs shared decision rule: Applies a reuse test to decide whether a file is colocated in the section folder or placed in the shared src/components/ library. - Folder promotion convention: Promotes a flat {Name}Section.astro file into a sections/{Name}Section/ folder with no index.astro and no barrel files. - Import and registry maintenance: Re-bases relative imports one level deeper and updates the PageSections.astro registry path while leaving schema names untouched. - Use Case: You add a custom element to a contact form section; the skill moves ContactFormSection.astro into its own folder, colocates ContactFormElement.ts beside it, and updates the registry import. ## Quick Start Ask the assistant to colocate a new client-side component with an existing page builder section and update the registry import accordingly.
