What problem does it solve? Teams routinely mismatch prototype fidelity to the question being asked — polishing mockups before structure is settled, testing performance with Figma click-throughs, or skipping prototyping entirely and iterating expensively in production. This Skill provides a decision framework for matching prototype fidelity to the specific question each iteration cycle needs to answer. ## Core Features & Use Cases - Fidelity Ladder Guidance: Covers six fidelity levels from paper sketches through wireframes, mockups, clickable prototypes, code prototypes, and production beta, with the cost and answerable questions for each. - Question-to-Fidelity Matching: Maps common design questions (IA structure, visual style, flow usability, performance, adoption) to the cheapest fidelity that answers them. - Anti-Pattern Detection: Flags mistakes like pixel-perfect early design, testing with the wrong fidelity, and shipping prototypes as products. - Use Case: When planning a user research session for a new feature, use this Skill to decide whether sketches, a clickable Figma prototype, or a code prototype will actually answer your research question — avoiding weeks of over-investment or unusable feedback. ## Quick Start Ask the agent which prototype fidelity to use for testing whether users understand your new onboarding flow before writing production code.
