prototypelisted

# /prototype Build prototypes people can click through, share URLs to specific screens, comment on, and iterate on — no build step, no backend. Output is plain HTML + Tailwind CDN + a few small vanilla JS files. ## When to use - User asks for a prototype, mockup, demo, pitch page, or sales click-through. - User wants to show stakeholders a UI without building the real product. - User wants to explore visual directions before committing to an implementation. ## When NOT to use - A real production feature — use the app's actual stack. - A one-off component or snippet — just write it inline. - A design system — use `/design-consultation` or `/teach-impeccable`. ## Commands ``` /prototype → full flow: discover → build → assess → ship /prototype variant "<vibe>" → fork current prototype into variants/<slug>/ /prototype apply-feedback <file> → read feedback JSON, apply each comment, re-assess /prototype intake <url…> → add sites to the inspiration corpus ``` ## The flow at a glance ``` 0. Preflight → ensure-deps.sh auto-installs impeccable + prompt-refiner 1–4. Discover → mode check, Q&A, refine spec, design shaping → reference/discovery.md 5–6. Build → scaffold templates, control bar, data layer, screens → reference/build.md 7–8. Assess → impeccable (or builtin-lint) + browser QA → reference/assess.md 9. Handoff → DEMO.md + README.md inside the prototype 10. Ship → run command, share-URL tip,