prototype

Build throwaway HTML or UI prototypes to answer design questions about logic or layout.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill prototype-maicongambini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/prototype
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill prototype-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design questions about state models, business logic, or UI layout are hard to settle on paper. This Skill produces throwaway prototypes that let you press buttons, watch state change, or flip between radically different UI variants before committing to real code. ## Core Features & Use Cases - Logic Prototypes: Generate a single self-contained HTML file with free-play 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 one route, switchable via a ?variant= URL param and a floating bottom bar with arrow-key cycling. - Capture Workflow: Fold validated decisions into real code and archive the prototype on a throwaway branch as a primary source. - Use Case: A product manager is unsure whether an order state machine handles cancellation-after-shipping. The Skill builds a one-file HTML demo with scenario walkthroughs so the PM can click through the edge case and confirm the model. ## Quick Start Ask the agent to prototype whether your state machine handles a specific edge case, or to generate three different layout variants for an existing page.

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 with a pure reducer or state machine in one script block, free-play buttons for each action, and tabbed guided walkthroughs for edge cases. Anyone can open it by double-clicking and watch state change after every click.

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 a framework like React or a dev server?

For logic prototypes, no — use one plain HTML file with inline CSS and JS so it opens by double-click and survives being emailed. UI prototypes follow the host project's existing framework and routing conventions instead of inventing new structure.

When should I not write a throwaway prototype?

Skip prototyping when the question is already answered, when the code needs tests, persistence, or production hardening, or when you intend to ship the prototype directly. Prototype code is written under no-tests, no-polish constraints and must be rewritten when folded into production.

What happens to prototype code after the question is answered?

The validated decision — such as the reducer or winning variant — is folded into the real codebase, while the full prototype is committed to a throwaway branch as a primary source. A pointer to that branch is left on the implementation issue.