Builds throwaway HTML or UI prototypes to answer design questions before implementation.
npx skills add https://github.com/MaxWolf-01/agents --skill prototype-maxwolf-01
Please help me install this Agent Skill. Skill: prototype Source: https://github.com/MaxWolf-01/agents/tree/main/mx/skills/prototype Command: npx skills add https://github.com/MaxWolf-01/agents --skill prototype-maxwolf-01
?variant= URL param and a floating bottom bar with arrow-key navigation. - Answer capture: Records the question, what was tried, and the user's verdicts as rules with reasons in an ANSWER.md, then archives the prototype under agent/prototypes/ as a primary source. - Use Case: A team is unsure whether a multi-step checkout state machine handles cancellations correctly. The Skill builds a clickable HTML demo with scenarios for the happy path, an illegal transition, and an edge case, letting a product manager feel the model and report what feels wrong. ## Quick Start Ask the agent to prototype the design question you are facing, for example: build a clickable prototype comparing three layouts for the settings page, or a state-machine demo for the checkout flow.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 module, free-play action buttons, and tabbed guided walkthroughs for edge cases. Non-developers can open it by double-clicking and drive the model through scenarios that are hard to reason about on paper.
Render 3 to 5 structurally different variants on the same route, gated by a ?variant= URL search param, with a floating bottom bar to cycle between them. Variants must differ in layout and information hierarchy, not just colors, and the switcher is hidden in production builds.
Prototype only when rival shapes exist: several designs to compare, or one design that must be seen or driven before it can be judged. A design with one clear shape should go straight to implementation, since prototyping it first is just a slower way of building it.
No, state lives in memory by default because persistence is usually the thing being checked, not a dependency. If the question explicitly involves a database, use a scratch database or local file clearly marked as disposable.
The verdicts are recorded as rules with reasons in an ANSWER.md, and the prototype moves to agent/prototypes/ as a committed primary source. Winning UI variants are rewritten properly in the real code rather than promoted directly, since prototype code skips tests and error handling.
NAMEWTAConverts an unanswerable decision into a structured Markdown discovery questionnaire for a knowledgeable recipient.
MythologIQCreate, version, and supersede Architecture Decision Records with traceable links.
nikhilvallishayeeDetect edge cases and challenge assumptions through three verification questions.
zgagnonWrite code and tests using mocks to define APIs through usage.