design-prototype
/design-prototype
Assemble a clickable, runnable prototype from screens/components — wiring navigation, state, and interactions so a team can actually click through it. Use when the user says "make it clickable", "build a prototype", "wire up the flow", "interactive prototype", "make the screens navigate", or has static screens that need to come alive. Part of the Product Design set. Verifies interactions with a browser tool.
- Author
- DKeken ↗
- Repository
- codex-skills-alternative ↗
- Licence
- MIT
- Last repository change
- 03.06.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 03.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Assemble a clickable, runnable prototype from screens/components — wiring navigation, state, and interactions so a team can actually click through it. Use when the user says "make it clickable", "build a prototype", "wire up the flow", "interactive prototype", "make the screens navigate", or has static screens that need to come alive. Part of the Product Design set. Verifies interactions with a browser tool.
Triggers from the description
Original author description
Assemble a clickable, runnable prototype from screens/components — wiring navigation, state, and interactions so a team can actually click through it. Use when the user says "make it clickable", "build a prototype", "wire up the flow", "interactive prototype", "make the screens navigate", or has static screens that need to come alive. Part of the Product Design set. Verifies interactions with a browser tool.
How it works
- When to use
- When NOT to use
- Inputs
- Workflow
- Worked example
- Quality bar / Definition of done
- Common pitfalls
- Handoff
- Tooling
SKILL.md preview
--- name: design-prototype description: Assemble a clickable, runnable prototype from screens/components — wiring navigation, state, and interactions so a team can actually click through it. Use when the user says "make it clickable", "build a prototype", "wire up the flow", "interactive prototype", "make the screens navigate", or has static screens that need to come alive. Part of the Product Design set. Verifies interactions with a browser tool. --- # Design — Prototype Turn static screens into a working clickable flow that demonstrates the experience end to end. A prototype's job is to let someone *experience the flow* and give feedback — not to be production-hardened. Stubs are fine and expected; broken navigation is not. ## When to use - You have screens/components (from image-to-code, url-to-code, or ideate) and need them connected. - "Make it clickable", "wire the flow", "let me click through it". - Validating a UX flow with stakeholders before real backend work. ## When NOT to use - No screens exist yet → build them first (`design-image-to-code` / `design-url-to-code`). - You need production code with real data/auth — that's an engineering task, not a prototype. - Just checking a built prototype against the design → `design-qa`. ## Inputs - The **screens/components** to connect. - The **flow to demonstrate**: happy path + key states. - `./design/context.md` for the JTBD (the flow should make *that* easy). ## Workflow 1. **Map the flow graph**: screens are nodes, actions are edges (click → navigate, submit → state change). Write it down before wiring. 2. **Wire routing/navigation** between screens. 3. **Add interaction states**: hover, active, disabled, loading, empty, error, success. Cover at least the **happy path + one error state** (the most-skipped, most-important state). 4. **Stub data** so it's clickable without a backend; clearly mark where real data plugs in. 5. **Verify**: drive the whole happy path in a browser-automation tool — click every step, confirm nothing dead-ends. Fix what breaks. 6. Keep it **runnable with one command**. ## Worked example Flow (JTBD: create first project in <2 min): Welcome → Choose template → Name it → Dashboard. ``` flow graph: Welcome --[Get started]--> Template --[select]--> Name --[Create]--> Dashboard Name --[empty submit]--> Name(error: "Name required") Template --[back]--> Welcome states wired: hover on cards, loading on Create (300ms stub), error on empty name, success → Dashboard with the new project card stubs: templates = 3 fixtures; "Create" writes to in-memory store (TODO: real API) verify (browser): clicked Welcome→Template→Name→Create→Dashboard ✓; empty-name error shows ✓; back nav works ✓; no dead ends run: `npm install && npm run dev` → :5173 ``` ## Quality bar / Definition of done - Full happy path is clickable end to end. - At least one error/empty state is present and reachable. - No dead ends or broken links. - Runs locally; build + typecheck clean. - A browser walkthrough of the happy path passes. ## Common pitfalls - **Happy-path only** — skipping error/empty/loading states; those are where real feedback comes from. - **Dead ends** — a button that goes nowhere kills the demo. Walk every path. - **Over-engineering** — wiring a real backend/auth for a prototype. Stub it, mark the TODO. - **Style drift** — re-styling screens during wiring so they no longer match the locked direction. - **No verification** — assuming it works without clicking through it. ## Handoff Working prototype → `design-qa` (conformance check vs the design + requirements) → `design-share` (publish for review). Don't share before QA on anything stakeholder-facing. ## Tooling Needs a **browser-automation tool** to verify the flow by clicking through it. Without one, wire carefully and manually note that the walkthrough is unverified.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · DKeken/codex-skills-alternative | 100 | MIT |
| mtrense/skills | 90 | MIT |
Database snapshot: 13.11.2026 · package version 98d615380ecd (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100arn-spark-clickable-prototype
This skill should be used when the user says "clickable prototype", "arn clickable prototype", "interactive prototype", "test interactions", "validate UX", "user journeys", "test navigation", "make it clickable", "prototype interactions", "test the prototype", "build the… - 95arn-spark-clickable-prototype-teams
This skill should be used when the user says "clickable prototype teams", "arn clickable prototype teams", "team clickable prototype", "debate clickable prototype", "collaborative interaction review", "clickable prototype with debate", "team-based interaction review",… - 90wire-prototype
Document a prototype or user flow — screens, states, transitions, and annotations. Use when asked to "document this prototype", "map the screens and states", or "annotate this flow". - 90design
Phase 3 of the Builder Method — create a preview of the product's screens (a Claude Design artifact or a local clickable prototype) to validate the user flows before building, recorded in builder/03-design.md. Use after the PRD, when the user wants to see the app before it's… - 90interactive-prototype
Use when the user asks for a working, clickable prototype — something that behaves like a real app rather than a static mockup. React + useState/useEffect, realistic fake data, working state transitions. - 100interactive-prototype
Build a clickable, hi-fi prototype of a product or flow — not a wireframe, not a static mock. The user can navigate, toggle states, and feel the interaction. Reach for this whenever the design has flows, multi-screen states, or many-option situations.