Agent skill

Team Frontend Debug

by catlog22 in catlog22/Claude-Code-Workflow

Frontend debugging team using Chrome DevTools MCP. An agent skill from catlog22/Claude-Code-Workflow.

MITAuto-check: notesTesting & QA

Install Team Frontend Debug

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

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

GitHub CLI
$ gh skill install catlog22/Claude-Code-Workflow team-frontend-debug --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-debug .claude/skills/team-frontend-debug && 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-debug
GitHub stars
2.1k
Token cost
~2.8k tokens
SKILL.md length
738 words
Files
12
Skills in repo
82
Repo updated
First seen
Licence
MIT

At a glance

Frontend debugging team using Chrome DevTools MCP. An agent skill from catlog22/Claude-Code-Workflow.

  • Works in 4 steps: Run Bash({ command: "pwd" }) → capture… → skill_root =… → Store in team-session.json → …
  • Team-frontend-debug
  • SKILL.md covers Architecture, Pipeline Modes, Role Registry and Role Router, plus 11 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Team Frontend Debug is an agent skill from catlog22/Claude-Code-Workflow. Frontend debugging team using Chrome DevTools MCP. Dual-mode — feature-list testing or bug-report debugging. Triggers on "team-frontend-debug", "frontend debug".

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

It sits in Testing & QA, covering Browser testing, Debugging and QA and bug reports. It works with Chrome DevTools and Model Context Protocol. 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

  • Team-frontend-debug
  • Tasks that involve Browser testing
  • Tasks that involve Debugging

Example prompts

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

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(*), mcp__chrome-devtools__*(*), mcp__ccw-tools__team_msg(*)

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Run Bash({ command: "pwd" }) → capture project_root (absolute path)
  2. skill_root = /.claude/skills/team-frontend-debug
  3. Store in team-session.json
  4. All worker role_spec values MUST use /roles//role.md (absolute)

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 6 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 (its code samples are json).

    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 Debug loads about 2.8k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 738 words of instructions outside code blocks.

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

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). 738 words, ~2,760 tokens.

Download SKILL.mdSave it as .claude/skills/team-frontend-debug/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
team-frontend-debug
description
Frontend debugging team using Chrome DevTools MCP. Dual-mode — feature-list testing or bug-report debugging. Triggers on "team-frontend-debug", "frontend debug".
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(*), mcp__chrome-devtools__*(*), mcp__ccw-tools__team_msg(*)

Frontend Debug Team

Dual-mode frontend debugging: feature-list testing or bug-report debugging, powered by Chrome DevTools MCP.

Architecture

Skill(skill="team-frontend-debug", args="feature list or bug description")
                    |
         SKILL.md (this file) = Router
                    |
     +--------------+--------------+
     |                             |
  no --role flag              --role <name>
     |                             |
  Coordinator                  Worker
  roles/coordinator/role.md    roles/<name>/role.md
     |
     +-- analyze input → select pipeline → dispatch → spawn → STOP
                                    |
         ┌──────────────────────────┼──────────────────────┐
         v                         v                       v
    [test-pipeline]          [debug-pipeline]          [shared]
     tester(DevTools)        reproducer(DevTools)      analyzer
                                                       fixer
                                                       verifier

Pipeline Modes

InputPipelineFlow
Feature list / 功能清单test-pipelineTEST → ANALYZE → FIX → VERIFY
Bug report / 错误描述debug-pipelineREPRODUCE → ANALYZE → FIX → VERIFY

Role Registry

RolePathPrefixInner Loop
coordinatorroles/coordinator/role.md——
testerroles/tester/role.mdTEST-*true
reproducerroles/reproducer/role.mdREPRODUCE-*false
analyzerroles/analyzer/role.mdANALYZE-*false
fixerroles/fixer/role.mdFIX-*true
verifierroles/verifier/role.mdVERIFY-*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: TFD
  • Session path: .workflow/.team/TFD-<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>, ...)

Workspace Resolution

Coordinator MUST resolve paths at Phase 2 before spawning workers:

  1. Run Bash({ command: "pwd" }) → capture project_root (absolute path)
  2. skill_root = <project_root>/.claude/skills/team-frontend-debug
  3. Store in team-session.json:
    json
    { "project_root": "/abs/path/to/project", "skill_root": "/abs/path/to/skill" }
  4. All worker role_spec values MUST use <skill_root>/roles/<role>/role.md (absolute)

This ensures workers always receive an absolute, resolvable path regardless of their working directory.

Chrome DevTools MCP Tools

