Codify the shared design language: tokens, components, patterns, guidelines.
When to run it
When the team has shipped enough surface area that inconsistency is starting to cost — different button styles, different colour decisions per feature, fragmented typography.
What you'll have at the end
A design_system with structured design_token, design_component, design_pattern, and design_guideline entities. Each connected back to the screens and flows that depend on it.
Common starting point
Audit the live product. List every variant of (a) button, (b) input, (c) heading style. Pick the canonical version of each.
Sequence summary
One step: run the design_system creation sequence — tokens, components, patterns, guidelines.
Run the design_system creation sequence: tokens, components, patterns, guidelines.
Gap: → playbook:experience-ux-domain-only