Build throwaway code experiments to answer open logic and data-flow questions.
npx skills add https://github.com/blauwtje/exo --skill prototyping-blauwtje
Please help me install this Agent Skill. Skill: prototyping Source: https://github.com/blauwtje/exo/tree/main/skills/prototyping Command: npx skills add https://github.com/blauwtje/exo --skill prototyping-blauwtje
temp/<name> branch, with no tests or abstractions, so real code never depends on them. - Design-space exploration: When no precedent settles the question, builds 2-3 structurally different variants and compares them before deciding. - Use Case: You are unsure whether a state machine or an event queue fits a new sync feature. Build a minimal throwaway version of each on a temp branch, observe the behavior, record the decision with the branch as evidence, then implement the chosen approach fresh. ## Quick Start Ask the AI to prototype an answer to an open question, for example: use prototyping to test whether a reducer pattern handles our undo stack correctly.High-intent search queries and answers about installing and using this skill.
Write one question ending in a question mark plus the observation that would settle it, then build the least code that produces that observation. Commit it on a temp branch, record the answer in your plan or issue, and build the real change fresh from the decision.
Build 2-3 structurally different variants when no precedent in the codebase or elsewhere settles the question and a single build would leave it open. Variants must differ in types, module boundaries, or control flow, not just naming, and land on the same temp branch.
No. A prototype has no tests, no failure handling, and no owner, so merging it ships those gaps. The temp branch stays unmerged as evidence for the decision, and the production change is built fresh through the ordinary stages.
Prototyping answers questions about how logic, state, or data behaves with running code. Questions about what a surface looks like belong to the designing skill, which renders rival visual directions side by side instead.
Storage is the first production concern and turns an experiment into code nobody dares delete. Prototypes carry no tests, no abstractions, and no persistence so they stay cheap to throw away once the question is answered.
josippapezGuides one-question-at-a-time dialogue to define outcomes and approaches before coding.
videojsWrites concise React component design records documenting non-inferable architectural decisions.
richfremPresent three plain-language layout options and save the selected direction.
surfingalienStress-tests implementation plans by resolving every open decision one question at a time.