Audit and Refactor a Design System

Use this play at the start of any design system work session. It orients you in the current state of the system before any decisions are made, and prevents a model from acting on stale context or making decisions that conflict with prior choices. **Step 1 — Read the living brief:** Read `LIVING_BRIEF.md` from the project root. Summarize: - The product identity (one sentence) - The key decisions already recorded, by area - The current state: what components exist, what is stubbed, what is missing - Any open questions **Step 2 — Confirm scope for this session:** What is the goal of this session? State it explicitly before beginning work. If the scope conflicts with an existing decision in the living brief, flag the conflict and resolve it before proceeding. Planned scope for this session: [Describe what you intend to work on — e.g. "implement the Button component", "generate dark mode tokens", "add the Modal component spec"] **Step 3 — Identify relevant synthesis documents:** Based on the planned scope, identify which synthesis documents are relevant. Load only what is needed for this session's work. Relevant synthesis documents may include: - Token architecture: `/raw/principles/tokens/architecture` - Color architecture: `/raw/principles/color/architecture` - Typography architecture: `/raw/principles/typography/architecture` - Spacing and layout: `/raw/principles/spacing/layout` - Shape architecture: `/raw/principles/shape/architecture` - Accessibility floor: `/raw/principles/accessibility/floor` - Motion architecture: `/raw/principles/motion/architecture` **Step 4 — Confirm readiness:** State: "Ready to begin. Current system state: [one-sentence summary]. Session goal: [goal]. Relevant documents loaded: [list]." Do not begin work until this confirmation is produced. ---