What problem does it solve? Teams often design from screenshots or assume the interface reflects what the product actually does, leading to surfaces that misrepresent business semantics, promise nonexistent actions, or organize information around system entities instead of user tasks. This Skill establishes what the business actually models before any design decision, then frames the user's view model so the surface answers real retrieval and decision needs. ## Core Features & Use Cases - Business Model Grounding: Enumerate concepts, states, roles, obligations, and business events from domain evidence, including capabilities the current surface hides. - Structural Diagnosis: Identify errors that are wrong regardless of taste, such as decision inboxes rendered as error logs or buttons promising business events that do not exist. - Scoped Deliverables: Produce design specs with reality-check logs, honest scope buckets (modeled/exposed/not modeled), and optional prototypes via three run modes: Discover, Frame, and Materialize. - Use Case: Given a vague request like "redesign our home surface," ground the domain model, discover that three of four message types were never surfaced, and deliver a spec for a decision inbox organized by required action rather than producing entity. ## Quick Start Ask the agent to analyze what a product surface should be and why, starting from the business model rather than the current screen.
