skills/frontend-qa/qa-coordinator/SKILL.md
Use when a user reports a frontend bug, visual defect, or unexpected behavior in a Next.js/TypeScript application. Orchestrates a multi-phase QA pipeline — component mapping, diagnosis, fix, and regression testing — by classifying symptoms and dispatching to the appropriate specialist skill. Does not perform diagnosis or fixes directly; delegates all domain work to specialists. Not for backend-only issues, infrastructure problems, or build/deployment failures.
npx skillsauth add dtsong/my-claude-setup qa-coordinatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Classify frontend bug symptoms, dispatch to the appropriate specialist skill, and orchestrate the MAP → DIAGNOSE → FIX → TEST pipeline with user confirmation between phases.
package.json, tsconfig.json, and project config files for stack detection.claude/qa-cache/project-config.jsonExtract route and symptom from user input. If ambiguous, ask one question.
Auto-detect the stack if no .claude/qa-cache/project-config.json exists: read package.json, detect framework/test/styling/state, check for app/ vs pages/, confirm with user, save config. Re-detect only when package.json changes.
| Symptom | Skill |
|---------|-------|
| Rendering, missing content, stale data, flicker | ui-bug-investigator |
| State not updating, form issues, toggle broken | ui-bug-investigator |
| Click/keyboard/focus broken, event issues | ui-bug-investigator |
| Data not loading, API errors, server actions | ui-bug-investigator |
| Hydration mismatch, RSC error, boundary issues | ui-bug-investigator |
| Layout broken, spacing, alignment, overflow | css-layout-debugger |
| Styling wrong, colors, dark mode, responsive | css-layout-debugger |
| Unclear/mixed | ui-bug-investigator first, then css-layout-debugger if styling root cause found |
| Skill | Path | Purpose | Model Tier |
|-------|------|---------|------------|
| Mapper | page-component-mapper/SKILL.md | Map route to component tree | haiku |
| UI Investigator | ui-bug-investigator/SKILL.md | Diagnose non-CSS UI bugs | sonnet |
| CSS Debugger | css-layout-debugger/SKILL.md | Diagnose CSS/layout/styling issues | sonnet |
| Fix & Verify | component-fix-and-verify/SKILL.md | Apply and verify diagnosed fix | sonnet |
| Test Generator | regression-test-generator/SKILL.md | Generate targeted regression test | sonnet |
Read ONLY the relevant specialist SKILL.md for the current phase. Never load multiple specialists simultaneously. Route silently — never present a skill menu.
Sequential four-phase pipeline. Pause for user confirmation between each phase.
MAP → Read page-component-mapper/SKILL.md. Output: ComponentMap artifact at .claude/qa-cache/component-maps/. Pause: "{N} components mapped. Continue?"
DIAGNOSE → Read classified specialist SKILL.md. Input: ComponentMap path + symptom + classification. Output: DiagnosisReport artifact. Pause: "Root cause: {description} in {file}:{line}. Proceed with fix?"
FIX → Read component-fix-and-verify/SKILL.md. Input: DiagnosisReport + ComponentMap paths. Output: FixResult artifact. Pause: "{PASS/FAIL/PARTIAL}. Generate regression test?"
TEST → Read regression-test-generator/SKILL.md. Input: FixResult + DiagnosisReport + ComponentMap paths. Output: RegressionTest artifact. "Test written. Investigation complete."
If user declines at any pause, stop and summarize findings so far.
testing
Use to convert a Word .docx file to PDF and/or verify its page count. Triggers on: converting docx to pdf, rendering a document, checking how many pages a docx produces, or asserting a page-count constraint (e.g. a resume must stay 2 pages). Wraps LibreOffice headless conversion.
development
Security audit checklist for web applications. Use when reviewing, auditing, or hardening a web app's security posture. Covers rate limiting, auth headers, IP blocking, CORS, security middleware, input validation, file upload limits, ORM usage, and password hashing. Triggers on requests like "review security", "harden this app", "security audit", "check for vulnerabilities", or when building/reviewing API endpoints.
development
Interactive wizard to craft effective prompts using Claude Code best practices
tools
Use when batch labeling, prioritizing, and assigning GitHub issues during triage sessions.