prototype

Builds disposable prototype demos to answer logic or UI design questions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design questions about state models, business logic, or UI layouts are hard to resolve on paper. This Skill produces throwaway prototype code—a shareable single-file HTML demo for logic questions, or multiple switchable UI variants on one route for visual questions—so decisions get validated before real implementation. ## Core Features & Use Cases - Logic Prototypes: Generates a self-contained HTML file with a pure reducer/state-machine module, free-play action buttons, and guided scenario walkthroughs that non-developers can click through. - UI Prototypes: Renders 3-5 structurally distinct UI variants on an existing route (or a disposable route), switched via a ?variant= URL parameter and a floating bottom bar with arrow-key navigation. - Use Case: A product manager is unsure whether an order state machine handles cancellation-after-shipping. The Skill builds a single HTML file with labeled state panels and scenario tabs so the PM can press buttons, spot the illegal transition, and hand back a verified reducer for the real codebase. ## Quick Start Ask the agent to build a prototype that tests whether your state model handles a specific edge case, or to generate three UI variants of a page switchable via 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 real code?▼

Build a single self-contained HTML file containing a pure reducer or state machine module, with buttons for each action and a readable state panel that re-renders after every click. Non-developers can open the file directly and test edge cases without any installation.

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

Render 3 to 5 structurally distinct variants on the same route, switched by a ?variant= URL search parameter. Add a floating bottom bar with previous/next arrows and keyboard navigation so stakeholders can cycle through variants and share links to specific ones.

Should a UI prototype modify an existing page or use a new route?▼

Prefer mounting variants on an existing page so they render with real data, headers, and density. Only create a disposable route when no existing page can reasonably host the prototype, and name it clearly as a prototype.

Can logic prototypes use React or a build server?▼

No. Logic prototypes must be a single HTML file with plain inline HTML, CSS, and JS so recipients can double-click to open or share it by email. Frameworks, bundlers, and dev servers break the shareability requirement.

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

Record the validated decision in the real codebase, then move the prototype itself to a throwaway branch rather than the main branch. The verified logic module gets extracted into a real module; losing UI variants are deleted from main.

When should I not use a disposable prototype?▼

Avoid prototyping when the question is already answered, when persistence or production behavior is the actual concern, or when the prototype would need tests and error handling. Prototypes answer exactly one question and skip all polish.