Build throwaway terminal or UI prototypes to validate logic and design decisions.
npx skills add https://github.com/Oatse/CWE-Automation --skill prototype-oatse
Please help me install this Agent Skill. Skill: prototype Source: https://github.com/Oatse/CWE-Automation/tree/main/.agents/skills/prototype Command: npx skills add https://github.com/Oatse/CWE-Automation --skill prototype-oatse
?variant= URL param and a floating bottom bar with arrow-key cycling. - Use Case: Before writing a real checkout flow, prototype the state machine in a terminal app to discover that canceling mid-payment leaves orphaned state, then capture the answer in a NOTES.md and delete the prototype. ## Quick Start Ask the AI to prototype the state machine for your checkout flow so you can drive it by hand and check the edge cases.High-intent search queries and answers about installing and using this skill.
Build a small terminal app where a pure reducer or state machine holds the logic and a thin TUI shell renders state after each keystroke. Drive it through edge cases by hand, capture what you learn, then lift the validated logic module into the real codebase.
Render several structurally different variants on the same route, gated by a ?variant= URL search param, with a floating bottom bar to cycle between them. Keep existing data fetching intact so variants are judged against real content, then delete the losers.
No. A prototype is throwaway code that answers one question, so tests, abstractions, and polish are explicitly skipped. If a prototype needs tests to be trusted, it has stopped being a prototype and should be rewritten properly.
Use a terminal prototype when the question is about logic, state transitions, or data shape. Use a UI prototype when the question is what something should look like. If ambiguous, match the surrounding code: backend modules suggest logic, pages suggest UI.
By default no; state lives in memory because persistence is usually what the prototype is checking, not depending on. If the question explicitly involves a database, use a scratch database or local file clearly marked as disposable.
no-sessionValidates product ideas through six forcing questions and saves a design document.
vinzenzBuilds throwaway logic TUIs or UI variants to answer design questions.
kashman001Capture decision rationale in commit trailers, project notes, and promoted ADRs.
c-sonnierCoordinate collaborative design sessions and produce a formal design document.