Skip to main content
ClaudeWave
ES, Spanish

Subagents de Claude Code · página 3

Subagentes individuales de Claude Code encontrados en el directorio: definiciones listas para copiar a ~/.claude/agents con un comando.

1184 subagentsinstalación en 1 comando
  1. Comprehensive testing architecture specialist for ZCF project using Vitest

    UfoMiao/zcfInstalar
  2. CCR, Cometix, and CCusage integration specialist for ZCF project

    UfoMiao/zcfInstalar
  3. MUST BE USED PROACTIVELY after writing or modifying any code. Reviews against project standards, TypeScript strict mode, and coding conventions. Checks for anti-patterns, security issues, and performance problems.

  4. Git workflow agent for commits, branches, and PRs. Use for creating commits, managing branches, and creating pull requests following project conventions.

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

  6. Use this agent when the user provides a Kaggle competition URL or asks to learn from Kaggle winning solutions. Examples:

  7. Use this agent when the user asks to "conduct literature review", "search for papers", "analyze research papers", "identify research gaps", "review related work", or mentions starting a research project. This agent integrates with Zotero for automated paper collection, organization, and full-text analysis. Examples:

  8. Use this agent when the user provides a research paper (PDF/DOCX/arXiv link) or asks to learn writing patterns from papers, extract venue-specific writing signals, study paper structure, or mine rebuttal strategies. The agent writes extracted knowledge into the active installed paper-miner writing memory for ml-paper-writing. It does not maintain project-specific writing memory.

  9. Use this agent when the user asks to "write rebuttal", "respond to reviewers", "analyze review comments", or needs help with academic paper review response. This agent specializes in systematic rebuttal writing with professional tone and structured responses.

  10. Test-driven development guide for writing tests first, implementing the smallest passing change, and keeping verification tight. Use when the user explicitly wants TDD or when a task should be driven by failing tests before code.

  11. >

  12. >

  13. >

  14. Proactively scans for achievements and wins that aren't in the brag doc yet. Checks recent work notes, incident resolutions, git history, and 1:1 feedback for brag-worthy items.

  15. Load all vault context about a specific topic — person, project, incident, team, or concept. Gathers notes, backlinks, mentions, timeline, and produces a synthesized briefing.

  16. Find every note restating a corrected fact and classify each as authoritative, restatement, or historical. Discovery and judgement only — never edits. Invoked by /om-correct, or when a fact has been corrected and the restatements need locating.

  17. Scan recent or specified notes for missing wikilinks. Finds mentions of people, projects, teams, competencies, and incidents that should be linked but aren't. Suggests missing bidirectional links for user approval.

  18. Bulk create or update person notes from Slack profiles. Given user IDs or names, checks Slack for role/title/team, checks vault for existing notes, creates missing ones, updates stale ones, and updates People & Context index.

  19. Verify every factual claim in a review draft against vault sources. Returns verified/unverified/flagged claims.

  20. Aggregate performance review material from the vault for a given period. Scans brag doc, decisions led, incidents handled, competency evidence, 1-on-1 feedback, and PR deep scans. Invoke via /om-review-brief or when the user asks for review prep.

  21. Deep reconstruction of Slack conversations. Given channel/DM/thread URLs, reads every message, every sub-thread, every profile, and produces a structured timeline with attribution. Use for incident reconstruction, evidence gathering, or any situation requiring full Slack context.

  22. Run vault maintenance: detect orphan notes, find broken wikilinks, validate frontmatter completeness, flag stale active notes, check cross-linking integrity. Invoke via /om-vault-audit or when the user asks for vault cleanup.

  23. Classify, transform, and migrate vault content from a source vault into this obsidian-mind instance. Two modes: classification (analyze source, return map) and execution (given approved plan, perform migration). Invoked by /om-vault-upgrade.

  24. Use this agent when the user needs to create or edit changelog entries in the Docusaurus documentation. Specifically, use this agent when: 1) The user mentions adding a new changelog entry or release notes, 2) The user asks to update or modify existing changelog entries, 3) The user wants to document a new feature, bug fix, or change in the project, 4) The user provides content that should be formatted as a changelog entry. Examples: \n\nExample 1:\nuser: "We just fixed the bug where users couldn't save their preferences. Can you add this to the changelog?"\nassistant: "I'll use the changelog-editor agent to create a proper changelog entry for this bug fix in both the main page and a detailed entry."\n\nExample 2:\nuser: "I need to document the new API authentication feature we released in v2.3.0"\nassistant: "Let me use the changelog-editor agent to create a comprehensive changelog entry for the new authentication feature, including checking if we have existing documentation to link to."\n\nExample 3:\nuser: "Can you update the changelog entry for the dashboard redesign? We now have screenshots and a demo video."\nassistant: "I'll use the changelog-editor agent to update that entry with proper placeholders for the screenshots and YouTube video embedding."\n\nProactively use this agent when you notice the user describing changes, features, or fixes that should be documented in the changelog, even if they don't explicitly ask for changelog updates.

  25. Implementa EXATAMENTE UMA feature de plan/features.json do gov-loop (DeskcommCRM · Governança de Atendimento), com precisão e impacto mínimo. Usado pela sessão do loop (loop/LOOP.md) para todo trabalho. Recebe o briefing com id, acceptance verbatim e restrições; devolve resumo com evidência observada. Não marca estado, não commita, não verifica o próprio trabalho.

  26. Verificador CÉTICO do gov-loop (DeskcommCRM · Governança de Atendimento), com poder de veto. Roda os acceptance de uma feature MECANICAMENTE e caça o que quebra. Chamado pela sessão do loop após o gov-implementer. Não corrige nada — sem Write/Edit no frontmatter, e sob hash-check do orquestrador (qualquer mudança no working tree durante a verificação invalida o veredito). Só emite PASS ou FAIL com findings. passes:true no features.json só existe com PASS dele.

  27. Tenta REFUTAR o veredito da triagem antes que ele seja publicado no PR do contribuidor. Chamado no passe 9. Recusa veredito sem o campo NÃO MEDIDO, pedido sem medição anexada, e afirmação cuja evidência é presença de símbolo em vez de comportamento. Não corrige e não publica — sem Write/Edit no frontmatter, e sob hash-check do orquestrador.

  28. Mede um PR de contribuidor — roda os gates da main na PRÉVIA DO MERGE e percorre o complemento do CI (o que nenhum job reprova). Chamado pela triagem no passe 3/4. Devolve MEDIÇÃO com comando e saída, nunca veredito: quem decide é a triagem, quem refuta é o triagem-cetico. Não corrige nada — sem Write/Edit no frontmatter.

  29. Reproduz o defeito que um PR alega consertar, no SHA atual da main, e escreve o teste que falta quando o PR muda comportamento sem trazer teste. Chamado pela triagem nos passes 5/6. Sabota a própria correção para provar que o teste vigia. Trabalha SEMPRE num worktree exclusivo — nunca compartilha árvore com outro agente.

  30. Council member. Use standalone for formal systems & computational analysis, or via /council for multi-perspective deliberation.

  31. Council member. Use standalone for categorization & structural analysis, or via /council for multi-perspective deliberation.

  32. Council member. Use standalone for resilience & moral clarity analysis, or via /council for multi-perspective deliberation.

  33. Council member. Use standalone for first-principles debugging & explanation testing, or via /council for multi-perspective deliberation.

  34. Council member. Use standalone for cognitive bias detection & decision science analysis, or via /council for multi-perspective deliberation.

  35. Council member. Use standalone for neural network intuition & empirical ML analysis, or via /council for multi-perspective deliberation.

  36. Council member. Use standalone for emergence & non-intervention analysis, or via /council for multi-perspective deliberation.

  37. Council member. Use standalone for power dynamics & incentive analysis, or via /council for multi-perspective deliberation.

  38. Council member. Use standalone for systems thinking & feedback loop analysis, or via /council for multi-perspective deliberation.

  39. Council member. Use standalone for multi-model reasoning & economic analysis, or via /council for multi-perspective deliberation.

  40. Council member. Use standalone for strategic timing & situational awareness analysis, or via /council for multi-perspective deliberation.

  41. Council member. Use standalone for user-centered design & simplicity analysis, or via /council for multi-perspective deliberation.

  42. Council member. Use standalone for assumption destruction & dialectical analysis, or via /council for multi-perspective deliberation.

  43. Council member. Use standalone for adversarial strategy & competitive analysis, or via /council for multi-perspective deliberation.

  44. Council member. Use standalone for scaling frontier & AI safety analysis, or via /council for multi-perspective deliberation.

  45. Council member. Use standalone for antifragility & tail risk analysis, or via /council for multi-perspective deliberation.

  46. Council member. Use standalone for pragmatic engineering & shipping analysis, or via /council for multi-perspective deliberation.

  47. Council member. Use standalone for perspective dissolution & reframing analysis, or via /council for multi-perspective deliberation.

  48. Use when working on WCAG compliance, inclusive design, and universal access, including screen reader compatibility, keyboard navigation, and assistive technology integration, with emphasis on creating barrier-free digital experiences.

  49. Use when browsing, searching, installing, or removing Claude Code agents from the awesome-claude-code-subagents community collection.

  50. Use when working on AI system design, model implementation, and production deployment, including multiple AI frameworks and tools, with emphasis on building scalable, efficient, and ethical AI solutions from research to production.

  51. Use when working on Angular 15+ with enterprise patterns, including RxJS, NgRx state management, micro-frontend architecture, and performance optimization, with emphasis on building scalable enterprise applications.

  52. Use when designing scalable, developer-friendly interfaces, creating REST and GraphQL APIs with comprehensive documentation, focusing on consistency, performance, and developer experience.

  53. Use when creating comprehensive, developer-friendly API documentation, including OpenAPI/Swagger specifications, interactive documentation portals, and documentation automation, with emphasis on clarity, completeness, and exceptional developer experience.

  54. Use when working on system design validation, architectural patterns, and technical decision assessment, including scalability analysis, technology stack evaluation, and evolutionary architecture, with emphasis on maintainability and long-term viability.

  55. Use when designing, reviewing, or debugging authentication, authorization, OAuth, OIDC, SSO, sessions, JWTs, RBAC, ABAC, or identity security flows.

  56. Use when working on scalable API development and microservices architecture, building robust server-side solutions, with emphasis on performance, security, and maintainability.

  57. Use when working on smart contract development, DApp architecture, and DeFi protocols, including Solidity, Web3 integration, and blockchain security, with emphasis on building secure, gas-efficient, and innovative decentralized applications.

  58. Use when working on build system optimization, compilation strategies, and developer productivity, including modern build tools, caching mechanisms, and creating fast, reliable build pipelines that scale with team growth.

  59. Use when working on command-line interface design, developer tools, and terminal applications, including user experience, cross-platform compatibility, and building efficient CLI tools that developers love to use.

  60. Use when working on multi-cloud strategies, scalable architectures, and cost-effective solutions, including AWS, Azure, and GCP, with emphasis on security, performance, and compliance while designing resilient cloud-native systems.

  61. Use when exploring unfamiliar legacy code, reconstructing intent, mapping hidden dependencies, finding ownership boundaries, or documenting risky behavior before changes.

  62. Use when working on code quality, security vulnerabilities, and best practices across multiple languages, including static analysis, design patterns, and performance optimization, with emphasis on maintainability and technical debt reduction.

  63. Use when working on modern C++20/23, systems programming, and high-performance computing, including template metaprogramming, zero-overhead abstractions, and low-level optimization with emphasis on safety and efficiency.

  64. Use when working on modern .NET development, ASP.NET Core, and cloud-native applications, including C# 12 features, Blazor, and cross-platform development with emphasis on performance and clean architecture.

  65. Use when working on business intelligence, data visualization, and statistical analysis, including SQL, Python, and BI tools to transform raw data into actionable insights, with emphasis on stakeholder communication and business impact.

  66. Use when building scalable data pipelines, ETL/ELT processes, and data infrastructure, including big data technologies and cloud platforms, with emphasis on reliable, efficient, and cost-optimized data platforms.

  67. Use when discovering, collecting, and analyzing diverse data sources, including data mining, statistical analysis, and pattern recognition, with emphasis on extracting meaningful insights from complex datasets to support evidence-based decisions.

  68. Use when working on statistical analysis, machine learning, and business insights, including exploratory data analysis, predictive modeling, and data storytelling, with emphasis on delivering actionable insights that drive business value.

  69. Use when working on high-availability systems, performance optimization, and disaster recovery, including PostgreSQL, MySQL, MongoDB, and Redis, with emphasis on reliability, scalability, and operational excellence.

  70. Use when working on query optimization, performance tuning, and scalability across multiple database systems, including execution plan analysis, index strategies, and system-level optimizations, with emphasis on achieving peak database performance.

  71. Use when working on complex issue diagnosis, root cause analysis, and systematic problem-solving, including debugging tools, techniques, and methodologies across multiple languages and environments, with emphasis on efficient issue resolution.

  72. Use when working on package management, security auditing, and version conflict resolution across multiple ecosystems, including dependency optimization, supply chain security, and automated updates, with emphasis on maintaining stable, secure, and efficient dependency trees.

  73. Use when working on CI/CD pipelines, release automation, and deployment strategies, including blue-green, canary, and rolling deployments, with emphasis on zero-downtime releases and rapid rollback capabilities.

  74. Use when bridging development and operations with comprehensive automation, monitoring, and infrastructure management, including CI/CD, containerization, and cloud platforms, with emphasis on culture, collaboration, and continuous improvement.

  75. Use when working on rapid detection, diagnosis, and resolution of production issues, including observability tools, root cause analysis, and automated remediation, with emphasis on minimizing downtime and preventing recurrence.

  76. Use when working on Django 4+ with modern Python practices, including scalable web applications, REST API development, async views, and enterprise patterns, with emphasis on rapid development and security best practices.

  77. Use when working on technical documentation systems, API documentation, and developer-friendly content, including documentation-as-code, automated generation, and creating maintainable documentation that developers actually use.

  78. Use when working on .NET Core, .NET 10, modern C#, minimal APIs, cross-platform services, cloud-native applications, and high-performance microservices.

  79. Use when maintaining, debugging, or modernizing .NET Framework 4.8 enterprise applications, Web Forms, WCF services, Windows services, and Windows-based legacy systems.

  80. Use when working on build performance, tooling efficiency, and workflow automation, including development environment optimization, with emphasis on reducing friction, accelerating feedback loops, and maximizing developer productivity and satisfaction.

  81. Use when designing, writing, reviewing, or debugging end-to-end tests with Playwright, Cypress, browser automation, user journeys, and UI regressions.

  82. Use when working on concurrent, fault-tolerant systems using OTP patterns, including Phoenix, LiveView, and BEAM VM optimization for building highly available distributed applications.

  83. Use when working on microcontroller programming, RTOS development, and hardware optimization, including low-level programming, real-time constraints, and resource-limited environments, with emphasis on reliability, efficiency, and hardware-software integration.

  84. Use when working on complex error pattern analysis, correlation, and root cause discovery, including distributed system debugging, error tracking, and anomaly detection, with emphasis on finding hidden connections and preventing error cascades.

  85. Use when working on financial systems, regulatory compliance, and secure transaction processing, including banking integrations, payment systems, and building scalable financial technology that meets stringent regulatory requirements.

  86. Use when working on Flutter 3+ with modern architecture patterns, including cross-platform development, custom animations, native integrations, and performance optimization, with emphasis on creating beautiful, native-performance applications.

  87. Use when crafting robust, scalable frontend solutions, building high-quality React components prioritizing maintainability, user experience, and web standards compliance.

  88. Use when building full-stack features and delivering complete solutions from database to UI, with emphasis on seamless integration and optimal user experience.

  89. Use when working on game engine programming, graphics optimization, and multiplayer systems, including game design patterns, performance optimization, and cross-platform development, with emphasis on creating engaging, performant gaming experiences.

  90. Use when working on branching strategies, automation, and team collaboration, including Git workflows, merge conflict resolution, and repository management, with emphasis on enabling efficient, clear, and scalable version control practices.

  91. Use when working on high-performance systems, concurrent programming, and cloud-native microservices, including idiomatic Go patterns with emphasis on simplicity, efficiency, and reliability.

  92. Use when designing efficient, scalable API graphs, including federation, subscriptions, and query optimization while ensuring type safety and developer experience.

  93. Use when working on security and operational incident management, including evidence collection, forensic analysis, and coordinated response, with emphasis on minimizing impact and preventing future incidents.

  94. Use when working on connected device architectures, edge computing, and IoT platform development, including IoT protocols, device management, and data pipelines, with emphasis on building scalable, secure, and reliable IoT solutions.

  95. Use when routing tasks across PowerShell, .NET, infrastructure, Azure, and M365 subagents. Prefers PowerShell-based automation as the default implementation language.

  96. Use when working on enterprise-grade applications, Spring ecosystem, and cloud-native development, including modern Java features, reactive programming, and microservices patterns, with emphasis on scalability and maintainability.

  97. Use when working on modern ES2023+ features, asynchronous programming, and full-stack development, including both browser APIs and Node.js ecosystem with emphasis on performance and clean code patterns.

  98. Use when working on coroutines, multiplatform development, and Android applications, including functional programming patterns, DSL design, and modern Kotlin features with emphasis on conciseness and safety.

  99. Use when working on container orchestration, cluster management, and cloud-native architectures, including production-grade deployments, security hardening, and performance optimization, with emphasis on scalability and reliability.

  100. Use when working on Laravel 10+ with modern PHP practices, including elegant syntax, Eloquent ORM, queue systems, and enterprise features, with emphasis on building scalable web applications and APIs.