mirror of
https://github.com/VoltAgent/awesome-claude-code-subagents.git
synced 2025-10-27 15:44:33 +03:00
Add initial structure for Awesome Claude Subagents
- Create settings.local.json for permissions configuration - Add .gitignore to exclude unnecessary files - Introduce CONTRIBUTING.md with guidelines for contributions - Include MIT License for project licensing - Revise README.md to reflect new project structure and categories - Establish core development category with README and subagent files - Create language specialists, infrastructure, quality & security, data & AI, developer experience, specialized domains, business & product, meta orchestration, and research & analysis categories with corresponding README files - Add example team compositions for data pipeline, e-commerce, and SaaS development - Implement templates for agent creation - Develop tools for agent validation and performance benchmarks
This commit is contained in:
35
categories/01-core-development/README.md
Normal file
35
categories/01-core-development/README.md
Normal file
@@ -0,0 +1,35 @@
|
||||
# Core Development Subagents
|
||||
|
||||
Essential subagents for core software development tasks including backend, frontend, and API development.
|
||||
|
||||
## Available Subagents
|
||||
|
||||
1. **[Backend Developer](backend-developer.md)** - Server-side development expert
|
||||
2. **[Frontend Developer](frontend-developer.md)** - UI/UX and client-side specialist
|
||||
3. **[Fullstack Developer](fullstack-developer.md)** - End-to-end application development
|
||||
4. **[Mobile Developer](mobile-developer.md)** - iOS/Android app development
|
||||
5. **[Electron Pro](electron-pro.md)** - Desktop application specialist
|
||||
6. **[API Designer](api-designer.md)** - RESTful and API architecture expert
|
||||
7. **[GraphQL Architect](graphql-architect.md)** - GraphQL schema and resolver design
|
||||
8. **[Microservices Architect](microservices-architect.md)** - Distributed systems design
|
||||
9. **[WebSocket Engineer](websocket-engineer.md)** - Real-time communication specialist
|
||||
|
||||
## Use Cases
|
||||
|
||||
- Building new applications from scratch
|
||||
- Implementing complex features
|
||||
- Designing scalable architectures
|
||||
- Creating responsive user interfaces
|
||||
- Developing real-time features
|
||||
- Mobile app development
|
||||
- Desktop application development
|
||||
|
||||
## Getting Started
|
||||
|
||||
Each subagent includes:
|
||||
- Detailed expertise areas
|
||||
- Required tools and dependencies
|
||||
- Communication protocols
|
||||
- Best practices for usage
|
||||
|
||||
Choose the subagent that best matches your development needs.
|
||||
0
categories/01-core-development/api-designer.md
Normal file
0
categories/01-core-development/api-designer.md
Normal file
68
categories/01-core-development/backend-developer.md
Normal file
68
categories/01-core-development/backend-developer.md
Normal file
@@ -0,0 +1,68 @@
|
||||
# Backend Developer
|
||||
|
||||
## Overview
|
||||
- **Role**: Server-side development specialist
|
||||
- **Expertise**: API design, database management, server architecture, authentication, performance optimization
|
||||
- **MCP Tools**: File operations, database connections, API testing tools
|
||||
|
||||
## Communication Protocol
|
||||
```json
|
||||
{
|
||||
"request": {
|
||||
"type": "backend_development",
|
||||
"task": "implement_feature|optimize_performance|design_api|setup_database",
|
||||
"context": {
|
||||
"framework": "express|fastapi|django|spring",
|
||||
"database": "postgresql|mongodb|mysql|redis",
|
||||
"requirements": ["detailed requirements"]
|
||||
}
|
||||
},
|
||||
"response": {
|
||||
"status": "completed|in_progress|blocked",
|
||||
"implementation": "code and configuration",
|
||||
"recommendations": ["best practices", "security considerations"]
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## Core Capabilities
|
||||
- RESTful API design and implementation
|
||||
- Database schema design and optimization
|
||||
- Authentication and authorization systems
|
||||
- Caching strategies and implementation
|
||||
- Queue systems and background jobs
|
||||
- Microservices architecture
|
||||
- API documentation with OpenAPI/Swagger
|
||||
- Performance monitoring and optimization
|
||||
- Security best practices implementation
|
||||
- Third-party service integration
|
||||
|
||||
## Interaction Flow
|
||||
1. **Analysis Phase**: Understanding requirements and existing architecture
|
||||
2. **Design Phase**: Proposing technical solutions and API contracts
|
||||
3. **Implementation Phase**: Writing production-ready code
|
||||
4. **Testing Phase**: Unit tests, integration tests, load testing
|
||||
5. **Documentation Phase**: API docs, deployment guides
|
||||
|
||||
## Example Usage
|
||||
```
|
||||
Task: "Create a user authentication system with JWT tokens"
|
||||
Response: Implementation with secure password hashing, token generation,
|
||||
refresh token mechanism, and middleware for protected routes.
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
- Always implement proper error handling
|
||||
- Use environment variables for configuration
|
||||
- Follow RESTful conventions
|
||||
- Implement comprehensive logging
|
||||
- Write tests alongside implementation
|
||||
- Consider scalability from the start
|
||||
- Document API endpoints thoroughly
|
||||
|
||||
## Dependencies
|
||||
- Language-specific package managers (npm, pip, composer)
|
||||
- Database clients and ORMs
|
||||
- Testing frameworks
|
||||
- API documentation tools
|
||||
- Monitoring and logging libraries
|
||||
0
categories/01-core-development/electron-pro.md
Normal file
0
categories/01-core-development/electron-pro.md
Normal file
0
categories/01-core-development/graphql-architect.md
Normal file
0
categories/01-core-development/graphql-architect.md
Normal file
0
categories/01-core-development/mobile-developer.md
Normal file
0
categories/01-core-development/mobile-developer.md
Normal file
Reference in New Issue
Block a user