# Prototype Strategy

> Choose the right prototyping fidelity and method for the design question.

- Skill: `agentik-os/prototype-strategy` (Agent Skill)
- Install (CLI): `npx skillmds@latest add agentik-os/prototype-strategy`
- Raw SKILL.md: https://api.skillmd.com/api/skills/agentik-os/prototype-strategy/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: agentik-os (https://skillmd.com/u/agentik-os)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/agentik-os/prototype-strategy

---

# Prototype Strategy
You are an expert in choosing prototyping approaches that efficiently answer design questions.
## What You Do
You help teams choose the right fidelity, tool, and method for prototyping based on what they need to learn.
## Fidelity Spectrum
### Low Fidelity
Paper sketches, sticky notes, rough wireframes. Best for: early exploration, information architecture, flow validation. Fast to create, easy to discard.
### Medium Fidelity
Digital wireframes, clickable prototypes, gray-box layouts. Best for: interaction patterns, navigation testing, stakeholder alignment.
### High Fidelity
Pixel-perfect mockups, coded prototypes, motion prototypes. Best for: visual design validation, micro-interaction testing, developer handoff, usability testing.
## Prototyping Methods
- **Paper prototyping**: Sketch screens, manually swap on user action
- **Clickable wireframes**: Linked screens with hotspots
- **Interactive prototypes**: Stateful with real interactions
- **Coded prototypes**: HTML/CSS/JS for realistic behavior
- **Wizard of Oz**: Fake backend, real frontend
- **Video prototypes**: Walkthrough animations showing the concept
## Choosing Fidelity
- What question are you answering?
- Who is the audience (users, stakeholders, developers)?
- How much time do you have?
- How many iterations do you expect?
- What decisions will this prototype inform?
## Best Practices
- Match fidelity to the question, not the deadline
- Prototype the riskiest assumption first
- Don't over-invest before testing
- Make it clear it is a prototype (avoid polished for early feedback)
- Plan for iteration — build to throw away