Build throwaway HTML or UI prototypes to answer design questions.
npx skills add https://github.com/Yassimba/loom --skill prototype-yassimba
Please help me install this Agent Skill. Skill: prototype Source: https://github.com/Yassimba/loom/tree/main/skills/prototype Command: npx skills add https://github.com/Yassimba/loom --skill prototype-yassimba
?variant= URL param and a floating bottom bar with arrow-key cycling. - Capture Workflow: Fold validated decisions into real code while committing the prototype to a throwaway branch as a primary source. - Use Case: Before writing a checkout state machine, build a clickable HTML demo so a PM can discover that the "cancel after payment" transition feels wrong. ## 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 for each action, and guided walkthrough tabs for edge cases. Anyone can open it by double-clicking, with no server or framework required.
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.
No. A prototype is throwaway code that answers one question, so tests, abstractions, and error handling beyond basic runnability are anti-patterns. Once the question is answered, rewrite the validated logic properly in the real codebase.
By default no — state lives in memory since persistence is usually what the prototype is checking, not a dependency. Only if the question explicitly involves a database should you use a scratch DB or local file clearly marked as disposable.
Fold the validated decision into the real code, then commit the full prototype to a throwaway branch outside main as a primary source. Leave a pointer to that branch on the implementation issue so the main branch keeps only the validated decision.
babuallyInterrogate plans and designs to expose missing assumptions and weak decision points.
samuelpatroImplement design variants directly on a live app route with a switcher for in-context comparison.
The-Focus-AIRuns a structured interview to refine a design while generating ADRs and a glossary.
agentflockDiagnose Myna issues by reading sources and skill files.