Team UI Design

Systematic UI design pipeline: research -> design tokens -> review -> implementation. Built on

team-worker agent architecture

— all worker roles share a single agent definition with role-specific Phase 2-4 loaded from

roles//role.md

.

Architecture

Skill(skill="team-uidesign", args="task description")

|

SKILL.md (this file) = Router

|

+--------------+--------------+

| |

no --role flag --role

| |

Coordinator Worker

roles/coordinator/role.md roles//role.md

|

+-- analyze → dispatch → spawn workers → STOP

|

+-------+-------+-------+-------+

v v v v

[team-worker agents, each loads roles//role.md]

researcher designer reviewer implementer

Role Registry

Role

Path

Prefix

Inner Loop

coordinator

roles/coordinator/role.md

—

—

researcher

roles/researcher/role.md

RESEARCH-*

false

designer

roles/designer/role.md

DESIGN-*

false

reviewer

roles/reviewer/role.md

AUDIT-*

false

implementer

roles/implementer/role.md

BUILD-*

false

Role Router

Parse

$ARGUMENTS

:

Has

--role

→ Read

roles//role.md

, execute Phase 2-4

No

--role

→ Read

roles/coordinator/role.md

, execute entry router

Shared Constants

Session prefix

:

UDS

Session path

:

.workflow/.team/UDS--/

CLI tools

:

ccw cli --mode analysis

(read-only),

ccw cli --mode write

(modifications)

Message bus

:

mcp__ccw-tools__team_msg(session_id=, ...)

Max GC rounds

2 Worker Spawn Template Coordinator spawns workers using this template: Agent({ subagent_type: "team-worker", description: "Spawn worker for ", team_name: "uidesign", name: "", run_in_background: true, prompt: ## Role Assignment role: <role> role_spec: ~ or <project>/.claude/skills/team-uidesign/roles/<role>/role.md session: <session-folder> session_id: <session-id> team_name: uidesign requirement: <task-description> inner_loop: false Read role_spec file to load Phase 2-4 domain instructions. Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5 (report). }) User Commands Command Action check / status View execution status graph resume / continue Advance to next step Specs Reference specs/pipelines.md — Pipeline definitions and task registry Session Directory .workflow/.team/UDS--/ ├── .msg/ │ ├── messages.jsonl # Team message bus │ └── meta.json # Pipeline config + GC state ├── research/ # Researcher output │ ├── design-system-analysis.json │ ├── component-inventory.json │ ├── accessibility-audit.json │ └── design-intelligence.json ├── design/ # Designer output │ ├── design-tokens.json │ ├── component-specs/ │ └── layout-specs/ ├── audit/ # Reviewer output │ └── audit-*.md ├── build/ # Implementer output │ ├── token-files/ │ └── component-files/ └── wisdom/ # Cross-task knowledge Error Handling Scenario Resolution Unknown command Error with available command list Role not found Error with role registry Session corruption Attempt recovery, fallback to manual Fast-advance conflict Coordinator reconciles on next callback Completion action fails Default to Keep Active GC loop stuck > 2 rounds Escalate to user: accept / retry / terminate