Build throwaway terminal or UI prototypes to validate logic and design questions.
npx skills add https://github.com/joshhornby/dotfiles --skill prototype-joshhornby
Please help me install this Agent Skill. Skill: prototype Source: https://github.com/joshhornby/dotfiles/tree/main/.claude/skills/prototype Command: npx skills add https://github.com/joshhornby/dotfiles --skill prototype-joshhornby
?variant= URL param and a floating bottom bar with arrow-key cycling. - Answer Capture: Records the question and verdict in a commit message, ADR, or NOTES.md, then deletes or absorbs the prototype so nothing rots in the repo. - Use Case: Before building a new settings page, ask for three radically different layouts; flip through them in the browser, pick the winner, and fold it into the real page. ## Quick Start Ask the assistant to prototype the feature you are unsure about, for example: prototype three different layouts for the dashboard settings page so I can compare them.High-intent search queries and answers about installing and using this skill.
Build a small interactive terminal app around a pure reducer or state machine, with keyboard shortcuts that dispatch actions and a full state re-render after each one. Driving the model by hand exposes edge cases that look fine on paper.
Render each variant on the same route gated by a ?variant= URL search param, with a floating bottom bar to cycle between them using clicks or arrow keys. Variants must differ structurally in layout and hierarchy, not just colour or copy.
No. Prototypes use in-memory state by default because persistence is usually the thing being checked, not a dependency. Only hit a scratch database or clearly marked throwaway file when the question explicitly involves persistence.
Skip prototyping when the question is already answered or the change is small enough to implement directly. A prototype that needs tests, error handling, or generalisation has stopped being a prototype and should just be built properly.
Capture the answer in a commit message, ADR, or NOTES.md, then delete the prototype or fold the validated logic into the real module. Prototype code is written without tests or polish, so rewrite it properly rather than shipping it directly.
onbluerosesCreate disposable code to answer specific design questions.
silcamApply prefactoring principles to module boundaries, domain types, and error handling.
galatanovidiuDelegate code and design reviews to AI teammates with verified findings.
wkentaroRe-asks pending assistant questions as native interactive structured choices.