Team Frontend Development
Unified team skill: frontend development with built-in ui-ux-pro-max design intelligence. Covers requirement analysis, design system generation, frontend implementation, and quality assurance. Built on team-worker agent architecture — all worker roles share a single agent definition with role-specific Phase 2-4 loaded from role.md specs.
Architecture
Skill(skill="team-frontend", args="task description")
|
SKILL.md (this file) = Router
|
+--------------+--------------+
| |
no --role flag --role <name>
| |
Coordinator Worker
roles/coordinator/role.md roles/<name>/role.md
|
+-- analyze -> dispatch -> spawn workers -> STOP
|
+-------+-------+-------+
v v v v
[analyst] [architect] [developer] [qa]
(team-worker agents, each loads roles/<role>/role.md)
Role Registry
| Role |
Path |
Prefix |
Inner Loop |
| coordinator |
roles/coordinator/role.md |
— |
— |
| analyst |
roles/analyst/role.md |
ANALYZE-* |
false |
| architect |
roles/architect/role.md |
ARCH-* |
false |
| developer |
roles/developer/role.md |
DEV-* |
true |
| qa |
roles/qa/role.md |
QA-* |
false |
Role Router
Parse $ARGUMENTS:
- Has
--role <name> → Read roles/<name>/role.md, execute Phase 2-4
- No
--role → @roles/coordinator/role.md, execute entry router
Shared Constants
- Session prefix:
FE
- Session path:
.workflow/.team/FE-<slug>-<date>/
- CLI tools:
ccw cli --mode analysis (read-only), ccw cli --mode write (modifications)
- Message bus:
mcp__ccw-tools__team_msg(session_id=<session-id>, ...)
Worker Spawn Template
Coordinator spawns workers using this template:
Agent({
subagent_type: "team-worker",
description: "Spawn <role> worker",
team_name: "frontend",
name: "<role>",
run_in_background: true,
prompt: `## Role Assignment
role: <role>
role_spec: <skill_root>/roles/<role>/role.md
session: <session-folder>
session_id: <session-id>
team_name: frontend
requirement: <task-description>
inner_loop: <true|false>
## Progress Milestones
session_id: <session-id>
Report progress via team_msg at natural phase boundaries (context loaded -> core work done -> verification).
Report blockers immediately via team_msg type="blocker".
Report completion via team_msg type="task_complete" after final SendMessage.
Read role_spec file (@<skill_root>/roles/<role>/role.md) 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 |
Session Directory
.workflow/.team/FE-<slug>-<YYYY-MM-DD>/
├── .msg/
│ ├── messages.jsonl # Message bus log
│ └── meta.json # Session state + cross-role state
├── task-analysis.json # Coordinator analyze output
├── wisdom/ # Cross-task knowledge
├── analysis/ # Analyst output
│ ├── design-intelligence.json
│ └── requirements.md
├── architecture/ # Architect output
│ ├── design-tokens.json
│ ├── component-specs/
│ └── project-structure.md
├── qa/ # QA output
│ └── audit-<NNN>.md
└── build/ # Developer output
Specs Reference
- specs/pipelines.md — Pipeline definitions and task registry
Error Handling
| Scenario |
Resolution |
| Unknown command |
Error with available command list |
| Role not found |
Error with role registry |
| QA score < 6 over 2 GC rounds |
Escalate to user |
| ui-ux-pro-max unavailable |
Degrade to LLM general design knowledge |
| Worker no response |
Report waiting task, suggest user resume |
| Pipeline deadlock |
Check blockedBy chain, report blocking point |
1---2name: team-frontend-23description: Unified team skill for frontend development. Pure router — all roles read this file. Beat model is coordinator-only in monitor.md. Built-in ui-ux-pro-max design intelligence. Triggers on "team frontend".4allowed-tools: Agent(*), TaskCreate(*), TaskList(*), TaskGet(*), TaskUpdate(*), TeamCreate(*), TeamDelete(*), SendMessage(*), AskUserQuestion(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), WebFetch(*), WebSearch(*), mcp__ace-tool__search_context(*), mcp__ccw-tools__team_msg(*)5metadata:6 source: https://skillmd.com/skills/catlog22/team-frontend-27---89# Team Frontend Development1011Unified team skill: frontend development with built-in ui-ux-pro-max design intelligence. Covers requirement analysis, design system generation, frontend implementation, and quality assurance. Built on **team-worker agent architecture** — all worker roles share a single agent definition with role-specific Phase 2-4 loaded from role.md specs.1213## Architecture1415```16Skill(skill="team-frontend", args="task description")17 |18 SKILL.md (this file) = Router19 |20 +--------------+--------------+21 | |22 no --role flag --role <name>23 | |24 Coordinator Worker25 roles/coordinator/role.md roles/<name>/role.md26 |27 +-- analyze -> dispatch -> spawn workers -> STOP28 |29 +-------+-------+-------+30 v v v v31 [analyst] [architect] [developer] [qa]32 (team-worker agents, each loads roles/<role>/role.md)33```3435## Role Registry3637| Role | Path | Prefix | Inner Loop |38|------|------|--------|------------|39| coordinator | [roles/coordinator/role.md](roles/coordinator/role.md) | — | — |40| analyst | [roles/analyst/role.md](roles/analyst/role.md) | ANALYZE-* | false |41| architect | [roles/architect/role.md](roles/architect/role.md) | ARCH-* | false |42| developer | [roles/developer/role.md](roles/developer/role.md) | DEV-* | true |43| qa | [roles/qa/role.md](roles/qa/role.md) | QA-* | false |4445## Role Router4647Parse `$ARGUMENTS`:48- Has `--role <name>` → Read `roles/<name>/role.md`, execute Phase 2-449- No `--role` → `@roles/coordinator/role.md`, execute entry router5051## Shared Constants5253- **Session prefix**: `FE`54- **Session path**: `.workflow/.team/FE-<slug>-<date>/`55- **CLI tools**: `ccw cli --mode analysis` (read-only), `ccw cli --mode write` (modifications)56- **Message bus**: `mcp__ccw-tools__team_msg(session_id=<session-id>, ...)`5758## Worker Spawn Template5960Coordinator spawns workers using this template:6162```63Agent({64 subagent_type: "team-worker",65 description: "Spawn <role> worker",66 team_name: "frontend",67 name: "<role>",68 run_in_background: true,69 prompt: `## Role Assignment70role: <role>71role_spec: <skill_root>/roles/<role>/role.md72session: <session-folder>73session_id: <session-id>74team_name: frontend75requirement: <task-description>76inner_loop: <true|false>7778## Progress Milestones79session_id: <session-id>80Report progress via team_msg at natural phase boundaries (context loaded -> core work done -> verification).81Report blockers immediately via team_msg type="blocker".82Report completion via team_msg type="task_complete" after final SendMessage.8384Read role_spec file (@<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions.85Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5 (report).`86})87```8889## User Commands9091| Command | Action |92|---------|--------|93| `check` / `status` | View execution status graph |94| `resume` / `continue` | Advance to next step |9596## Session Directory9798```99.workflow/.team/FE-<slug>-<YYYY-MM-DD>/100├── .msg/101│ ├── messages.jsonl # Message bus log102│ └── meta.json # Session state + cross-role state103├── task-analysis.json # Coordinator analyze output104├── wisdom/ # Cross-task knowledge105├── analysis/ # Analyst output106│ ├── design-intelligence.json107│ └── requirements.md108├── architecture/ # Architect output109│ ├── design-tokens.json110│ ├── component-specs/111│ └── project-structure.md112├── qa/ # QA output113│ └── audit-<NNN>.md114└── build/ # Developer output115```116117## Specs Reference118119- [specs/pipelines.md](specs/pipelines.md) — Pipeline definitions and task registry120121## Error Handling122123| Scenario | Resolution |124|----------|------------|125| Unknown command | Error with available command list |126| Role not found | Error with role registry |127| QA score < 6 over 2 GC rounds | Escalate to user |128| ui-ux-pro-max unavailable | Degrade to LLM general design knowledge |129| Worker no response | Report waiting task, suggest user `resume` |130| Pipeline deadlock | Check blockedBy chain, report blocking point |