Build throwaway HTML or UI prototypes to answer design questions.
npx skills add https://github.com/MSC72m/DevForge --skill prototype-msc72m
Please help me install this Agent Skill. Skill: prototype Source: https://github.com/MSC72m/DevForge/tree/main/skills/prototype Command: npx skills add https://github.com/MSC72m/DevForge --skill prototype-msc72m
?variant= URL param and a floating bottom bar with arrow-key cycling. - Capture Workflow: Fold validated decisions into real code while committing the prototype itself to a throwaway branch as a primary source. - Use Case: A PM is unsure whether a checkout state machine handles cancel-after-payment. Use this Skill to build a shareable HTML demo where they click through the exact scenario and discover the flaw themselves. ## Quick Start Use the prototype skill to build a clickable demo that tests whether my order state machine handles cancellation after payment.High-intent search queries and answers about installing and using this skill.
Build a single self-contained HTML file with a pure reducer or state machine in one script block, free-play buttons per action, and guided walkthrough tabs for edge cases. Anyone can open it by double-clicking and drive the model without installing anything.
Render 3-5 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.
Logic prototypes should be one plain HTML file with inline CSS and JS so they survive being emailed and opened by double-click. UI prototypes follow the host project's existing framework and component library since they live on real routes.
Never add tests to a prototype; a prototype that needs tests is no longer a prototype. The code is throwaway by design, so skip error handling, persistence, and abstractions beyond what makes it runnable.
Fold the validated decision into the real codebase, then commit the full prototype to a throwaway branch as a primary source with a pointer on the implementation issue. The main branch keeps only the validated decision, not the prototype shell.
HDeiblerAn example.
inkfinBuild throwaway HTML or UI prototypes to answer design questions about logic or layout.
Evolutionary-LeadershipInterviews users to stress-test ideas and records outcomes in issue tracker.
EveryIncBuild throwaway web prototypes to settle product design questions before implementation.