Prototyping strategy
Skill Dragoon0x/everything-design-taste/skills/prototyping-strategy
A taste system for AI agents. 288 skills, 80 agents, 12 rules, and 8 hooks that turn generic AI output into work with genuine design quality. Anti-slop detection, typography craft, color systems, brand voice, product strategy, and 50+ specialized reviewers across UI, industry, platform, and content domains.
npx -y skills add Dragoon0x/everything-design-taste --skill prototyping-strategyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Prototyping fidelity decisions, tools selection, prototype testing, and interactive prototype design.
SKILL.md
1.3 KB, as published. Nobody here has run it
Prototyping Strategy
Fidelity Spectrum
| Fidelity | Tool | Best For | Time |
|---|---|---|---|
| Paper | Paper + pen | Early concepts, team brainstorming | Minutes |
| Lo-fi wireframe | Balsamiq, Whimsical | Structure validation, flow testing | Hours |
| Mid-fi | Figma wireframes | Usability testing, stakeholder alignment | Days |
| Hi-fi | Figma, Framer | Final design validation, development spec | Days-weeks |
| Code | HTML/CSS, React | Production-ready, complex interactions | Weeks |
When to Use Each
- Paper: When you need to explore 10+ ideas quickly
- Lo-fi: When testing navigation and flow (not visual design)
- Mid-fi: When testing usability before investing in visual design
- Hi-fi: When testing visual design, brand response, and polish
- Code: When testing complex interactions, animations, or real data
Prototype Testing Rules
- Match fidelity to the question you're testing
- Use real content (not lorem ipsum)
- Build only the paths you're testing (not the whole app)
- Let users find their own way (don't guide them)
- Prototype the error states and edge cases too