What problem does it solve? Design artifacts often describe the system instead of guiding the consumer, mixing implementation details with purpose and proposing solutions that cannot actually be executed. This Skill reframes design work around who consumes the artifact and what they need to accomplish. ## Core Features & Use Cases - Create mode: Set the frame before designing — identify the consumer, their task, and success criteria, then design through that lens. - Review mode: Run a finished artifact through consumer criteria to find where you wrote "for yourself" instead of "for the consumer". - Two-check validation: Verify solutions are operationalizable (the user can actually act on them) and available (the proposed UI or tool actually exists). - Use Case: When writing an API response description for an AI agent, replace architectural explanations like "peer to other root contexts" with actionable guidance like "default folder for paths, starting points for navigation". ## Quick Start Review this design document from the consumer's perspective and flag anything written for the implementer instead of the user.
