Skip to main content
ClaudeWave

Claude Code Subagents · page 6

Individual Claude Code subagents found across the directory: ready-made agent definitions you can drop into ~/.claude/agents with one command.

1,279 subagents1-command install
  1. Expert in testing JavaScript applications using Jest, ensuring comprehensive test coverage and efficient test practices.

  2. jQuery specialist focusing on efficient DOM manipulation, event handling, and AJAX interactions. Expert in optimizing jQuery code and ensuring cross-browser compatibility.

  3. Specializes in JSON Web Tokens (JWT) implementation, security, and optimization. Handles token creation, validation, and best practices for JWT usage.

  4. Write highly efficient, scalable, and fault-tolerant Kafka architectures. Handles Kafka stream processing, cluster setup, and performance optimization. Use PROACTIVELY for Kafka architecture design, troubleshooting, or improving Kafka performance.

  5. Keycloak specialist for identity and access management, realm configuration, and user federation.

  6. Expertise in Knex.js for SQL database manipulation, migration handling, and query building in Node.js environments.

  7. Expert in Kotlin programming language, focusing on idiomatic Kotlin code, coroutines, extension functions, and memory management.

  8. Master Kubernetes for container orchestration, pod management, and cluster optimization. Use PROACTIVELY for Kubernetes deployments, scaling, or troubleshooting.

  9. Expert in LangChain with focus on document processing, pipeline construction, and optimization.

  10. Expert in Laravel framework, mastering modern Laravel features, Eloquent ORM, and comprehensive testing strategies. Use PROACTIVELY for Laravel optimization, debugging, or refactoring.

  11. Expert in Liquibase for database schema management, migrations, and version control. Use proactively for managing and automating database changes.

  12. Master in building, managing, and optimizing Loki for efficient log aggregation and querying.

  13. Write efficient and idiomatic Lua code, mastering the language features, patterns, and performance optimization. Use PROACTIVELY for Lua scripting, optimization, or solving complex Lua challenges.

  14. Expert in MariaDB database management, optimization, and best practices.

  15. Expertise in Mocha, the JavaScript test framework running on Node.js, focusing on writing, organizing, and executing tests efficiently.

  16. Master MongoDB operations, schema design, performance optimization, and data modeling. Handles indexing, aggregations, and replication. Use PROACTIVELY for MongoDB query optimization, data consistency, or database scaling.

  17. Mongoose ODM specialist for MongoDB, proficient in schema design, query optimization, and data validation.

  18. Master of MQTT protocol, focusing on message brokering, QoS levels, and efficient IoT communication. Handles connection management, topic hierarchy, and security best practices using MQTT.

  19. Expert in Microsoft SQL Server handling query optimization, database design, and advanced T-SQL features.

  20. Expert in MySQL database management, query optimization, and schema design. Provides efficient solutions for MySQL-related tasks.

  21. Specialized in NATS, handling messaging patterns, scalability, and security features accurately within NATS deployments.

  22. Expert in Neo4j graph database specializing in Cypher queries, graph modeling, and optimization.

  23. Expert in building scalable and efficient applications using the NestJS framework. Focused on design patterns, best practices, and performance optimization specific to NestJS.

  24. Expert in Next.js development, specializing in serverless architecture, static site generation, and optimized React apps.

  25. Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.

  26. Deprecated placeholder. Do not use; follow root AGENTS.md and package instructions instead.

  27. Deprecated placeholder. Do not use; follow root AGENTS.md and package instructions instead.

  28. Deprecated placeholder. Do not use; follow root AGENTS.md and package instructions instead.

  29. Deprecated placeholder. Do not use; follow root AGENTS.md and package instructions instead.

  30. Deprecated placeholder. Do not use; follow root AGENTS.md and package instructions instead.

  31. Deprecated placeholder. Do not use; follow root AGENTS.md and package instructions instead.

  32. Deprecated placeholder. Do not use; follow root AGENTS.md and package instructions instead.

  33. Principal Software Architect specializing in system design, database modeling, API engineering, and system resilience.

  34. Principal Diagnostics Engineer specializing in root cause analysis, error troubleshooting, and hotfixes.

  35. Principal Clean Code Specialist specializing in code simplification, performance tuning, and refactoring loops.

  36. Senior Technical Lead and Security Auditor specializing in code quality, correctness, and security audits.

  37. Senior QA Automation Engineer specializing in unit, integration, and E2E test suite creation.

  38. Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.

  39. Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.

  40. Use this agent when you need to investigate issues, analyze system behavior, diagnose performance problems, examine database structures, collect and analyze logs from servers or CI/CD pipelines, run tests for debugging purposes, or optimize system performance. This includes troubleshooting errors, identifying bottlenecks, analyzing failed deployments, investigating test failures, and creating diagnostic reports. Examples:\n\n<example>\nContext: The user needs to investigate why an API endpoint is returning 500 errors.\nuser: "The /api/users endpoint is throwing 500 errors"\nassistant: "I''ll use the debugger agent to investigate this issue"\n<commentary>\nSince this involves investigating an issue, use the Task tool to launch the debugger agent.\n</commentary>\n</example>\n\n<example>\nContext: The user wants to analyze why the CI/CD pipeline is failing.\nuser: "The GitHub Actions workflow keeps failing on the test step"\nassistant: "Let me use the debugger agent to analyze the CI/CD pipeline logs and identify the issue"\n<commentary>\nThis requires analyzing CI/CD logs and test failures, so use the debugger agent.\n</commentary>\n</example>\n\n<example>\nContext: The user notices performance degradation in the application.\nuser: "The application response times have increased by 300% since yesterday"\nassistant: "I''ll launch the debugger agent to analyze system behavior and identify performance bottlenecks"\n<commentary>\nPerformance analysis and bottleneck identification requires the debugger agent.\n</commentary>\n</example>

  41. EXECUTE MODE - Implementing EXACTLY what was planned. Full tool access. Can only be invoked after explicit user confirmation. Use after plan is approved.

  42. FAST MODE - Execute compressed RIPER-5 workflow (RESEARCH + INNOVATE + PLAN) in one session, then pause for EXECUTE confirmation. Use when you want quick end-to-end solution.

  43. Stage, commit, and push code changes with conventional commits. Use when user says "commit", "push", or finishes a feature/fix.

  44. INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.

  45. PLAN MODE - Creating exhaustive technical specifications and implementation plans. Can write to process/general-plans/active/ and process/features/*/active/ only. Use after approach is decided.

  46. RESEARCH MODE - Information gathering only. Use for understanding existing code, architecture, and context. Never suggests implementations or modifications.

  47. Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant code changes to ensure everything works as expected. Examples:\n\n<example>\nContext: The user has just finished implementing a new API endpoint and wants to ensure it works correctly.\nuser: "I''ve implemented the new user authentication endpoint"\nassistant: "Great! Now let me use the tester agent to run the test suite and validate the implementation"\n<commentary>\nSince new code has been written, use the Task tool to launch the tester agent to run tests and ensure everything works properly.\n</commentary>\n</example>\n\n<example>\nContext: The user wants to check test coverage after adding new features.\nuser: "Can you check if our test coverage is still above 80%?"\nassistant: "I''ll use the tester agent to analyze the current test coverage and provide a detailed report"\n<commentary>\nThe user is asking about test coverage metrics, so use the tester agent to run coverage analysis.\n</commentary>\n</example>\n\n<example>\nContext: After fixing a bug, ensuring the fix doesn''t break existing functionality.\nuser: "I''ve fixed the database connection issue in the auth module"\nassistant: "Let me use the tester agent to run the test suite and ensure the fix doesn''t introduce any regressions"\n<commentary>\nAfter bug fixes, use the tester agent to validate that existing tests still pass.\n</commentary>\n</example>

  48. Use this agent when the user needs UI/UX execution support including interface implementation, design-system polish, responsive layouts, animations, accessibility review, or design documentation. Examples:\n\n<example>\nContext: User wants to implement a new landing page from an approved direction\nuser: "I need a modern landing page for our SaaS product with a hero section, features, and pricing"\nassistant: "I''ll use the ui-ux-designer agent to translate that approved direction into a polished implementation plan and UI output."\n<commentary>The user is requesting UI/UX execution work, so delegate to the ui-ux-designer agent to handle the design-aware implementation and polish.</commentary>\n</example>\n\n<example>\nContext: User has implemented a new feature and wants design review\nuser: "I''ve added a new dashboard widget, can you review the design?"\nassistant: "Let me first capture the current UI and then use the ui-ux-designer agent to analyze and provide design recommendations."\n<commentary>Use screenshot tools to capture current state, then delegate to ui-ux-designer for expert design analysis and suggestions.</commentary>\n</example>\n\n<example>\nContext: User mentions design inconsistencies\nuser: "The buttons across different pages look inconsistent"\nassistant: "I''ll use the ui-ux-designer agent to audit the design system and propose a more consistent implementation."\n<commentary>Design-system work requires the ui-ux-designer agent to analyze, document, and improve consistent design patterns.</commentary>\n</example>\n\n<example>\nContext: Proactive design optimization opportunity\nuser: "Here''s the new signup form I just built"\nassistant: "Let me use the ui-ux-designer agent to review the form design for accessibility, user experience, and mobile responsiveness."\n<commentary>Even without an explicit design brief, ui-ux-designer can help ensure design quality and best practices during execute-phase polish.</commentary>\n</example>

  49. UPDATE PROCESS MODE - Analyze execution, generate rule improvements, update plan files and context. Use after completing EXECUTE mode to reconcile deviations and capture learnings.

  50. Review code changes for quality, security, and best practices. Proactively use this after code modifications.

  51. Run tests and report results concisely. Use this after code changes to verify everything works.

  52. Analyze log files and extract actionable insights. Use when troubleshooting issues or investigating incidents.

  53. Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.

  54. Explore and analyze authentication-related code. Use when investigating auth flows, session management, or security.

  55. Explore and analyze database-related code. Use when investigating data models, queries, or persistence.

  56. Analyze root cause of bugs after location is identified. Second step in bug investigation.

  57. Implement bug fixes after analysis is complete. Third step in bug fix pipeline.

  58. Locate the source of bugs in the codebase. First step in bug investigation.

  59. Verify bug fixes by running tests. Final step in bug fix pipeline.

  60. Generate comprehensive API documentation by scanning Express route files.

  61. Pipeline Stage 2 - Generate API documentation from a route manifest.

  62. Pipeline Stage 3 - Validate generated API documentation against quality standards.

  63. Pipeline Stage 1 - Scan Express routes and produce a route manifest.

  64. Interactive guide for building custom Claude Code Agents and subagents. Asks straightforward questions, generates enhanced YAML frontmatter with tools/model/color/field/expertise, creates agent .md files, validates format, and helps install to .claude/agents/ or ~/.claude/agents/. Use when user wants to build workflow specialist agents.

  65. Main navigation guide for Claude Code Skills Factory. Use when user wants to build custom Skills, Prompts, or Agents. Orchestrates and delegates to specialized guide agents.

  66. Interactive guide for building custom Claude Code hooks. Asks straightforward questions, uses hook-factory skill, generates complete hooks with validation, and provides installation instructions.

  67. Interactive guide for using prompt-factory skill to generate mega-prompts. Helps choose from 69 presets or create custom prompts, select formats (XML/Claude/ChatGPT/Gemini), and explains usage. Use when user wants to generate production-ready prompts for any LLM.

  68. Interactive guide for building custom Claude Skills. Asks straightforward questions, uses SKILLS_FACTORY_PROMPT template, generates complete skill files, validates format, creates ZIP, and helps install. Use when user wants to build multi-file skill capabilities.

  69. Software architecture specialist for system design, scalability, and technical decision-making. Use PROACTIVELY when planning new features, refactoring large systems, or making architectural decisions.

  70. Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.

  71. Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.

  72. PostgreSQL database specialist for query optimization, schema design, security, and performance. Use PROACTIVELY when writing SQL, creating migrations, designing schemas, or troubleshooting database performance. Incorporates Supabase best practices.

  73. Documentation and codemap specialist. Use PROACTIVELY for updating codemaps and documentation. Runs /update-codemaps and /update-docs, generates docs/CODEMAPS/*, updates READMEs and guides.

  74. End-to-end testing specialist using Vercel Agent Browser (preferred) with Playwright fallback. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.

  75. Expert planning specialist for complex features and refactoring. Use PROACTIVELY when users request feature implementation, architectural changes, or complex refactoring. Automatically activated for planning tasks.

  76. Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.

  77. Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.

  78. Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.

  79. Fresh-context verification sub-agent. Runs build/type/lint/test verification pipeline.

  80. Use this agent when you need to create foundational templates, boilerplate code, or starter configurations for new projects, components, or features. This agent excels at generating clean, well-structured base templates that follow best practices and can be easily customized. Examples: <example>Context: User needs to start a new React component and wants a solid foundation. user: 'I need to create a new user profile component' assistant: 'I'll use the base-template-generator agent to create a comprehensive React component template with proper structure, TypeScript definitions, and styling setup.' <commentary>Since the user needs a foundational template for a new component, use the base-template-generator agent to create a well-structured starting point.</commentary></example> <example>Context: User is setting up a new API endpoint and needs a template. user: 'Can you help me set up a new REST API endpoint for user management?' assistant: 'I'll use the base-template-generator agent to create a complete API endpoint template with proper error handling, validation, and documentation structure.' <commentary>The user needs a foundational template for an API endpoint, so use the base-template-generator agent to provide a comprehensive starting point.</commentary></example>

  81. Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.

  82. Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.

  83. Performance engineering specialist for application profiling, optimization, and scalability. Use proactively for performance issues, bottleneck analysis, and optimization tasks.

  84. Code refactoring specialist focused on clean architecture, SOLID principles, and technical debt reduction. Use proactively for code quality improvements and architectural refactoring.

  85. Expert debugging specialist focused on comprehensive root cause analysis (RCA), systematic problem-solving, and minimal-impact fixes. Use for complex bugs, performance issues, and production incidents requiring deep investigation.

  86. Expert system architect specializing in evidence-based design decisions, scalable system patterns, and long-term technical strategy. Use proactively for architectural reviews and system design.

  87. Specialized testing expert for comprehensive test creation, validation, and quality assurance across all testing levels. Use proactively for test generation and coverage analysis.

  88. Use this agent when you need to identify and fix TypeScript 'any' type usage in your codebase. Examples: <example>Context: User has written some TypeScript code with any types that need to be properly typed. user: "I just wrote this function but it uses 'any' types everywhere" assistant: "Let me use the typescript-any-fixer agent to analyze and fix the any type issues" <commentary>Since the user has TypeScript code with any type issues, use the typescript-any-fixer agent to identify and provide proper type definitions.</commentary></example> <example>Context: User is reviewing code and wants to eliminate any types for better type safety. user: "Can you help me remove all the 'any' types from this code?" assistant: "I'll use the typescript-any-fixer agent to help eliminate the any types and provide proper TypeScript typing" <commentary>The user specifically wants to fix any types, so use the typescript-any-fixer agent to provide type-safe alternatives.</commentary></example>

  89. >-

  90. >-

  91. >-

  92. >-

  93. Read-only code review agent. Catches type issues, pattern violations, missing tests. Cannot modify files.

  94. Run tests, analyze failures, suggest fixes. Use after code changes.

  95. Decomposes goals into parallel tasks, assigns them to CLI coding agents, verifies output, and merges results. Use when a task is too large for a single agent.

  96. |

  97. |

  98. |

  99. |

  100. |