### Getting Started Guide Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/07-specialized-domains/README.md Provides a step-by-step guide for getting started with the project, emphasizing understanding domain requirements, choosing appropriate specialists, considering compliance, planning for challenges, and leveraging domain expertise. ```markdown 1. **Understand domain requirements** and constraints 2. **Choose appropriate specialists** for your domain 3. **Consider regulatory compliance** if applicable 4. **Plan for domain-specific challenges** early 5. **Leverage domain expertise** throughout development ``` -------------------------------- ### Getting Started with Subagents Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/03-infrastructure/README.md A step-by-step guide on how to get started with the subagents, including assessing needs, choosing specialists, providing context, and sharing configurations. ```markdown 1. **Assess your infrastructure needs** and current challenges 2. **Choose the appropriate specialist** based on your requirements 3. **Provide context** about your environment and constraints 4. **Share existing configurations** if applicable 5. **Follow the specialist's recommendations** for best practices ``` -------------------------------- ### Getting Started with Subagents Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/02-language-specialists/README.md A step-by-step guide on how to get started with Claude code subagents, from identifying your technology stack to providing context and following guidance. ```Markdown List 1. **Identify your technology stack** and choose the appropriate specialist 2. **Describe your project context** including existing code and constraints 3. **Specify your goals** (learning, optimization, implementation) 4. **Share relevant code** for context-aware assistance 5. **Follow the specialist's guidance** for best practices ``` -------------------------------- ### Getting Started with Quality and Security Subagents Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/04-quality-security/README.md A step-by-step guide on how to begin using the quality and security subagents. It outlines the process from identifying concerns to implementing recommended improvements. ```markdown 1. **Identify quality concerns** in your application 2. **Choose appropriate specialists** for your needs 3. **Provide application context** and existing issues 4. **Share relevant code and logs** for analysis 5. **Implement recommended improvements** systematically ``` -------------------------------- ### Getting Started with Claude Subagents Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/08-business-product/README.md This guide outlines the essential steps for initiating projects using Claude subagents, emphasizing clear objective setting and effective collaboration. ```APIDOC GettingStarted: Steps: - Step: 1 Action: Identify business objectives clearly - Step: 2 Action: Choose specialists that align with goals - Step: 3 Action: Provide business context and constraints - Step: 4 Action: Foster collaboration between specialists - Step: 5 Action: Measure business impact continuously ``` -------------------------------- ### Getting Started Steps Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/05-data-ai/README.md A concise guide to initiating data and AI projects, emphasizing clear objective definition, landscape assessment, specialist selection, context provision, and adherence to best practices. ```markdown 1. **Define your data/AI objectives** clearly 2. **Assess your data landscape** and requirements 3. **Choose appropriate specialists** for your needs 4. **Provide data context** and constraints 5. **Follow best practices** for implementation ``` -------------------------------- ### Automation Examples in Development Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/06-developer-experience/dx-optimizer.md Lists common examples of automation that can be implemented to streamline development workflows and reduce manual effort. ```text - Code generation - Dependency updates - Release automation - Documentation generation - Environment setup - Database migrations - API mocking - Performance monitoring ``` -------------------------------- ### Subagent Selection Guide Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/01-core-development/README.md A quick guide to selecting the appropriate subagent based on project needs, including a specific recommendation for real-time features. ```markdown | If you need to... | Use this subagent | |-------------------|-------------------| | Build a REST API with database | **backend-developer** | | Create a responsive web UI | **frontend-developer** | | Develop a complete web application | **fullstack-developer** | | Build a mobile app | **mobile-developer** | | Create a desktop application | **electron-pro** | | Design a new API structure | **api-designer** | | Implement GraphQL | **graphql-architect** | | Build a distributed system | **microservices-architect** | | Add real-time features | **websocket-engineer** | ``` -------------------------------- ### Delivery Notification Example Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/07-specialized-domains/api-documenter.md An example of a delivery notification message confirming the completion of API documentation, including key metrics and achievements. ```APIDOC Delivery Notification: "API documentation completed. Documented 127 endpoints with 453 examples across 8 SDK languages. Implemented interactive try-it-out console with 94% success rate. User satisfaction increased from 3.1 to 4.7/5. Reduced support tickets by 67%." ``` -------------------------------- ### Quick Selection Guide - Infrastructure Tasks Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/03-infrastructure/README.md A quick reference guide mapping common infrastructure needs to the appropriate subagent, such as cloud architecture, database management, CI/CD, and security. ```markdown | If you need to... | Use this subagent | |-------------------|-------------------| | Design cloud architecture | **cloud-architect** | | Manage databases | **database-administrator** | | Automate deployments | **deployment-engineer** | | Build CI/CD pipelines | **devops-engineer** | | Handle DevOps incidents | **devops-incident-responder** | | Manage critical outages | **incident-responder** | | Deploy with Kubernetes | **kubernetes-specialist** | | Design networks | **network-engineer** | | Build developer platforms | **platform-engineer** | | Secure infrastructure | **security-engineer** | | Implement SRE practices | **sre-engineer** | | Write infrastructure code | **terraform-engineer** | ``` -------------------------------- ### Delivery Notification Example Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/09-meta-orchestration/context-manager.md An example of a delivery notification message for the context management system, highlighting key performance metrics and achievements. ```text Context management system completed. Managing 2.3M contexts with 47ms average retrieval time. Cache hit rate 89% with 100% consistency score. Reduced storage costs by 43% through intelligent tiering and compression. ``` -------------------------------- ### Python Environment Context Query Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/02-language-specialists/python-pro.md A JSON payload used to request detailed context about a Python development environment. It specifies the information needed, such as interpreter version, installed packages, virtual environment setup, code style configuration, testing frameworks, type checking setup, and CI/CD pipeline status. ```JSON { "requesting_agent": "python-pro", "request_type": "get_python_context", "payload": { "query": "Python environment needed: interpreter version, installed packages, virtual env setup, code style config, test framework, type checking setup, and CI/CD pipeline." } } ``` -------------------------------- ### Monitoring Setup Components Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/05-data-ai/database-optimizer.md Details the components required for setting up effective database performance monitoring, including metrics, alerts, and dashboards. ```APIDOC Monitoring setup: - Performance metrics - Query statistics - Wait events - Lock analysis - Resource tracking - Trend analysis - Alert thresholds - Dashboard creation ``` -------------------------------- ### Delivery Notification Example Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/08-business-product/technical-writer.md An example of a delivery notification summarizing the impact and success of documentation efforts. ```APIDOC Delivery Notification: "Documentation completed. Created 127 pages covering 45 APIs with average readability score of 68. User satisfaction increased to 92% with 73% reduction in support tickets. Documentation-driven adoption increased by 45%." ``` -------------------------------- ### Distribution Checklist and Report Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/01-core-development/electron-pro.md Details the essential steps for preparing a desktop application for distribution, including code signing, notarization, installer generation, testing, security audits, and documentation. It also includes a sample completion report summarizing the application's features, platform support, performance, and security. ```APIDOC Distribution Checklist: - Code signing completed - Notarization processed - Installers generated - Auto-update tested - Performance validated - Security audit passed - Documentation ready - Support channels setup Completion Report: "Desktop application delivered successfully. Built secure Electron app supporting Windows 10+, macOS 11+, and Ubuntu 20.04+. Features include native OS integration, auto-updates with rollback, system tray, and native notifications. Achieved 2.5s startup, 180MB memory idle, with hardened security configuration. Ready for distribution." ``` -------------------------------- ### Delivery Notification Example Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/07-specialized-domains/game-developer.md An example of a delivery notification summarizing key achievements in game development. ```text Game development completed. Achieved stable 72 FPS across all platforms with 2.3s load times. Implemented ECS architecture supporting 1000+ entities. Multiplayer supports 64 players with 45ms average latency. Reduced build size by 40% through asset optimization. ``` -------------------------------- ### Plugin Examples Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/06-developer-experience/tooling-engineer.md Examples of functionalities that can be implemented as plugins for a CLI tool, extending its capabilities. ```text - Custom commands - Output formatters - Integration adapters - Transform pipelines - Validation rules - Code generators - Report generators - Custom workflows ``` -------------------------------- ### Delivery Notification Example Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/04-quality-security/debugger.md An example of a delivery notification message detailing the debugging process, root cause, fix, and impact. ```text Debugging completed. Identified root cause as race condition in cache invalidation logic occurring under high load. Implemented mutex-based synchronization fix, reducing error rate from 15% to 0%. Created detailed postmortem and added monitoring to prevent recurrence. ``` -------------------------------- ### Quick Selection Guide for Subagents Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/09-meta-orchestration/README.md A quick selection guide mapping common needs to specific Meta & Orchestration subagents, facilitating efficient choice for coordinating agents, managing context, handling errors, synthesizing knowledge, scaling operations, monitoring performance, distributing tasks, and automating workflows. ```markdown ## = Quick Selection Guide | If you need to... | Use this subagent | |-------------------|-------------------| | Coordinate multiple agents | **agent-organizer** | | Manage context efficiently | **context-manager** | | Handle system errors | **error-coordinator** | | Combine knowledge sources | **knowledge-synthesizer** | | Scale agent operations | **multi-agent-coordinator** | | Monitor performance | **performance-monitor** | | Distribute tasks | **task-distributor** | | Automate workflows | **workflow-orchestrator** | ``` -------------------------------- ### Performance Evaluation Steps Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/05-data-ai/database-optimizer.md Details the steps involved in performance evaluation, including baseline collection, bottleneck analysis, and target setting. ```APIDOC Performance evaluation: - Collect baselines - Identify bottlenecks - Analyze patterns - Review configurations - Check indexes - Assess schemas - Plan optimizations - Set targets ``` -------------------------------- ### Build Strategies for DX Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/06-developer-experience/dx-optimizer.md Lists various build strategies that contribute to a better developer experience, focusing on speed and efficiency. ```text - Incremental builds - Module federation - Build caching - Parallel compilation - Lazy loading - Tree shaking - Source map optimization - Asset pipeline ``` -------------------------------- ### Delivery Notification Example Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/09-meta-orchestration/task-distributor.md An example of a delivery notification message from the task distribution system, summarizing key performance metrics and achievements. ```text Task distribution system completed. Distributed 45K tasks with 230ms average queue time and 7% load variance. Achieved 97% deadline success rate with 84% resource utilization. Reduced task wait time by 67% through intelligent routing. ``` -------------------------------- ### API Documentation Best Practices and Features Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/07-specialized-domains/api-documenter.md This entry consolidates best practices for OpenAPI specifications, portal features, example strategies, automation techniques, and user experience considerations for API documentation. ```APIDOC OpenAPI Best Practices: - Descriptive summaries - Detailed descriptions - Meaningful examples - Consistent naming - Proper typing - Reusable components - Security definitions - Extension usage Portal Features: - Smart search - Code highlighting - Version switcher - Language selector - Dark mode - Export options - Bookmark support - Analytics tracking Example Strategies: - Real-world scenarios - Edge cases - Error examples - Success paths - Common patterns - Advanced usage - Performance tips - Security practices Documentation Automation: - CI/CD integration - Auto-generation - Validation checks - Link checking - Version syncing - Change detection - Update notifications - Quality metrics User Experience: - Clear navigation - Quick search - Copy buttons - Syntax highlighting - Responsive design - Print friendly - Offline access - Feedback widgets ``` -------------------------------- ### Next.js Delivery Notification Example Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/02-language-specialists/nextjs-developer.md An example of a delivery notification message for a completed Next.js application, highlighting key metrics and features. ```text Next.js application completed. Built 24 routes with 18 API endpoints achieving 98 Lighthouse score. Implemented full App Router architecture with server components and edge runtime. Deploy time optimized to 45s. ``` -------------------------------- ### Implementation Approach Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/05-data-ai/database-optimizer.md Describes the approach for implementing database optimizations, focusing on queries, indexes, configuration, and schemas. ```APIDOC Implementation approach: - Optimize queries - Design indexes - Tune configuration - Adjust schemas - Improve caching - Reduce contention - Monitor impact - Document changes ``` -------------------------------- ### Index Strategy Guidelines Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/05-data-ai/database-optimizer.md Outlines best practices for index strategy, covering selection, covering indexes, maintenance, and bloat prevention. ```APIDOC Index strategy: - Index selection - Covering indexes - Partial indexes - Expression indexes - Multi-column ordering - Index maintenance - Bloat prevention - Statistics updates ``` -------------------------------- ### Delivery Notification Example Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/01-core-development/backend-developer.md An example of a delivery notification message from the backend developer, summarizing the implemented microservice architecture, technologies used, and key performance metrics. ```plaintext Backend implementation complete. Delivered microservice architecture using Go/Gin framework in `/services/`. Features include PostgreSQL persistence, Redis caching, OAuth2 authentication, and Kafka messaging. Achieved 88% test coverage with sub-100ms p95 latency. ``` -------------------------------- ### I/O Optimization Strategies Source: https://github.com/voltagent/awesome-claude-code-subagents/blob/main/categories/05-data-ai/database-optimizer.md Covers strategies for I/O optimization, such as storage layout, read-ahead tuning, and SSD optimization. ```APIDOC I/O optimization: - Storage layout - Read-ahead tuning - Write combining - Checkpoint tuning - Log optimization - Tablespace design - File distribution - SSD optimization ```