/design
DesignUser-invoked

Write UI specs at `docs/design/<feature>.md` — flows, empty/loading/error/success states, accessibility, and ui-kit component maps.

When to use

A PRD exists and screens or flows need a spec before /dev ships UI.

Prerequisites

  • A PRD or feature brief (tracker issue or chat draft).
  • UI work is in scope for this slice.

How to use

  1. Invoke /design and point at the PRD (e.g. PRD #42).
  2. Walk screens and flows — confirm empty, loading, error, and success states.
  3. Confirm the spec lands at `docs/design/<feature>.md` with `@polyms/ui-kit` maps.
  4. Hand off to /dev with the design path.

Done when

An engineering-ready UI spec exists under `docs/design/` covering flows, four states, a11y, and component maps.

Pipeline

Upstream
/align → /reqs or /to-prd
Downstream
/dev

Boundaries

Does not rewrite product scope (/reqs). Does not place code seams (`arch`). Does not document the ui-kit API (`/ui-kit` in the lib repo).

Tips

  • Long sessions: ask to use the `designer` agent.
  • Product scope changes belong in /reqs, not in the design pass.

Sample prompt

prompt
/design

PRD #42

Agent

PRINCIPAL DESIGNER

Owns: docs/design/, @polyms/ui-kit component maps

Use the designer to spec UI from PRD #42
designer
← Skill catalog