What problem does it solve? Building a storefront with the sb_* tools involves dozens of silent failure modes — wrong build order, responsive cascade leaks, unstyled satellites, broken purchase bindings — that only surface when a real shopper hits the site. This Skill encodes the ordered build recipe and the nine design rules learned from actual shipped defects, so an agent produces a store that can take money rather than a generated-looking mockup. ## Core Features & Use Cases - Ordered build recipe: Connect, catalogue before pages, media, delivery before payment, checkout via the editor's four-step flow, pages by type, publish, then verify — each step justified by the rebuild it prevents. - Design source integration: Reads tokens from Figma MCP or Google Stitch MCP design systems before inventing anything, and defines which MCP server (sb_look, Chrome DevTools, Playwright) answers which verification question. - Nine design rules: Covers the responsive cascade tail, satellite styling, form field-skin config keys, sticky header preconditions, aspect-ratio matching, and the surfaces (cart drawer, empty states) that ship platform defaults. - Use Case: An agent tasked with porting a Figma design onto a Store Builder site reads the tokens from Figma, builds pages by type with sb_page_create seeds, styles satellites and the cart drawer to match, then verifies at 1440/768/390 widths and submits a sandbox checkout with Playwright. ## Quick Start Ask the agent to build a storefront for your Store Builder site following the sbuilder-site-design recipe, starting from your Figma file or a written token set.
