draft-designlisted

# /draft-design ## Preconditions - `spec/PRD.md` must exist - Project has a UI surface (marketing site, app UI, email, docs). Skip for pure-backend products. ## Init prompt When `/draft-design` runs the first time on a project, ask: > Do you have a design system to reference, or should I create one for this project? > > **A) Reference external** — point me at a URL, file path, or brand-book asset. The project's DESIGN.md will be generated *consistent with* that reference, but stored locally as a self-contained doc. > > **B) Create new** — I'll generate a self-contained palette, type scale, spacing, components, voice from your product requirements. Save the answer to `.forge/settings.yaml`: ```yaml design: mode: project_owned # project_owned | reference_external reference: <url-or-path> # only if mode = reference_external ``` ## Orchestration 1. Read PRD 2. Read `.forge/settings.yaml` for `design.mode` + `design.reference` 3. Check if user has a `ux-design`, `graphic-design`, or `frontend-design-pro` skill — invoke with PRD + reference (if any) as context 4. Determine project surface area (marketing site, app UI, email, docs) 5. Generate `spec/DESIGN.md` according to mode: - **project_owned** — write self-contained tokens, components, layouts, voice derived from product requirements - **reference_external** — read the reference, extract its guidelines (palette, type scale, spacing, voice register), write DESIGN.md *consistent with* it as a self-cont