z-design-brief
Design brief
Walk the idea's UI one screen at a time — what it shows, what the user can click or act on, what states each element has, how screens connect — then write the brief to docs/design/<slug>-brief.md. Same interview discipline as [[z-grill-with-docs]]: one question per turn, option cases with a marked recommended answer. Use the host's available question tool for structured choices within its supported schema; fall back to concise prose when unavailable.
Screen inventory
List every screen the idea implies — including the auth, empty, error, and settings screens briefs usually forget. Reuse an already-approved inventory. Resolve missing or changed screens before descending into them; use multi-select only when the host question tool supports it.
Per screen
Resolve in order, one screen at a time; finish a screen before opening the next.
- Purpose — the one job this screen does; if it has two, it may be two screens.
- Shows — data and content, where it comes from, what empty and loading look like.
- Actions — every clickable or actionable element; for each: label, effect, destination, failure behavior.
- States — per element: default, disabled, loading, error; hover/focus where it matters.
- Transitions — what leads here, where each action leads, what back does.