prototype

Build throwaway HTML or UI prototypes to validate state models and interface designs.

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill prototype-cloudofgeorge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/cloudofgeorge/AI-hands-Engineer/tree/main/skills/engineering/prototype
Command: npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill prototype-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design questions about state machines, data models, or UI layouts are hard to settle on paper. This Skill produces throwaway, runnable 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 free-play action buttons and tabbed guided walkthroughs that drive a pure reducer, state machine, or function set through edge cases — shareable with non-developers by double-click. - UI Prototypes: Render 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 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: A PM is unsure whether an order state machine handles cancellation-after-payment. You build a one-file HTML demo with scenario walkthroughs; they click through, spot the illegal transition, and the validated reducer lifts directly into the real module. ## Quick Start Ask the agent to prototype whether your state model handles a specific edge case, or to generate three UI variants of an existing page switchable via a URL parameter.

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 containing a pure reducer or state machine module, with one button per action and tabbed scenario walkthroughs for edge cases. Anyone can open it by double-clicking, and the validated logic lifts directly into the real module afterward.

How to compare multiple UI design variants on the same page?▼

Render each variant as a separate exported component on the existing route, gated by a ?variant= URL search param. A floating bottom bar with arrow buttons and keyboard cycling switches variants while keeping the page's real data fetching, params, and auth intact.

Should a prototype use a framework or a plain HTML file?▼

Logic prototypes should be one plain HTML file with no framework, bundler, or server so non-developers can run them by double-clicking. UI prototypes follow the host project's existing framework and routing conventions since they live inside the real app.

When should I not write a throwaway prototype?▼

Skip prototyping when the question is already answered or when the code would need tests, persistence, or error handling to be meaningful — at that point you are building the real feature. Prototypes answer one question with in-memory state and no polish.

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 outside main as a primary source. Leave a pointer to that branch on the implementation issue so the main branch keeps only the validated decision.