What problem does it solve?
Product UI builds often start from vague requests, leading to wasted work on the wrong product, wrong visual style, or wrong level of interactivity. This Skill acts as a mandatory design-brief gate that clarifies or confirms the product, visual source, and interactivity expectations before any ideation, prototyping, or image-to-code work begins.
Core Features & Use Cases
- Question Mode: Asks targeted questions about what the product should do, which visual source (Figma, screenshot, URL, design system) it should match, and the expected interactivity level when details are missing.
- Playback Mode: Summarizes an already-supplied brief in a pithy format without re-asking answered questions, then names the next workflow.
- Hard Boundary Enforcement: Blocks UI implementation, scaffolding, server startup, and file creation until the user confirms the design brief.
- Use Case: A user asks to redesign a login page. The Skill asks about authentication methods, existing design systems to match, and whether full form states or a static mock are needed, then plays back the confirmed brief before handing off to ideation or prototyping.
Quick Start
Ask the agent to design or prototype a product UI screen, and it will first run this context-gathering step to confirm the design brief with you before building.