prototype

Build throwaway HTML demos and UI variants to answer design questions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design questions about state models, business logic, or UI layouts are hard to settle on paper. This Skill produces throwaway prototypes that let you and stakeholders press buttons, flip between variants, and feel whether a model or layout actually works before committing to real code. ## Core Features & Use Cases - Logic prototypes: Generate a single self-contained HTML file with a pure reducer or state machine, free-play action buttons, and tabbed guided walkthroughs that a non-developer can drive by double-clicking. - UI prototypes: Generate 3-5 structurally different variants of a page on an existing route, switchable via a ?variant= URL param and a floating bottom bar with arrow-key navigation. - Capture workflow: Fold validated decisions into real code and preserve the prototype on a throwaway branch as a primary source. - Use Case: You are unsure whether a state machine handles an edge case. The Skill builds a shareable HTML demo where a PM clicks through scenarios and discovers the illegal transition themselves. ## Quick Start Ask the AI to prototype whether your state machine handles the edge case where a user cancels mid-checkout, as a shareable HTML demo.

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 without writing production code?▼

Build a single self-contained HTML file with the state machine as a pure module, free-play buttons for each action, and tabbed guided walkthroughs for edge cases. Anyone can open it by double-clicking, with no framework, bundler, or server required.

How to compare multiple UI layout options for one page?▼

Render 3-5 structurally different variants on the same route, gated by a ?variant= URL search param, with a floating bottom bar to cycle between them. Variants must differ in layout and information hierarchy, not just colors or copy.

Should a prototype use the real database or in-memory state?▼

Prototypes should use in-memory state by default, since persistence is usually the thing being checked, not a dependency. Only hit a scratch database or clearly marked local file when the question explicitly involves persistence.

When should I not build a throwaway prototype?▼

Skip prototyping when the question is already answered or when you would add tests, error handling, or abstractions, since those signal production work. A prototype answers one question fast and is never promoted directly to production.

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

Fold the validated decision into the real code, then commit the full prototype to a throwaway branch as a primary source with a pointer on the implementation issue. The main branch keeps only the validated decision, not the prototype shell.