Build throwaway HTML demos and UI variants to answer design questions.
npx skills add https://github.com/jwh3times/holland-vip --skill prototype-jwh3times
Please help me install this Agent Skill. Skill: prototype Source: https://github.com/jwh3times/holland-vip/tree/main/.agents/skills/prototype Command: npx skills add https://github.com/jwh3times/holland-vip --skill prototype-jwh3times
?variant= URL parameter and a floating bottom bar with arrow-key navigation. - Capture Workflow: Fold validated decisions into real code while preserving the prototype on a throwaway branch as a primary source. - Use Case: A product manager is unsure whether a checkout state machine handles a cancel-after-payment edge case. The Skill builds a shareable HTML demo the PM can click through to find the flaw before any backend code is written. ## Quick Start Ask the AI to build a prototype that answers whether your state model handles a specific edge case, or to generate three UI variants of an existing page.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 for each action, and tabbed guided walkthroughs for edge cases. Anyone can open the file by double-clicking and drive the model without installing anything.
Render 3 to 5 structurally different variants on the same route, gated by a ?variant= URL search parameter. Add a floating bottom bar with left and right arrows that cycles variants via the framework router so each variant is shareable and reload-stable.
No. Prototypes keep state in memory by default because persistence is usually the thing being checked, not a dependency. Only use a scratch database or clearly marked throwaway file when the question explicitly involves persistence.
Use a logic prototype when the question is whether a state model, data shape, or business rule feels right. Use a UI prototype when the question is what a page or component should look like. Ambiguous cases default to whichever branch matches the surrounding code.
The validated decision is folded into the real codebase, 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.
trydyddHarden interactive UI components with error handling, empty states, onboarding, and i18n support.
devmuslimTrack stakeholder satisfaction KPIs for product releases via surveys and issue tracking.
santosomarTranslate natural-language requirements into formal constraints and property-based tests.