Build throwaway prototypes that answer logic or UI design questions.
npx skills add https://github.com/IsKenKenYa/skills --skill prototype-iskenkenya
Please help me install this Agent Skill. Skill: prototype Source: https://github.com/IsKenKenYa/skills/tree/main/skills/engineering/prototype Command: npx skills add https://github.com/IsKenKenYa/skills --skill prototype-iskenkenya
?variant= URL param and a floating bottom bar with arrow-key navigation, mounted on an existing route or a throwaway one. - Capture Workflow: Fold validated decisions into real code, then commit the prototype to a throwaway branch as a primary source with a pointer on the implementation issue. - Use Case: Before implementing a checkout state machine, build a clickable HTML demo so a PM can press buttons through edge cases and confirm the model feels right. ## Quick Start Ask the agent to prototype the state model or page layout you are unsure about, stating the specific question the prototype should answer.High-intent search queries and answers about installing and using this skill.
Build a single self-contained HTML file with the state machine as a pure module, free-play buttons for each action, and tabbed guided walkthroughs for edge cases. Anyone can open it by double-clicking, with no framework, bundler, or server required.
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 and only swap the rendered subtree per variant.
No. Prototypes keep state in memory by default, since persistence is usually the thing being checked, not a dependency. If the question explicitly involves a database, use a scratch DB or local file clearly marked as disposable.
A UI prototype is wrong when the question is about logic or state transitions rather than appearance; use a clickable logic demo instead. It is also wrong when variants differ only in color or copy, since real variants must disagree about structure.
The validated decision is folded into the real code, and the prototype itself is committed to a throwaway branch as a primary source with a pointer left on the implementation issue. Prototype code is never promoted directly to production.
MushroomFleetConduct adaptive twenty-question interviews and update a markdown artifact.
ArcReelBuild throwaway HTML or UI prototypes to validate design questions.
ruskibeatsReview code diffs against coding standards and specifications.
EmrebenerDetect shallow, leaky, and tightly coupled modules and propose seam-focused refactoring designs.