What problem does it solve? When a design kit only covers part of a product page, agents are forced to either fake missing components or produce rigid, low-quality layouts. This Skill defines a structured way to build expressive, runnable prototypes that mix stable kit components with base UI primitives and clearly marked exploratory modules, without polluting the design system. ## Core Features & Use Cases - Three constraint modes: Kit Strict for production pages with full component coverage, Hybrid Prototype as the default for most feature prototypes, and Exploratory for concept work with three genuinely different directions. - Source tagging and governance: Every visible layer is labeled as kit, primitive, or prototype, so exploratory modules never masquerade as kit components or inflate component coverage statistics. - Feedback loop into the design system: Prototype modules that repeat across two or more prototypes with stable requirements can enter the draft → review → stable component lifecycle. - Use Case: A designer asks for a profile page concept, but the kit only covers navigation, search, lists, and buttons. The Skill anchors the page with those stable components, fills gaps with Stack/Text/Surface primitives, adds a Prototype profile-hero module, and records kit gaps in the manifest for later componentization. ## Quick Start Ask the agent to build a hybrid prototype of a profile page using the TopTop kit, marking which parts come from stable components and which are exploratory prototype modules.
