Prototype picks a branch from the question. “Does this logic or state model feel right” leads to LOGIC.md, a single HTML file with free-play buttons and tabbed guided walkthroughs that a non-developer can drive. “What should this look like” leads to UI.md, several radically different variations on one route switched with a URL search param and a floating bottom bar.
If the question is ambiguous and you are away, it picks the branch that matches the surrounding code and states the assumption.
What You Get
- A single self-contained HTML file with the logic in a pure, portable module
- Three UI variants by default, five at most, behind a ?variant= param with arrow-key switching
- The full relevant state shown after every action or variant switch
- A prototype branch kept as a primary source and the verdict recorded in the issue or a commit
Common Use Cases
- Checking whether a state machine handles an awkward edge case before writing it for real
- Comparing three layouts of a settings page against real data
- Handing a non-developer a demo they can click through to challenge a data model
What Makes It Unique
The shape of the artifact follows the question. The logic demo is written in domain language for people outside engineering. The UI variants must be structurally different, and the skill prefers hosting them inside an existing page so they sit among real data. Main keeps only the validated decision.
Under The Hood
SKILL.md is Markdown that routes to LOGIC.md or UI.md. It bundles no scripts. The model creates prototype files in your project, adds a run command to your task runner for UI prototypes, writes one HTML file for logic prototypes, and commits the prototype to a throwaway branch.