Agent skill

Team Frontend

by catlog22 in catlog22/Claude-Code-Workflow

Unified team skill for frontend development. An agent skill from catlog22/Claude-Code-Workflow.

MITAuto-check: notesFrontend & Design

Install Team Frontend

skills CLI
$ npx skills add catlog22/Claude-Code-Workflow --skill team-frontend -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install catlog22/Claude-Code-Workflow team-frontend --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/team-frontend .claude/skills/team-frontend && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
team-frontend
GitHub stars
2.1k
Token cost
~2.1k tokens
SKILL.md length
585 words
Files
11
Skills in repo
82
Repo updated
First seen
Licence
MIT

At a glance

Unified team skill for frontend development. An agent skill from catlog22/Claude-Code-Workflow.

  • Tasks that involve Frontend development
  • SKILL.md covers Architecture, Role Registry, Role Router and Delegation Lock, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve UI design

What it does

Team Frontend is an agent skill from catlog22/Claude-Code-Workflow. 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".

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 18 other files (for example `roles/analyst/role.md`, `roles/architect/role.md` and `roles/coordinator/commands/analyze.md`).

It sits in Frontend & Design, covering Frontend development and UI design. The repository describes itself as: JSON-driven multi-agent cadence-team development framework with intelligent CLI orchestration (Gemini/Qwen/Codex), context-first architecture, and automated workflow execution. The licence is MIT.

When your agent uses it

  • Tasks that involve Frontend development
  • Tasks that involve UI design

Example prompts

  • “team frontend”
  • “/team-frontend”

Requirements

  • Pre-approved tools (allowed-tools): spawn_agent(*), wait_agent(*), send_message(*), followup_task(*), close_agent(*), list_agents(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), WebFetch(*), WebSearch(*), mcp__ace-tool__search_context(*), mcp__ccw-tools__team_msg(*)

What it can do on your machine

Read from SKILL.md and the folder at commit 07491b0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • spawn_agent(*)
    • wait_agent(*)
    • send_message(*)
    • followup_task(*)
    • close_agent(*)
    • list_agents(*)
    • report_agent_job_result(*)
    • request_user_input(*)
    • Read(*)
    • Write(*)

    …and 8 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Team Frontend loads about 2.1k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 585 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: spawn_agent(*), wait_agent(*), send_message(*), followup_task(*), close_agent(*), list_agents(*), re

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from catlog22/Claude-Code-Workflow at commit 07491b0, republished under its MIT licence (© catlog22). 585 words, ~2,147 tokens.

Download SKILL.mdSave it as .claude/skills/team-frontend/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
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
spawn_agent(*), wait_agent(*), send_message(*), followup_task(*), close_agent(*), list_agents(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), WebFetch(*), WebSearch(*), mcp__ace-tool__search_context(*), mcp__ccw-tools__team_msg(*)

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

RolePathPrefixInner Loop
coordinatorroles/coordinator/role.md——
analystroles/analyst/role.mdANALYZE-*false
architectroles/architect/role.mdARCH-*false
developerroles/developer/role.mdDEV-*true
qaroles/qa/role.mdQA-*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

Delegation Lock

Coordinator is a PURE ORCHESTRATOR. It coordinates, it does NOT do.

Before calling ANY tool, apply this check:

Tool CallVerdictReason
spawn_agent, wait_agent, close_agent, send_message, followup_taskALLOWEDOrchestration
list_agentsALLOWEDAgent health check
request_user_inputALLOWEDUser interaction
mcp__ccw-tools__team_msgALLOWEDMessage bus
Read/Write on .workflow/.team/ filesALLOWEDSession state
Read on roles/, commands/, specs/ALLOWEDLoading own instructions
Read/Grep/Glob on project source codeBLOCKEDDelegate to worker
Edit on any file outside .workflow/BLOCKEDDelegate to worker
Bash("ccw cli ...")BLOCKEDOnly workers call CLI
Bash running build/test/lint commandsBLOCKEDDelegate to worker

If a tool call is BLOCKED: STOP. Create a task, spawn a worker.

No exceptions for "simple" tasks. Even a single-file read-and-report MUST go through spawn_agent.


Shared Constants

  • Session prefix: FE
  • Session path: .workflow/.team/FE-<date>-<slug>/
  • 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:

spawn_agent({
  agent_type: "team_worker",
  task_name: "<task-id>",
  fork_turns: "none",
  message: `## Role Assignment
role: <role>
role_spec: <skill_root>/roles/<role>/role.md
session: <session-folder>
session_id: <session-id>
requirement: <task-description>
inner_loop: <true|false>

Read role_spec file (<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions.

## Task Context
task_id: <task-id>
title: <task-title>
description: <task-description>
pipeline_phase: <pipeline-phase>

## Upstream Context
<prev_context>`
})

