What problem does it solve? Teams often jump from functional requirements straight into architecture and backlog without ever defining how the product should feel and behave, leaving navigation, platform choices, and accessibility commitments to be invented later by developers. This Skill produces a definition-level Experience Design document that binds those decisions before requirements are quantified. ## Core Features & Use Cases - Structured Experience Definition: Generates a 13-section document covering information architecture, application shell, platform definition, creative direction, key user journeys, motion system, view state matrix, and a WCAG accessibility baseline. - Calibration Dials: Classifies the product archetype (data-dense tool, transactional app, content surface, consumer mobile) and sets VISUAL_DENSITY, MOTION_INTENSITY, and DESIGN_VARIANCE so later decisions stay consistent. - Traceability & Gating: Every screen gets an XD-S-XXX ID traced to functional requirements, every journey traces to a use case, and the document is blocked until the Functional Spec is signed and validated against 20 rules before Solution Architect sign-off. - Use Case: After signing a Functional Requirements Specification for a field-technician mobile app, run this Skill to define offline-capable platform intent, the screen map, and the WCAG 2.2 AA baseline that Phase 4 will turn into measurable NFRs. ## Quick Start Ask the agent to run the experience-design skill to define the product experience for the current project once the functional spec is signed.
