prototype

Build throwaway terminal or UI prototypes to validate state models and design questions.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/julianckt/adoptarun --skill prototype-julianckt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/julianckt/adoptarun/tree/main/.agents/skills/prototype
Command: npx skills add https://github.com/julianckt/adoptarun --skill prototype-julianckt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design questions about state machines, data models, or page layouts are hard to answer on paper. This Skill builds throwaway, runnable prototypes that let you press buttons, flip between UI variants, and discover flaws in the idea before committing to production code. ## Core Features & Use Cases - Logic Prototypes: Build a lightweight interactive terminal app that drives a pure reducer, state machine, or function set through edge cases, re-rendering full state after every keystroke. - UI Prototypes: Generate 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 prototype itself to a throwaway branch as a primary source. - Use Case: Before writing a checkout flow, prototype the state machine in a terminal TUI to confirm that cancel-after-payment transitions behave correctly, then lift the validated reducer into the real module. ## Quick Start Ask the AI to build a throwaway prototype that answers whether your state model handles a specific edge case, or to generate three UI variants of a 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 small interactive terminal app around a pure reducer or state machine, with keyboard shortcuts dispatching actions and the full state re-rendered after every keystroke. Keep the logic module free of I/O so it can be lifted into the real codebase once validated.

How to compare multiple UI design variants on one page?

Render each variant on the same existing route gated by a ?variant= URL search param, with a floating bottom bar offering previous/next arrows and arrow-key cycling. Variants must differ structurally in layout and information hierarchy, not just color or copy.

Should a prototype include tests and error handling?

No. A prototype that needs tests is no longer a prototype. Skip tests, persistence, and abstractions; include only the minimal error handling needed to keep it runnable, since the goal is to learn something fast and throw the code away.

When should I use a terminal prototype versus a UI prototype?

Use a terminal (logic) prototype when the question is whether a state model or data shape behaves correctly under edge cases. Use a UI prototype when the question is what a page should look like, generating several variants on an existing route.

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 kept out of main as a primary source. Leave a pointer to that branch on the implementation issue along with the verdict.