| name | team-frontend |
| description | 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". |
| allowed-tools | ["AskUserQuestion","Bash","Edit","Glob","Grep","Read","SendMessage","WebFetch","WebSearch","Write","mcp__maestro__team_msg","teammate","todo"] |
| session-mode | run |
<required_reading>
@~/.maestro/workflows/run-mode-lite.md
</required_reading>
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
Pre-load (coordinator, before dispatch)
- Codebase docs: If
.workflow/codebase/ARCHITECTURE.md exists, read for module boundaries
- Specs (coding):
maestro load --type spec --category coding — load coding constraints as shared context
- Specs (ui):
maestro load --type spec --category ui — load ui constraints as shared context
- Wiki knowledge:
maestro search "frontend component UI" --json — top 5 entries as prior context
- All optional — proceed without if unavailable
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:
{run_dir}/work/team/
- CLI tools:
maestro delegate --mode analysis (read-only), maestro delegate --mode write (modifications)
- Message bus:
mcp__maestro__team_msg(session_id=<run-id>, ...)
Worker Spawn Template
Coordinator spawns workers using this template:
teammate({ agent: "team-worker", name: "<role>", description: "Spawn <role> worker", context: "fresh" })
User Commands
| Command | Action |
|---|
check / status | View execution status graph |
resume / continue | Advance to next step |
Session Directory
{run_dir}/work/team/
├── .msg/
│ ├── messages.jsonl # Message bus log
│ └── meta.json # Session state + cross-role state
├── task-analysis.json # Coordinator analyze output
├── wisdom/ # Cross-task knowledge
├── {run_dir}/outputs/analysis/ # Analyst output
│ ├── design-intelligence.json
│ └── requirements.md
├── {run_dir}/outputs/architecture/ # Architect output
│ ├── design-tokens.json
│ ├── component-specs/
│ └── project-structure.md
├── {run_dir}/outputs/qa/ # QA output
│ └── audit-<NNN>.md
└── {run_dir}/outputs/build/ # Developer output
Specs Reference
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 |