All browser inspection operations use Chrome DevTools MCP. Reproducer and Verifier are primary consumers.

ToolPurpose
mcp__chrome-devtools__navigate_pageNavigate to target URL
mcp__chrome-devtools__take_screenshotCapture visual state
mcp__chrome-devtools__take_snapshotCapture DOM/a11y tree
mcp__chrome-devtools__list_console_messagesRead console logs
mcp__chrome-devtools__get_console_messageGet specific console message
mcp__chrome-devtools__list_network_requestsMonitor network activity
mcp__chrome-devtools__get_network_requestInspect request/response detail
mcp__chrome-devtools__performance_start_traceStart performance recording
mcp__chrome-devtools__performance_stop_traceStop and analyze trace
mcp__chrome-devtools__clickSimulate user click
mcp__chrome-devtools__fillFill form inputs
mcp__chrome-devtools__hoverHover over elements
mcp__chrome-devtools__evaluate_scriptExecute JavaScript in page
mcp__chrome-devtools__wait_forWait for element/text
mcp__chrome-devtools__list_pagesList open browser tabs
mcp__chrome-devtools__select_pageSwitch active tab

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.

Show full SKILL.md (325 more words)Show less
Model Selection Guide

Debug workflows require tool-heavy interaction (Chrome DevTools MCP). Reasoning effort varies by role.

Rolereasoning_effortRationale
testermediumSystematic feature testing via DevTools, follows test plan
reproducermediumReproduce bugs via DevTools interaction steps
analyzerhighRoot cause analysis requires deep reasoning about evidence
fixerhighCode fixes must address root cause precisely
verifiermediumVerification follows defined success criteria via DevTools

User Commands

CommandAction
check / statusView execution status graph
resume / continueAdvance to next step
revise <TASK-ID> [feedback]Revise specific task
feedback <text>Inject feedback for revision
retry <TASK-ID>Re-run a failed task

v4 Agent Coordination

