What problem does it solve? Teams often design interfaces from screenshots, surface labels, or assumed mental models, producing screens that misrepresent what the business actually does. This Skill turns vague product asks into grounded, shippable designs by establishing the business model and the user's task before proposing any surface. ## Core Features & Use Cases - Business Model Grounding: Extracts concepts, states, obligations, and business events from domain evidence before diagnosing any surface, preventing designs built on misleading labels. - Structured Design Workflow: Runs Discover, Frame, or Materialize modes covering evidence mapping, view modeling, structural diagnosis, scoping, and optional prototyping. - Pattern Base and Reality-Check Log: Applies a curated pattern base (P-01 through P-14) and a trace schema to record overturned assumptions and feed reusable product lessons. - Use Case: When a stakeholder says "this page feels wrong," use this Skill to ground what the business actually models, diagnose the structural error, and produce a scoped design spec with honest capability buckets. ## Quick Start Ask the agent to use the product-design skill to figure out what the team dashboard surface should actually be and why.
