design-council

# Design Council — selected seats, one accountable applier Run only when `pnpm design:route` returns `council.required=true`. Local visual work, spacing/layout repairs, responsive fixes, interaction-state fixes, motion tuning, topology gesture work, and copy do not acquire a council merely because they are UI. The council reviews one built direction and its proof packet. Run `/design-directions` first only when the route says `directions=yes`. ## Roster | Agent | Seat | Atlas ownership | |---|---|---| | `design-lead` | Lead Product Designer | primary Atlas fact/action and attention | | `design-system` | Design Systems Engineer | tokens, primitives, markers, and gates | | `design-interaction` | Interaction Designer | inspect, correct, confirm, reverse, keyboard | | `design-motion` | Motion / Action Designer | temporal meaning and reduced motion | | `design-infoviz` | Information Visualization Designer | topology mark → typed fact | | `design-workbench` | macOS Workbench Designer | installed window and WKWebView | | `design-responsive` | Responsive & Touch Designer | measured bands, input mode, safe area | | `design-handoff` | Agent Handoff Designer | state-bound MCP and CLI continuation | No seat always attends. Use exactly the seats returned by the router; structural routes derive at least two contrasting seats. `design-guardian` is not a seat. It is the accountable decider and applier. Seat briefs live at `../../agents/design-*.md`. The path resolves inside each mirror...