After spawning, use wait_agent({ timeout_ms: 1800000 }) to collect results. If result.timed_out, send STATUS_CHECK via followup_task (wait 3 min), then FINALIZE with interrupt (wait 3 min), then mark timed_out and close agents. Use close_agent({ target }) each worker.

Model Selection Guide
Rolemodelreasoning_effortRationale
Analyst (ANALYZE-*)(default)highDesign intelligence requires deep UI/UX reasoning
Architect (ARCH-*)(default)highComponent spec and design token generation needs precision
Developer (DEV-*)(default)highFrontend code generation needs full reasoning
QA (QA-*)(default)high5-dimension audit requires thorough analysis

Override model/reasoning_effort in spawn_agent when cost optimization is needed:

spawn_agent({
  agent_type: "team_worker",
  task_name: "<task-id>",
  fork_turns: "none",
  model: "<model-override>",
  reasoning_effort: "<effort-level>",
  message: "..."
})

User Commands

CommandAction
check / statusView execution status graph
resume / continueAdvance to next step
Show full SKILL.md (235 more words)Show less

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

v4 Agent Coordination

Message Semantics
IntentAPIExample
Send architecture specs to running developersend_messageQueue design tokens and component specs to DEV-*
Not used in this skillfollowup_taskNo resident agents -- all workers are one-shot
Check running agentslist_agentsVerify agent health during resume
Pipeline Pattern

Sequential pipeline with GC loops: analyst -> architect -> developer -> QA. In system mode, architect revision (ARCH-002) and developer (DEV-001) may run in parallel after QA-001 arch review.

fork_turns Consideration

Developer workers (DEV-*) benefit from fork_turns: "all" when the coordinator has accumulated significant design context (analysis results, architecture specs, design tokens). This avoids the developer needing to re-read all upstream artifacts:

// Consider fork_turns: "all" for developer in feature/system modes
spawn_agent({
  agent_type: "team_worker",
  task_name: "DEV-001",
  fork_turns: "all",  // Developer gets full coordinator context including design decisions
  message: "..."
})
GC Loop (QA Fix Cycle)

QA may flag FIX_REQUIRED, creating DEV-fix + QA-recheck tasks (max 2 rounds). If QA score remains < 6 after 2 rounds, escalate to user.

Agent Health Check

Use list_agents({}) in handleResume and handleComplete:

// Reconcile session state with actual running agents
const running = list_agents({})
// Compare with tasks.json active_agents
// Reset orphaned tasks (in_progress but agent gone) to pending
Named Agent Targeting

Workers are spawned with task_name: "<task-id>" enabling direct addressing:

  • send_message({ target: "DEV-001", message: "..." }) -- queue architecture specs to running developer
  • close_agent({ target: "ARCH-001" }) -- cleanup by name after completion

Error Handling

ScenarioResolution
Unknown commandError with available command list
Role not foundError with role registry
QA score < 6 over 2 GC roundsEscalate to user
ui-ux-pro-max unavailableDegrade to LLM general design knowledge
Worker no responseReport waiting task, suggest user resume
Pipeline deadlockCheck blockedBy chain, report blocking point

© catlog22, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files in .codex/skills/team-frontend of catlog22/Claude-Code-Workflow.

  • SKILL.md
  • roles/analyst/role.md
  • roles/architect/role.md
  • roles/coordinator/commands/analyze.md
  • roles/coordinator/commands/dispatch.md
  • roles/coordinator/commands/monitor.md
  • roles/coordinator/role.md
  • roles/developer/role.md
  • roles/qa/role.md
  • specs/pipelines.md
  • specs/team-config.json

Open the folder on GitHubat commit 07491b0

Compare with similar skills

Team Frontend next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Team Frontend compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Team Frontend this skillcatlog22/Claude-Code-Workflow2.1k—~2.1kAutomated safety check: NotesMIT
Senior FrontendOhh-889/skyroc7952 repos~1.1kAutomated safety check: NotesMIT
Userinterface Wikiraphaelsalaja/userinterface-wiki906—~3.5kAutomated safety check: PassMIT
UI Design Braincarmahhawwari/ui-design-brain893—~2.1kAutomated safety check: PassMIT
Variate Design VariationsNutlope/variate211—~3.5kAutomated safety check: PassMIT
Design-Led Website Builderliucongg/liucong-skills248—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • Senior Frontend

    Ohh-889/skyroc

    Comprehensive frontend development skill for building modern, performant web applications using ReactJS, NextJS, TypeScript, Tailwind CSS.

    795 GitHub starsUsed in 2 repos~1.1k tokens
    Frontend & DesignAuto-check: notes
  • Userinterface Wiki

    raphaelsalaja/userinterface-wiki

    UI/UX best practices for web interfaces. An agent skill from raphaelsalaja/userinterface-wiki.

    906 GitHub stars~3.5k tokensUpdated 2 mo ago
    Frontend & DesignAuto-check passed
  • UI Design Brain

    carmahhawwari/ui-design-brain

    Generate production-grade UI using real component patterns and best practices from 60+ documented interface components.

    893 GitHub stars~2.1k tokensUpdated 7 mo ago
    Frontend & DesignAuto-check passed
  • Puts four real design variations of one project file on your localhost behind a small card you flip with the arrow keys, then acts on your verdict.

    211 GitHub stars~3.5k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check passed
  • Design-Led Website Builder

    liucongg/liucong-skills

    Turns a short brief into a researched, distinctive website: lock the intent with at most one question, research live reference sites, source materials, then build and verify.

    248 GitHub stars~1.3k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check passed
  • UI Aesthetics Judgment

    kasonye/ui-aesthetics-skill

    Sets rules for web UI work that favor hierarchy, spacing and restrained styling, with routes for generating, reviewing and polishing interfaces.

    384 GitHub stars~3.2k tokensUpdated 5 mo ago
    Frontend & DesignAuto-check passed

