What problem does it solve? When modifying the sbuilder-mcp server's store tooling, hard-won platform facts (checkout ordering, fixed page paths, form templates, category scoping, layout patterns) are easy to re-derive wrongly or accidentally "fix". This Skill preserves those verified behaviors so changes to the store flows do not regress them. ## Core Features & Use Cases - Checkout and form flow reference: Explains the four ordered writes behind sb_store checkout and the seventeen form templates reachable via sb_store action form. - Page seed and fixed-path knowledge: Covers the six store page seeds applied by sb_page_create, the four fixed paths resolving by page type, and /account sign-in behavior. - Layout pattern guidance: Details LAYOUT_PATTERNS, sb_template_use, media search rules, and render-only defects (measure, grid wrapping, type scale, alignment) that tree checks miss. - Use Case: When editing src/tools/store.ts or src/domains/site/patterns.ts, load this Skill to learn why category templates scope to the URL's collection and why global chrome must be read off the home page before changing the code. ## Quick Start Load the sbuilder-store-flows skill before modifying the checkout, chrome, overlay, or pattern code so the documented platform behaviors are preserved.
