Audit frontend code for WCAG 2.1 AA compliance. Use when building UI components, before launch, or when accessibility issues are reported. Checks semantic HTML, keyboard navigation, ARIA, color contrast, and screen reader compatibility.
Reviews system design, module boundaries, and architectural patterns. Use PROACTIVELY when adding new modules, creating new directories, or restructuring code. Catches structural problems before they become expensive to fix.
MUST BE USED PROACTIVELY after writing or modifying any code. Reviews against project standards, TypeScript strict mode, React patterns, accessibility, and performance. Catches anti-patterns before they ship.
Writes and updates project documentation automatically. Use PROACTIVELY after code changes to keep docs in sync. Generates JSDoc comments, component docs, README updates, and API references without being asked.
Monitors all other agents and produces a single unified project health report. Use when starting a coding session, before deploying, or when context-switching back to a project. Summarizes findings from code-reviewer, performance-auditor, accessibility-auditor, architecture-reviewer, doc-generator, and test-writer.
Analyze frontend performance — bundle size, Core Web Vitals, rendering, network waterfall. Use when investigating slow pages, optimizing load times, or auditing performance before launch.
Plan safe, incremental refactoring strategies. Use when code needs restructuring, patterns need updating, or technical debt needs addressing. Creates a step-by-step migration plan with rollback points.
Writes and runs tests automatically. Use PROACTIVELY after new features, bug fixes, or refactors to maintain coverage. Creates unit tests with React Testing Library, factory functions, and proper mocking.
Runs before the agent uses a tool for Edit, Write, MultiEdit, Edit, Write and MultiEdit tool calls, running an inline shell check (2 commands). From Piyush8296/claude-workspace.