prototyping-strategy
Installation
SKILL.md
Purpose
Guide the selection of the most effective prototyping approach for a given project situation. Use this when requirements are unclear, feasibility is uncertain, or stakeholders need something tangible to react to. The output is a recommended prototyping approach with scope, fidelity, lifecycle, and evaluation plan.
This is not a prototyping tutorial -- it is a decision framework for choosing what to prototype, how, and how to evaluate the results. For UI flow modeling that informs prototyping, see skills/dialog-map/SKILL.md.
Key Concepts
Prototype Dimensions
Horizontal (Breadth) vs. Vertical (Depth):
| Dimension | What It Shows | Best For |
|---|---|---|
| Horizontal (mock-up) | Many features at the surface level; navigation and layout | Validating UI flow, screen inventory, user workflows |
| Vertical (proof-of-concept) | One feature implemented deeply, end to end | Validating technical feasibility, performance, integration |
Fidelity Levels: