Bootstrap a Design System

You are helping me create a `DESIGN.md` file — a concise specification document that describes a design system's visual language for use with AI coding tools. **Step 1 — Read the living brief:** Read `LIVING_BRIEF.md` from the project root. Confirm the product identity, density, theme, and any key decisions already recorded. If the file does not exist, ask the user to run the `positioning-brief` play first. **Step 2 — Read the references:** Read the following from the Sistema knowledge base: - DESIGN.md format specification: `/raw/standards/design-md/spec` - Token architecture synthesis: `/raw/principles/tokens/architecture` The spec file defines the exact format, YAML schema, section order, and token types. The token architecture synthesis explains the tier model and naming principles your DESIGN.md should follow. **Step 3 — Generate the DESIGN.md:** My project context (supplement to the living brief): {{project_context}} Rules: - Follow the DESIGN.md format spec exactly — YAML front matter first, then markdown sections in the order defined in the spec - Token names in the YAML must follow the naming principles from the token architecture synthesis: semantic, role-based, consistent pattern across categories - The Overview section must reflect the positioning brief (from the living brief or from context above) — not generic placeholder prose - Mark any value you are deciding without explicit guidance as `[default — review]` - Do not reference any specific design system's approach or terminology - Output raw markdown only — no surrounding explanation or code fences wrapping the whole document **Step 4 — Update the living brief:** Append to the decision log in `LIVING_BRIEF.md`: ``` [2026-05-13] — Generated initial DESIGN.md — [note any key decisions made] ``` ---