prototype

Build throwaway terminal or UI prototypes to validate logic and design decisions.

Updated Nov 23, 2024
One-click install
npx skills add https://github.com/tokisakiyuu/dotfiles --skill prototype-tokisakiyuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/tokisakiyuu/dotfiles/tree/main/home/dot_claude/skills/prototype
Command: npx skills add https://github.com/tokisakiyuu/dotfiles --skill prototype-tokisakiyuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design decisions about state models, business logic, or UI layouts often look fine on paper but break down in practice. This Skill builds quick throwaway prototypes so you can press buttons, flip between variants, and discover flaws before committing to real implementation. ## Core Features & Use Cases - Logic Prototypes: Build a small interactive terminal app with a pure reducer, state machine, or function set behind a thin TUI shell, so you can drive state transitions by hand and spot edge cases. - 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. - Answer Capture: Records the validated decision in a commit message, ADR, or NOTES.md, then deletes or absorbs the prototype so nothing rots in the repo. - Use Case: You are unsure whether a state machine handles an edge case where action X precedes Y. The Skill builds a one-command terminal app that renders current state and keyboard shortcuts, letting you push the model through real cases until the flaw surfaces. ## Quick Start Ask the AI to prototype the state machine or page design you are unsure about so you can play with it before writing production code.

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 where a pure reducer or state machine sits behind a thin TUI shell. Each keystroke dispatches an action, the screen clears and re-renders the full state, letting you drive edge cases by hand and see where the model breaks.

How to create multiple UI design variants on one page?▼

Render each variant as a separate exported component on the same route, gated by a ?variant= URL search param. Add a floating bottom bar with left and right arrows that updates the param via the framework router, so variants are shareable and reload-stable.

Should a prototype connect to a real database?▼

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

When should I use a logic prototype versus a UI prototype?▼

Use a logic prototype when the question is whether a state model, reducer, or data shape behaves correctly under real cases. Use a UI prototype when the question is what a page or component should look like, comparing structurally different layouts.

What are the limitations of prototype code?▼

Prototype code skips tests, error handling, and abstractions, so it must never ship directly to production. Once it answers its question, either delete it or rewrite the validated logic properly in the real module.