prototype

What problem does it solve? Teams often debate design decisions about UI, state logic, or system behavior without evidence, building full implementations before knowing whether the idea works. This Skill structures the creation of small, disposable prototypes that answer one specific question by being executed, then captures the verdict so the finding is never lost. ## Core Features & Use Cases - Question-first workflow: Forces a written question contract (question, options, deciding observation, done condition) before any code is written, so the prototype has a clear stopping condition. - Three prototype shapes: UI variants rendered on a real route with a switcher bar, interactive terminal apps for state/logic models, and one-shot probe scripts that verify assumptions about existing code or external APIs. - Verdict capture and clean handover: Records answered, rejected, or inconclusive outcomes next to the prototype and hands git commands to the user without ever running write operations itself. - Use Case: A team is unsure whether a checkout state machine should allow applying a coupon after payment. The Skill builds a small terminal app with a pure reducer and preset states, the user drives it by hand, and the rejected or validated design is recorded before any real implementation begins. ## Quick Start Ask the assistant to build a prototype that answers your specific design question, for example: prototype whether the checkout flow should allow applying a coupon after payment.