prototype

Builds throwaway logic TUIs or UI variants to answer design questions.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/vinzenz/workflows --skill prototype-vinzenz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/vinzenz/workflows/tree/main/.agents/skills/prototype
Command: npx skills add https://github.com/vinzenz/workflows --skill prototype-vinzenz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Some design questions cannot be settled by discussion — you have to see or feel the answer. This Skill guides the creation of throwaway prototypes that answer a single stated question, whether that is validating a state model through an interactive terminal app or comparing radically different UI variants with a human reviewer. ## Core Features & Use Cases - Logic prototypes: Build a clear-and-redraw terminal UI over a pure, portable logic module (reducer, state machine, or function set) so a human can press keys and watch state change. - UI prototypes: Generate 3-5 structurally different UI variants reviewed through a galley HTML artifact with a blocking human-in-the-loop gate, or via an in-app route with a variant switcher. - Capture workflow: Keep scaffolding off main on a prototype/<slug> branch, record the verdict in the commit message or originating ticket, and fold only the validated decision into real code. - Use Case: When unsure whether a state machine handles an edge case, state the question, build a minimal TUI over a pure reducer, let the human drive it, then lift the validated module into production code. ## Quick Start Ask the agent to prototype whether your proposed state model handles a specific edge case, stating the question you want answered.

Frequently Asked Questions about prototype

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prototype a state machine before writing production code?▼

State the question in one paragraph, isolate the logic in a pure module such as a reducer or state machine, then build a minimal clear-and-redraw terminal UI that dispatches keystrokes to it. The human drives it to find edge cases, and the validated module lifts into the real codebase.

How do I compare multiple UI design variants with a human reviewer?▼

Create 3 to 5 structurally different variants in a single HTML artifact and open it with galley, which provides a blocking human-in-the-loop review gate. Alternatively, render variants on an in-app route behind a URL parameter with a floating switcher bar.

When should I not build a prototype?▼

Skip prototyping when the decision is already clear, when building the real thing behind a flag is cheaper, or when the question concerns scale or performance rather than shape. Prototypes answer questions about shape and feel, not speed.

Should prototype code include tests and error handling?▼

No. A prototype that needs tests is no longer a prototype. Skip tests, persistence, and polish; keep state in memory and focus only on answering the stated question quickly.

What happens to prototype code after the question is answered?▼

The scaffolding stays on a throwaway branch named prototype/<slug> and never merges to main. Only the validated decision is folded into real code, with the branch serving as the primary source record.