← ClaudeAtlas

prototypelisted

Turn a static mockup / design into a working, clickable prototype, then close the gap with an automated visual-diff loop against the original. TRIGGER when the user pastes or points to a mockup/screenshot/Figma and wants it built ("here is a mockup, build a working prototype I can click through, matching the layout and states shown"), or asks to implement a design and self-correct against it ("implement this design, then take a screenshot of the result, compare it to the original, and fix any differences"). Hebrew: 'תבנה פרוטוטייפ מהמוקאפ', 'תהפוך את התמונה לפרוטוטייפ קליקבילי', 'תממש את העיצוב ותשווה למקור', 'לולאת השוואה ויזואלית'. NOT for production feature work with a real backend (use your normal feature-development process), NOT for pure design generation in Figma (use the figma skills).
hiyabh/claude-skills · ★ 0 · Web & Frontend · score 66
Install: claude install-skill hiyabh/claude-skills
# Prototype — Mockup → Clickable Prototype (+ Visual-Diff Loop) ## Purpose Take a **static input** (pasted mockup image, screenshot, Figma frame, or a written design spec) and produce a **working, clickable prototype** that reproduces the layout and the visible states. Then optionally run a **visual-diff loop**: render the result, screenshot it, compare against the original, and fix the differences — repeating until it matches. This is throwaway-quality-friendly, fast-feedback work. Do not over-engineer: no real backend, no auth, no DB unless explicitly asked. Mock data is fine. **Language:** talk to the user in Hebrew; code/comments in English (global rules). --- ## Mode A — Mockup → Clickable Prototype ### 1. Read the mockup - If an image was pasted, **look at it carefully** and enumerate: screens/views, major regions (header, sidebar, content, footer), components, and every **state** shown (default, hover, active, empty, loading, error, filled, modal open, etc.). - If it's a Figma URL, use the `figma:figma-generate-design` / `get_design_context` tools to pull layout + tokens instead of guessing. - Restate to the user, in one short Hebrew paragraph, what you're about to build: the list of screens and the interactive states — so mismatches surface early. ### 2. Pick the lightest stack that fits - Default to a **single self-contained HTML file** (inline CSS + a little JS) for simple 1–3 screen flows — fastest to iterate and screenshot. - Use **React (Vite) +