Prototype

A prototype is throwaway code that answers a question. The question decides the shape.

Route the question

Identify which question is being answered — from the user's prompt, the surrounding code, or by asking if the user is around:

• "Does this logic / state model feel right?" → LOGIC.md. Build a single shareable HTML file — free-play buttons plus tabbed guided walkthroughs — that pushes the state machine through cases that are hard to reason about on paper, and that a non-developer can drive.
• "What should this look like?" → invoke /frontend-design. It owns the richer visual workflow: prerequisite gating, three runnable directions, screenshots, user grilling, and an approved docs/design/<feature>/DESIGN.md contract. If its product prerequisites are unresolved, route them back to /wayfinder or /grilling; do not build UI variants here.

These are two destinations, not two prototype branches: this skill builds only logic/state prototypes, while /frontend-design owns visual exploration. If the question is genuinely ambiguous and the user is not reachable, build a logic prototype only when the prompt clearly asks about state or behavior. Otherwise stop and route the missing decision through /wayfinder or /grilling; never resurrect a local UI-prototype path.

Rules for logic prototypes