Skip to main content
ClaudeWave

Claude Code Subagents · page 7

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

1,353 subagents1-command install
  1. Review MCP server changes for tool safety, schema quality, and host integration correctness.

  2. 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.

  3. 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.

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

  5. 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.

  6. 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.

  7. |

  8. >-

  9. >-

  10. >-

  11. >-

  12. |

  13. |

  14. |

  15. Use when writing SQL queries, creating migrations, or troubleshooting database performance in Supabase/PostgreSQL projects. Reviews indexes, RLS policies, schema types, N+1 patterns. Read-only reviewer with EXPLAIN ANALYZE capability.

  16. |

  17. |

  18. |

  19. |

  20. |

  21. |

  22. |

  23. 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>

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

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

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

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

  28. 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.

  29. 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.

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

  31. 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.

  32. Update people profiles in 05-knowledge/people/ with new information from brief data, meetings, or Slack

  33. Collect data from GitHub, Slack, Jira, Linear, or file system. Structured extraction only — no synthesis.

  34. Execute pre-approved mutations — Jira transitions, Linear updates, API calls, build commands.

  35. Read, write, and organize vault files. Metadata updates, file moves, profile updates.

  36. Execute publishing operations — Slack, Confluence, Notion, webhooks. Receives final content and posts it.

  37. Web research agent. Searches, fetches URLs, extracts facts and evidence. No synthesis — just structured findings.

  38. 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>

  39. Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.

  40. Validates Design Doc compliance and implementation completeness from third-party perspective. Use PROACTIVELY after implementation completes or when "review/implementation check/compliance" is mentioned. Provides acceptance criteria validation and quality reports.

  41. Validates consistency between PRD/Design Doc and code implementation. Use PROACTIVELY after implementation completes, or when "document consistency/implementation gap/as specified" is mentioned. Uses multi-source evidence matching to identify discrepancies.

  42. Analyzes existing codebase objectively for facts about implementation, user behavior patterns, and technical architecture. Use when existing code needs to be understood without hypothesis bias. Invoked before Design Doc creation to produce focused guidance for technical designers.

  43. Detects conflicts across multiple Design Docs and provides structured reports. Use when multiple Design Docs exist, or when "consistency/conflict/sync/between documents" is mentioned. Focuses on detection and reporting only, no modifications.

  44. Reviews document consistency and completeness, providing approval decisions. Use PROACTIVELY after PRD/UI Spec/Design Doc/work plan creation, or when "document review/approval/check" is mentioned. Detects contradictions and rule violations with improvement suggestions.

  45. Verifies consistency between test skeleton comments and implementation code. Use PROACTIVELY after test implementation completes, or when "test review/skeleton verification" is mentioned. Returns quality reports with failing items and fix instructions.

  46. Comprehensively collects problem-related information and creates evidence matrix. Use PROACTIVELY when bug/error/issue/defect/not working/strange behavior is reported. Reports only observations without proposing solutions.

  47. Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metrics.

  48. Specialized agent for fixing quality issues in frontend React projects. Executes all verification and fixing tasks including React Testing Library tests in a completely self-contained manner. Takes responsibility for fixing all quality errors until all checks pass. MUST BE USED PROACTIVELY when any quality-related keywords appear (quality/check/verify/test/build/lint/format/type/fix) or after code changes. Handles all verification and fixing tasks autonomously.

  49. Specialized agent for fixing quality issues in software projects. Executes all verification and fixing tasks related to code quality, correctness guarantees, testing, and building in a completely self-contained manner. Takes responsibility for fixing all quality errors until all tests pass. MUST BE USED PROACTIVELY when any quality-related keywords appear (quality/check/verify/test/build/lint/format/correctness/fix) or after code changes. Handles all verification and fixing tasks autonomously.

  50. Performs requirements analysis and work scale determination. Use PROACTIVELY when new feature requests or change requests are received, or when "requirements/scope/where to start" is mentioned. Extracts user requirement essence and proposes development approaches.

  51. Selects optimal rulesets for tasks and performs metacognitive analysis. Use PROACTIVELY before implementation tasks start, or when "rules/ruleset/coding standards" is mentioned. Returns structured JSON with recommended skills and rationale.

  52. Discovers functional scope from existing codebase for reverse documentation. Identifies targets through multi-source discovery combining user-value and technical perspectives. Use when "reverse engineering/existing code analysis/scope discovery" is mentioned.

  53. Reviews implementation for security compliance against Design Doc security considerations. Use PROACTIVELY after all implementation tasks complete, or when "security review/security check/vulnerability check" is mentioned. Returns structured findings with risk classification and fix suggestions.

  54. Derives multiple solutions for verified causes and analyzes tradeoffs. Use when root cause verification has concluded, or when "solution/how to fix/fix method/remedy" is mentioned. Focuses on solutions from given conclusions without investigation.

  55. Reads work plan documents from docs/plans and decomposes them into independent, single-commit granularity tasks placed in docs/plans/tasks. PROACTIVELY proposes task decomposition when work plans are created.

  56. Executes React implementation completely self-contained following frontend task files. Use when frontend task files exist, or when "frontend implementation/React implementation/component creation" is mentioned. Asks no questions, executes consistently from investigation to implementation.

  57. Executes implementation completely self-contained following task files. Use when task files exist in docs/plans/tasks/, or when "execute task/implement task/start implementation" is mentioned. Asks no questions, executes consistently from investigation to implementation.

  58. Creates frontend ADR and Design Docs to evaluate React technical choices. Use when frontend PRD is complete and technical design is needed, or when "frontend design/React design/UI design/component design" is mentioned.

  59. Creates ADR and Design Docs to evaluate technical choices and implementation approaches. Use when PRD is complete and technical design is needed, or when "ADR/design doc/technical design/architecture" is mentioned.

  60. Gathers UI-related facts by reading the project's external-resources file, fetching external sources (design origin, design system, guidelines) via MCP or URL, and analyzing the existing UI codebase. Use when frontend design or adjustment work needs a single consolidated UI context (external sources + code) before document creation or implementation.

  61. Creates UI Specifications from PRD and optional prototype code. Use when PRD is complete and frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.

  62. Critically evaluates investigation results, checks path coverage, and validates failure points using Devil's Advocate method. Use when investigation has completed, or when "verify/validate/double-check/confirm findings" is mentioned. Focuses on verification and conclusion derivation.

  63. Creates work plan documents with trackable execution plans. Use when Design Doc is complete and implementation planning is needed, or when "work plan/implementation plan/task planning" is mentioned.

  64. Invoke when the user needs to manage multiple client brands, view portfolio-level dashboards, generate client reports, manage SOPs, switch credential profiles, assign team tasks, configure regions, or generate executive summaries. Triggers on requests involving multi-client management, agency workflows, client onboarding, or portfolio oversight.

  65. Invoke when the user needs help with marketing measurement, KPI definition, dashboard design, attribution modeling, performance analysis, anomaly detection, competitive benchmarking, or translating data into marketing decisions. Triggers on requests involving metrics, reporting, analytics setup, or data interpretation.

  66. Invoke when marketing content needs quality control review — brand voice consistency checks, regulatory compliance verification (GDPR, CAN-SPAM, CCPA, HIPAA, FTC, industry-specific), accessibility auditing (WCAG 2.1), inclusive language review, or brand safety assessment. Automatically invoked as a final review step before any content is published or delivered.

  67. Invoke when the user needs competitor analysis — content strategy teardowns, SEO gap analysis, paid ad analysis from ad libraries, social media benchmarking, AI visibility comparisons, pricing and positioning research, or market landscape mapping. Triggers on requests mentioning competitors, competitive gaps, market analysis, or benchmarking.

  68. Use when the task requires ongoing competitive monitoring, competitor change detection, share of voice tracking, competitive alerts, ad monitoring, price monitoring, win/loss analysis, or competitive narrative mapping.

  69. Invoke when the user needs any form of marketing content created or refined — blog posts, ad copy, email campaigns, social media posts, landing page copy, press releases, video scripts, product descriptions, or newsletter content. Triggers on requests to write, draft, rewrite, or improve marketing copy.

  70. Invoke when the user needs to manage CRM operations — creating contacts, importing leads, updating deals, syncing campaign data, segmenting audiences, managing pipelines, or connecting marketing data to Salesforce, HubSpot, Zoho, or Pipedrive. Triggers on requests involving CRM data, lead management, pipeline updates, or sales-marketing alignment.

  71. Invoke when the user needs help with conversion rate optimization — landing page audits, A/B test design, form optimization, pricing page strategy, checkout flow improvement, personalization, statistical significance calculations, page speed impact analysis, or mobile conversion optimization. Triggers on requests involving conversions, landing pages, A/B testing, or optimization experiments.

  72. Invoke when the user needs help with email marketing — campaign strategy, automation flows, deliverability optimization, A/B testing methodology, list segmentation, lifecycle sequences, re-engagement campaigns, win-back flows, transactional email optimization, or newsletter strategy. Triggers on requests involving email campaigns, drip sequences, email deliverability, list management, or email automation.

  73. Invoke when the user wants to publish, send, launch, schedule, or execute any marketing action on an external platform. Triggers on requests to publish blog posts, send emails, launch ads, schedule social posts, deliver reports, sync CRM data, or send SMS/notifications. Manages the approval workflow and ensures every execution is logged.

  74. Invoke when the user needs help with product-led growth strategy, referral programs, viral loop design, launch strategy, retention optimization, growth experiments, activation funnels, or conversion rate optimization. Triggers on requests involving growth models, PLG, user acquisition loops, experiment design, or retention mechanics for SaaS, marketplace, and consumer products.

  75. Invoke when the user needs help with influencer marketing — creator discovery, campaign briefs, FTC compliance verification, UGC strategy, influencer contract guidance, performance measurement, audience authenticity assessment, cost benchmarking, or B2B thought leader identification. Triggers on requests involving influencers, creators, brand ambassadors, or user-generated content campaigns.

  76. Use when the task requires storing, retrieving, synthesizing, or distributing marketing learnings across agents — compound intelligence, pattern recognition, playbook generation, or institutional knowledge management.

  77. Use when the task requires designing cross-channel customer journeys, mapping touchpoint sequences, planning journey state machines with branching logic, simulating journey outcomes, or coordinating multi-channel nurture flows.

  78. Multilingual marketing specialist who manages translation routing, transcreation, cultural adaptation, multilingual SEO, and translation quality assurance across languages and cultures.

  79. Use when the task requires monitoring macro signals — economic indicators, cultural trends, industry events, platform algorithm changes, or regulatory updates — that impact marketing strategy and timing.

  80. Use when the task requires marketing science — causal inference, Marketing Mix Modeling, incrementality testing, revenue simulation, statistical rigor, saturation curve analysis, or churn prediction.

  81. Invoke when the user needs high-level marketing strategy, campaign planning, budget allocation, go-to-market planning, competitive positioning, or funnel design. Triggers on requests involving marketing plans, channel mix decisions, growth roadmaps, or strategic marketing questions.

  82. Invoke when the user needs help with paid advertising — campaign setup, audience targeting, bid strategies, ad creative recommendations, budget pacing, performance optimization, or media plans across Google Ads, Meta Ads, LinkedIn Ads, TikTok Ads, Pinterest Ads, Amazon Ads, programmatic, or retail media networks.

  83. Invoke when the user wants to save brand knowledge to persistent memory, search past campaign learnings, sync session insights to a vector database, manage the knowledge graph, or configure the memory architecture. Triggers on requests involving long-term memory, RAG retrieval, knowledge storage, cross-session learnings, or "what worked before" queries.

  84. Invoke when the user wants to check campaign performance, detect anomalies, track budget pacing, monitor deliverability, or get real-time marketing metrics from connected platforms. Triggers on requests involving live data, performance alerts, anomaly detection, or campaign health checks.

  85. Invoke when the user needs help with digital PR, media outreach, press release writing, journalist pitching, HARO or Connectively responses, thought leadership strategy, newsjacking opportunities, E-E-A-T authority building, or executive branding. Triggers on requests involving press coverage, media relations, PR campaigns, or building domain authority through earned media.

  86. Senior QA lead who orchestrates multi-dimensional content evaluation, synthesizes results across scoring dimensions, identifies quality risks, and recommends fixes before publication.

  87. Invoke when the user needs help with search engine optimization, AI engine optimization (AEO), generative engine optimization (GEO), keyword research, technical SEO audits, content optimization for search, local SEO, link building strategy, or improving visibility in AI-generated answers and search features.

  88. Invoke when the user needs help with social media management — community management, content calendar planning, algorithm optimization, trend response, engagement strategy, UGC curation, social commerce, crisis monitoring, platform-specific strategy, or social listening insights. Triggers on requests involving social media strategy, posting plans, engagement, community management, or social platform optimization.

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

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

  91. Use this agent when you need comprehensive full-stack engineering expertise, particularly for server-side development, system architecture, DevOps, and infrastructure tasks. Examples include: (1) Designing and implementing scalable server architectures using languages like Node.js, Python, Go, Java, or Ruby; (2) Setting up CI/CD pipelines, Docker containers, Kubernetes orchestrations, or cloud infrastructure on AWS/Azure/GCP; (3) Optimizing database performance, implementing caching strategies, or designing API systems; (4) Troubleshooting production issues, analyzing logs, or performing system monitoring and alerting setup; (5) Implementing security best practices, authentication systems, or compliance requirements; (6) Conducting code reviews for backend services, infrastructure as code, or deployment configurations. This agent should be consulted proactively when architectural decisions, scalability concerns, or operational excellence considerations are needed for any server-side or infrastructure component.

  92. Use this agent when you need Pencil-based design workflows: atomic designer actions, MCP tools, and spec-driven UI plans. Examples include: (1) Turning PRD or user requirements into action-level PENCIL_PLAN via pencil-ui-design-spec-generator; (2) Executing Pencil MCP tools in sequence (open_document, batch_design, set_variables, get_screenshot, get_style_guide, etc.) to simulate designer operations; (3) Initializing design systems (Layui, Ant Design, Bootstrap, Element Plus, uView, uView Pro, Vant, uCharts, ECharts) with pencil-ui-design-system-* skills; (4) Creating new pencil-ui-design-system-* skills with pencil-skill-creator. This agent should be used when the task involves Pencil, Figma-like design automation, or action-level design plans rather than high-level text-to-UI.

  93. |

  94. |

  95. |

  96. |

  97. |

  98. |

  99. |

  100. |