# Design prompts — ready-to-send design briefs

> One brief per screen/feature that has **no prototype source** and must be designed before it can be reconstructed. Source of truth for *what* needs design: [`DESIGN_BACKLOG.md`](DESIGN_BACKLOG.md) (authoritative for lifecycle status). Briefs are authored by the **`design-prompt-authoring`** skill from the §J template (`PROMPT_TEMPLATES.md`).
>
> **Single writer (Law 3):** only the orchestrator edits this file.
>
> **Every brief serves BOTH design lanes** — the same brief is the prompt either way:
> - **In-repo lane:** `/design-build <DB-id>` hands the Global preamble + the row's brief block to the `design-builder` agent. No copy/paste, no download; provenance + contract sidecar recorded at birth.
> - **Console lane:** copy the **Global preamble** once, append the row's **brief block**, send to the design tool (Claude Design or equivalent) — batch a module's rows into one session. On delivery, ingest with **`/promote-design <delivery>`** (never hand-place files; never run a drift sweep over an expected delivery).

---

## Global preamble (authored once per project — prepend to every console-lane brief; passed verbatim to `design-builder`)

<!-- Authored by the design-prompt-authoring skill from CLAUDE.md. It carries, single-sourced:
  - the design-system law: token rules (never raw values), the page scaffolds, the hard prohibitions
    (no width-cap wrapper, no native controls where a DS component exists, no new tokens/classes/patterns,
    the modal-dismissal rule), the voice;
  - the continuity invariants every screen must satisfy (no dead-end / no orphan /
    guarded-disabled-with-reason / draft-resumable);
  - the compliance hooks for sensitive writes (identity confirmation, audit, permission gate);
  - the OUTPUT CONTRACT: (1) one prototype screen file in the project's prototype file pattern —
    addable to the prototype directory and wirable into the entry point + route resolver with no build
    step, using ONLY tokens/components already present in the prototype; AND (2) its contract sidecar
    `<screen-file>.uimap.json` per the contract-sidecar skill — route, entities+fields, every CTA with
    guard/destination/effect, states, role gates, list params. The sidecar must describe exactly what
    the file renders. A delivery without its sidecar is incomplete.
-->

---

## Index

| # | ID | Module | Screen / Feature | Scaffold | Severity | Workflow | Lane | Status |
|---|---|---|---|---|---|---|---|---|
| | | | | | | | | |

---

## Briefs (one block per `☐` row — §J template, severity order: Must-have first)