prototype

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

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/kashman001/ai-workspace-template --skill prototype-kashman001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/kashman001/ai-workspace-template/tree/main/skills/prototype
Command: npx skills add https://github.com/kashman001/ai-workspace-template --skill prototype-kashman001

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: Build a single self-contained HTML file with a pure reducer, state machine, or function module, free-play action buttons, and tabbed guided walkthroughs that a non-developer can drive by double-clicking. - UI Prototypes: Generate 3-5 radically different UI variants on an existing route (or a throwaway route), switchable via a ?variant= URL param and a floating bottom bar with arrow-key cycling. - Capture Workflow: Fold validated decisions into real code while committing the full prototype to a throwaway branch as a primary source, keeping main clean. - Use Case: Before implementing a checkout state machine, hand a PM a single HTML file with scenario walkthroughs covering the happy path, edge cases, and illegal transitions, then lift the validated reducer into the real module. ## Quick Start Ask the agent to prototype whether your state model handles a tricky edge case, or to generate three different layout variants for a page you are unsure about.

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?▼

Build a single self-contained HTML file with the logic isolated as a pure reducer or state machine module, plus free-play action buttons and guided scenario walkthroughs. Anyone can open it by double-clicking, and the validated module lifts directly into the real codebase afterward.

How to compare multiple UI design variants in one app?▼

Render 3-5 structurally different variants on the same route, gated by a ?variant= URL search param, with a floating bottom bar for switching. Keep existing data fetching intact so variants are judged against real content, then fold the winner into the page.

Should a prototype use a framework like React or plain HTML?▼

Logic prototypes should be one plain HTML file with no framework, bundler, or server so they survive being emailed and double-clicked. UI prototypes follow the host project's existing framework and component library since they live on real routes.

When should I not write a throwaway prototype?▼

Skip prototyping when the question is already answered or when you start adding tests, error handling, persistence, or abstractions. A prototype that needs tests is no longer a prototype; it answers exactly one question and is then captured on a throwaway branch.

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

The validated decision, such as a reducer or winning variant, is folded into the real code, while the full prototype is committed to a throwaway branch as a primary source. The main branch keeps only the validated decision, never the prototype shell.