More from catlog22/Claude-Code-Workflow

All 82 skills in this repo
  • Prompt Generator

    catlog22/Claude-Code-Workflow

    Generate or convert Claude Code prompt files — command orchestrators, skill files, agent role definitions, or style conversion of existing files.

    2.1k GitHub starsUsed in 1 repo~4.7k tokens
    Auto-check: notes
  • Ccw Help

    catlog22/Claude-Code-Workflow

    CCW command help system. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed
  • Team Ultra Analyze

    catlog22/Claude-Code-Workflow

    Deep collaborative analysis team skill. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub starsUsed in 1 repo~2.4k tokens
    Auto-check: notes
  • Brainstorm

    catlog22/Claude-Code-Workflow

    Unified brainstorming skill with dual-mode operation — auto mode (framework generation, parallel multi-role analysis, cross-role synthesis) and single role analysis.

    2.1k GitHub stars~4.8k tokensUpdated 3 mo ago
    Auto-check: notes
  • Ccw Chain

    catlog22/Claude-Code-Workflow

    Chain-based CCW workflow orchestrator. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~1.1k tokensUpdated 3 mo ago
    Auto-check: notes
  • Delegation Check

    catlog22/Claude-Code-Workflow

    Check workflow delegation prompts against agent role definitions for content separation violations.

    2.1k GitHub stars~2.8k tokensUpdated 3 mo ago
    Auto-check: notes

Questions about Team Frontend

What does Team Frontend do?

Unified team skill for frontend development. An agent skill from catlog22/Claude-Code-Workflow. Team Frontend is an agent skill from catlog22/Claude-Code-Workflow. Unified team skill for frontend development.

When should I use Team Frontend?

Team Frontend fits situations like: tasks that involve Frontend development; tasks that involve UI design.

How do I install Team Frontend in Claude Code?

Run `npx skills add catlog22/Claude-Code-Workflow --skill team-frontend -a claude-code`. Or copy the skill folder (.codex/skills/team-frontend in catlog22/Claude-Code-Workflow) into .claude/skills/team-frontend in your project. Claude Code loads it when a task matches its description.

How do I install Team Frontend in Codex?

Run `npx skills add catlog22/Claude-Code-Workflow --skill team-frontend -a codex`. Or copy the skill folder (.codex/skills/team-frontend in catlog22/Claude-Code-Workflow) into .agents/skills/team-frontend in your project. Codex loads it when a task matches its description.

Can I use Team Frontend in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add catlog22/Claude-Code-Workflow --skill team-frontend -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/team-frontend, .gemini/skills/team-frontend, .github/skills/team-frontend and .opencode/skills/team-frontend in your project.

What does Team Frontend need to run?

SKILL.md names no scripts, command-line tools or credentials: Team Frontend is instructions for the agent only. Its frontmatter pre-approves these tools: spawn_agent(*), wait_agent(*), send_message(*), followup_task(*), close_agent(*), list_agents(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), WebFetch(*), WebSearch(*), mcp__ace-tool__search_context(*), mcp__ccw-tools__team_msg(*).

Does Team Frontend access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Team Frontend safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Team Frontend use?

Team Frontend is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Team Frontend use?

About 2.1k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Team Frontend?

Skills that share tags, products or a category with Team Frontend: Senior Frontend (Ohh-889/skyroc, 795 stars), Userinterface Wiki (raphaelsalaja/userinterface-wiki, 906 stars), UI Design Brain (carmahhawwari/ui-design-brain, 893 stars) and Variate Design Variations (Nutlope/variate, 211 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Team Frontend?

catlog22 (a GitHub user) maintains it in catlog22/Claude-Code-Workflow, which has 2,130 GitHub stars. The repository holds 82 skills in this directory. The repository was last updated on June 18, 2026.

Source: catlog22/Claude-Code-Workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.