prototype

combined

Build multiple genuinely different versions of a UI piece you describe, rendered behind a visual picker so you can flip through them live and promote the one that feels right. Only runs when explicitly invoked; it does not trigger on its own. Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

When to use

Use when this workflow matches the user request: Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. _Sourc…

When not to use

Requires the upstream tool, account, API key, or local setup when the workflow names one.
Does not authorize destructive, production, paid, or external-message actions without explicit user approval.
Validate generated artifacts or recommendations against the user's real sources before treating them as final.

Skill page

Conflict

The copies overlap on the core idea of building throwaway prototypes, but they disagree on the artifact type and the process. mattpocock/skills and sickn33/agentic-awesome-skills (a mirror of mattpocock) define a two-branch skill (Logic vs UI) with specific rules for throwaway code. emilkowalski/skills defines a single-branch skill focused exclusively on UI divergence with a specific 'picker' harness and design engineering constraints. plugin87/ux-ui-agent-skills defines a completely different process: a 5-level fidelity ladder (content-first to code) with validation plans. Because the mattpocock version and the emilkowalski version offer mutually exclusive approaches to the 'UI' branch (single HTML file vs. multi-variant picker), and the plugin87 version offers a different fidelity-based approach, crowning one would hide real alternatives.