What problem does it solve? When building or modifying page builder sections in an Astro + Sanity project, developers often make inconsistent decisions about which HTML tag a section renders, how its width is controlled, and where shared layout switches live. This Skill enforces a single set of rules so every section owns its outer shape, renders SectionFrame as its root, and keeps PageSections.astro as a bare registry. ## Core Features & Use Cases - Tag selection rules: Decide between section, div, or figure based on whether the section carries its own heading in the document outline. - Shared layout switches: Add a new editor-facing switch (like Full Bleed) in exactly three places—schema fields, the SECTION_SETTINGS GROQ slice, and the sectionLayout() handler—never per-section. - Registry discipline: Keep PageSections.astro as a pure type-to-component map with no wrappers, tag maps, or conditional logic. - Use Case: You are adding a new testimonials section and need to decide its root tag, wire its width to the Sanity editor's Full Bleed toggle, and register it without polluting the shared registry. ## Quick Start Ask the assistant to apply the section-anatomy rules when creating or modifying a page builder section so it renders SectionFrame with the correct tag and settings.
