prototype

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

Updated May 31, 2026
One-click install
npx skills add https://github.com/AlexanderNarbaev/agi --skill prototype-alexandernarbaev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/AlexanderNarbaev/agi/tree/main/.opencode/skills/matt-pocock/prototype
Command: npx skills add https://github.com/AlexanderNarbaev/agi --skill prototype-alexandernarbaev

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, flip between variants, and feel whether a model or design actually works 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: Generate 3-5 radically different UI variants on one route, switchable via a ?variant= URL param and a floating bottom bar with arrow-key cycling, gated out of production builds. - Capture Workflow: Fold validated decisions into real code while preserving the prototype on a throwaway branch as a primary source. - Use Case: A PM is unsure whether a state machine handles an edge case. 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 assistant to prototype whether your state machine handles a specific edge case, or to generate three 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 production code?

Build a single self-contained HTML file with a pure reducer or state machine in one script block, free-play buttons per action, and tabbed guided 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 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 cycling via arrows or keyboard. Keep existing data fetching intact and hide the switcher in production builds.

Should a prototype use a real database or persistence?

No. Prototypes keep state in memory by default because persistence is usually the thing being checked, not a dependency. Only use a scratch database or clearly marked throwaway file when the question explicitly involves storage.

When should I not write tests for prototype code?

Never write tests for a prototype — a prototype that needs tests is no longer a prototype. Tests belong to the validated logic once it is folded into the real codebase after the prototype answers its question.

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

The validated decision is rewritten properly into the real code, while the full prototype is committed to a throwaway branch as a primary source with a pointer left on the implementation issue. Prototype code never ships directly to production.