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

.claude/settings.local.json

@@ -0,0 +1,8 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(touch:*)"
+    ],
+    "deny": []
+  }
+}

.gitignore

@@ -0,0 +1,13 @@
+.DS_Store
+*.log
+node_modules/
+.env
+.idea/
+.vscode/
+__pycache__/
+*.pyc
+.pytest_cache/
+.coverage
+dist/
+build/
+*.egg-info/

CONTRIBUTING.md

@@ -0,0 +1,49 @@
+# Contributing to Awesome Claude Subagents
+
+Thank you for your interest in contributing to this collection!
+
+## 🤝 How to Contribute
+
+### Adding a New Subagent
+
+1. **Choose the right category** - Place your subagent in the most appropriate category folder
+2. **Use the template** - Follow the structure in `templates/basic-agent-template.md`
+3. **Test your subagent** - Ensure it works with Claude Code
+4. **Submit a PR** - Include a clear description of the subagent's purpose
+
+### Subagent Requirements
+
+Each subagent should include:
+- Clear role definition
+- List of expertise areas
+- Required MCP tools (if any)
+- Communication protocol examples
+- Core capabilities
+- Example usage scenarios
+- Best practices
+
+### Code of Conduct
+
+- Be respectful and inclusive
+- Provide constructive feedback
+- Test contributions before submitting
+- Follow the existing format and structure
+
+### Pull Request Process
+
+1. Fork the repository
+2. Create a feature branch (`git checkout -b feature/new-subagent`)
+3. Add your subagent following the template
+4. Update the category README if needed
+5. Submit a pull request with a clear description
+
+### Quality Guidelines
+
+- Subagents should be production-ready
+- Include clear documentation
+- Provide practical examples
+- Ensure compatibility with Claude Code
+
+## 📝 License
+
+By contributing, you agree that your contributions will be licensed under the MIT License.

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Awesome Claude Subagents Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -1,65 +1,38 @@
-# 🤖 awesome-claude-code-subagents
+# Awesome Claude Subagents 🤖
 
-A curated list of Claude sub-agent designs, helper prompts, and modular tools that make it easier to build multi-step AI workflows — especially for coding, reasoning, and structured task delegation.
+A curated collection of production-ready Claude Code subagents for various development tasks.
 
-This collection focuses on **Claude-based sub-agents**: small, focused units that help orchestrate or handle specific steps within a larger AI agent system.
+## 🚀 Quick Start
 
----
+1. Browse categories to find the subagent you need
+2. Copy the subagent definition
+3. Use with Claude Code or integrate into your workflow
 
-## 🧩 What Are Sub-Agents?
+## 📚 Categories
 
-Sub-agents (or helper agents) are modular AI behaviors that handle isolated responsibilities — like:
+- **[Core Development](categories/01-core-development/)** - Backend, Frontend, API development
+- **[Language Specialists](categories/02-language-specialists/)** - Language-specific experts
+- **[Infrastructure](categories/03-infrastructure/)** - DevOps, Cloud, Deployment
+- **[Quality & Security](categories/04-quality-security/)** - Testing, Security, Code Review
+- **[Data & AI](categories/05-data-ai/)** - Data Engineering, ML, AI
+- **[Developer Experience](categories/06-developer-experience/)** - Tooling, Refactoring
+- **[Specialized Domains](categories/07-specialized-domains/)** - Payment, Blockchain, IoT
+- **[Business & Product](categories/08-business-product/)** - PM, Business Analysis
+- **[Meta & Orchestration](categories/09-meta-orchestration/)** - Agent Coordination
+- **[Research & Analysis](categories/10-research-analysis/)** - Research, Search
 
-- 🔍 Searching for files
-- 🛠 Refactoring code blocks
-- 🧠 Suggesting architecture changes
-- 📄 Generating documentation
-- 📦 Running tests or validations
+## ⭐ Popular Subagents
 
-In Claude-based systems, sub-agents help break down complex coding workflows into reliable, explainable, and reusable steps.
+1. [Backend Developer](categories/01-core-development/backend-developer.md)
+2. [Frontend Developer](categories/01-core-development/frontend-developer.md)
+3. [Agent Organizer](categories/09-meta-orchestration/agent-organizer.md)
+4. [Code Reviewer](categories/04-quality-security/code-reviewer.md)
+5. [Data Engineer](categories/05-data-ai/data-engineer.md)
 
----
+## 🤝 Contributing
 
-## 📦 What's Inside?
+See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
 
-- 🧠 **Claude Prompt Patterns for Sub-Agents**  
-  Examples of how to structure prompts for focused responsibilities.
+## 📄 License
 
-- ⚙️ **Sub-Agent Templates**  
-  Standard input/output shapes for common tasks like refactoring, summarizing, or evaluating code.
-
-- 🛠 **Real-World Use Cases**  
-  Modular building blocks for larger Claude agents (e.g., supervisors, tool-using agents, CI assistants).
-
-- 🌐 **Related Projects**  
-  Pointers to open source frameworks using sub-agent strategies.
-
----
-
-## 🧪 Example Sub-Agent Patterns
-
-- `codeReviewerAgent(prompt, diff) → suggestions[]`
-- `functionExplainerAgent(code) → explanation`
-- `fileRouterAgent(filePaths[], goal) → relevantFiles[]`
-- `testWriterAgent(fnCode) → testCode`
-
-Each sub-agent focuses on one responsibility, and can be composed into more complex Claude agents.
-
----
-
-## 🤝 Contribute
-
-Pull requests and issue suggestions welcome!  
-If you're building Claude-based agents or helper functions, feel free to share your patterns here.
-
----
-
-## 📚 Related
-
-- [VoltAgent](https://github.com/voltagent/voltagent) – Open-source TypeScript AI agent framework with Claude support
-
----
-
-## 📝 License
-
-MIT
+MIT License - see [LICENSE](LICENSE)

categories/01-core-development/README.md

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

categories/01-core-development/backend-developer.md

@@ -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