Message Semantics
IntentAPIExample
Queue supplementary info (don't interrupt)send_messageSend DevTools evidence to running analyzer
Assign new work / trigger debug roundfollowup_taskAssign re-fix after verification failure
Check running agentslist_agentsVerify agent health during resume
Agent Health Check

Use list_agents({}) in handleResume and handleComplete:

// Reconcile session state with actual running agents
const running = list_agents({})
// Compare with team-session.json active tasks
// 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: "ANALYZE-001", message: "..." }) -- send evidence from reproducer to analyzer
  • followup_task({ target: "FIX-001", message: "..." }) -- assign fix based on analysis results
  • close_agent({ target: "VERIFY-001" }) -- cleanup after verification
Iterative Debug Loop Pattern

When verifier reports a fix did not resolve the issue, coordinator uses followup_task to trigger re-analysis and re-fix:

// Verifier reports failure -> coordinator dispatches re-fix
followup_task({
  target: "FIX-001",   // reuse existing fixer if inner_loop, or spawn new
  message: `## Re-fix Assignment
verification_result: FAIL
failure_evidence: <verifier's screenshot/console evidence>
previous_fix_summary: <what was tried>
instruction: Analyze verification failure and apply corrected fix.`
})

This pattern enables iterative debug rounds: FIX -> VERIFY -> re-FIX -> re-VERIFY (max 3 rounds).

Completion Action

When pipeline completes, coordinator presents:

functions.request_user_input({
  questions: [{
    question: "Pipeline complete. What would you like to do?",
    header: "Completion",
    multiSelect: false,
    options: [
      { label: "Archive & Clean (Recommended)", description: "Archive session, clean up" },
      { label: "Keep Active", description: "Keep session for follow-up debugging" },
      { label: "Export Results", description: "Export debug report and patches" }
    ]
  }]
})

Specs Reference

Session Directory

.workflow/.team/TFD-<date>-<slug>/
├── team-session.json           # Session state + role registry
├── evidence/                   # Screenshots, snapshots, network logs
├── artifacts/                  # Test reports, RCA reports, patches, verification reports
├── wisdom/                     # Cross-task debug knowledge
└── .msg/                       # Team message bus

Error Handling

ScenarioResolution
All features pass testReport success, pipeline completes without ANALYZE/FIX/VERIFY
Bug not reproducibleReproducer reports failure, coordinator asks user for more details
Browser not availableReport error, suggest manual reproduction steps
Analysis inconclusiveAnalyzer requests more evidence via iteration loop
Fix introduces regressionVerifier reports fail, coordinator dispatches re-fix
No issues found in testSkip downstream tasks, report all-pass
Unknown commandError with available command list
Role not foundError with role registry

© 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 11 other files in .codex/skills/team-frontend-debug of catlog22/Claude-Code-Workflow.

  • SKILL.md
  • roles/analyzer/role.md
  • roles/coordinator/commands/analyze.md
  • roles/coordinator/commands/dispatch.md
  • roles/coordinator/commands/monitor.md
  • roles/coordinator/role.md
  • roles/fixer/role.md
  • roles/reproducer/role.md
  • roles/tester/role.md
  • roles/verifier/role.md
  • specs/debug-tools.md
  • specs/pipelines.md

Open the folder on GitHubat commit 07491b0

Compare with similar skills

Team Frontend Debug 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 Debug compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Team Frontend Debug this skillcatlog22/Claude-Code-Workflow2.1k—~2.8kAutomated safety check: NotesMIT
Extension Puppeteer Debuggingmengxi-ream/read-frog10k—~2kAutomated safety check: NotesGPL-3.0
Diff-Driven Smoke TestsSkyvern-AI/skyvern23k—~5.2kAutomated safety check: PassAGPL-3.0
Chrome Devtoolstech-leads-club/agent-skills7k—~1.3kAutomated safety check: PassMIT
Doctorbluzir/claude-code-design106—~931Automated safety check: PassNone
Chrome Devtools MCPmanagedcode/dotnet-skills486—~2.2kAutomated safety check: PassMIT

Similar skills

  • Extension Puppeteer Debugging

    mengxi-ream/read-frog

    Debug the built Read Frog extension in real Chrome. An agent skill from mengxi-ream/read-frog.

    10k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check: notes
  • Diff-Driven Smoke Tests

    Skyvern-AI/skyvern

    Reads your git diff, writes a handful of happy-path browser smoke tests, runs them with Skyvern or Chrome DevTools MCP and posts screenshot evidence to the PR.

    23k GitHub stars~5.2k tokensUpdated today
    Testing & QAAuto-check passed
  • Chrome Devtools

    tech-leads-club/agent-skills

    Browser debugging, performance profiling, and automation via Chrome DevTools MCP.

    7k GitHub stars~1.3k tokensUpdated 18 days ago
    Testing & QAAuto-check passed
  • Doctor

    bluzir/claude-code-design

    First-run setup + health check. An agent skill from bluzir/claude-code-design.

    106 GitHub stars~931 tokensUpdated 5 mo ago
    Testing & QAAuto-check passed
  • Chrome Devtools MCP

    managedcode/dotnet-skills

    Use Chrome DevTools MCP from .NET agents and .NET-focused repos to inspect, debug, and automate Chrome through an MCP client.

    486 GitHub stars~2.2k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Connects an agent to a real Chrome instance through the Chrome DevTools MCP server, so it can inspect the DOM, read console errors and profile performance directly.

    103k GitHub starsUsed in 4 repos~3.5k tokens
    Testing & QAAuto-check: warnings

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 Debug

What does Team Frontend Debug do?

Frontend debugging team using Chrome DevTools MCP. An agent skill from catlog22/Claude-Code-Workflow. Team Frontend Debug is an agent skill from catlog22/Claude-Code-Workflow. Frontend debugging team using Chrome DevTools MCP.

When should I use Team Frontend Debug?

Team Frontend Debug fits situations like: team-frontend-debug; tasks that involve Browser testing; tasks that involve Debugging.

How do I install Team Frontend Debug in Claude Code?

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

How do I install Team Frontend Debug in Codex?

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

Can I use Team Frontend Debug 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-debug -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-debug, .gemini/skills/team-frontend-debug, .github/skills/team-frontend-debug and .opencode/skills/team-frontend-debug in your project.

What does Team Frontend Debug need to run?

SKILL.md names no scripts, command-line tools or credentials: Team Frontend Debug 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(*), mcp__chrome-devtools__*(*), mcp__ccw-tools__team_msg(*).

Does Team Frontend Debug 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 Debug 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 Debug use?

Team Frontend Debug 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 Debug use?

About 2.8k tokens (SKILL.md is roughly 11k 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 Debug?

Skills that share tags, products or a category with Team Frontend Debug: Extension Puppeteer Debugging (mengxi-ream/read-frog, 10k stars), Diff-Driven Smoke Tests (Skyvern-AI/skyvern, 23k stars), Chrome Devtools (tech-leads-club/agent-skills, 7k stars) and Doctor (bluzir/claude-code-design, 106 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Team Frontend Debug?

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.