What problem does it solve? Without a shared experience baseline, each feature team invents its own components, state signals, and wording, so a product of eleven features becomes eleven inconsistent products. This Skill structures an expert interview with the design lead and writes the result as a ratifiable baseline document that every feature inherits. ## Core Features & Use Cases - Structured eight-topic interview: Covers conditions of use, navigation, component inventory, state dimensions, content and voice, accessibility floor, interaction budgets, and deferred decisions. - Baseline document generation: Writes .specify/memory/experience.md from a fixed template with status dimensions, composite state rules, confusable pairs, and pinned design references. - Gate and ratification workflow: Produces an evaluated checklist and a Draft/Ratified status footer so downstream architecture work knows what is binding. - Use Case: After product specs and technical constraints exist, run this Skill to agree the design ground rules — surface states, component vocabulary, accessibility minimums — before the architecture baseline is written. ## Quick Start Ask the AI to run the experience-baseline skill to interview the design lead and draft the project experience baseline from the existing specs.
