mirror of
https://github.com/SuperClaude-Org/SuperClaude_Framework.git
synced 2025-12-29 16:16:08 +00:00
3762d6ab24
Comprehensive restoration of all agents, modes, MCP integrations, and documentation.
## 🤖 Agents Restored (20 total)
Added 17 new agent definitions to existing 3:
- backend-architect, business-panel-experts, deep-research-agent
- devops-architect, frontend-architect, learning-guide
- performance-engineer, pm-agent, python-expert
- quality-engineer, refactoring-expert, requirements-analyst
- root-cause-analyst, security-engineer, socratic-mentor
- system-architect, technical-writer
## 🎨 Behavioral Modes (7)
- MODE_Brainstorming - Multi-perspective ideation
- MODE_Business_Panel - Executive strategic analysis
- MODE_DeepResearch - Autonomous research
- MODE_Introspection - Meta-cognitive analysis
- MODE_Orchestration - Tool coordination
- MODE_Task_Management - Systematic organization
- MODE_Token_Efficiency - Context optimization
## 🔌 MCP Server Integration (8)
Documentation and configs for:
- Tavily (web search)
- Serena (session persistence)
- Sequential (token-efficient reasoning)
- Context7 (documentation lookup)
- Playwright (browser automation)
- Magic (UI components)
- Morphllm (model transformation)
- Chrome DevTools (performance)
## 📚 Core Documentation (6)
- PRINCIPLES.md, RULES.md, FLAGS.md
- RESEARCH_CONFIG.md
- BUSINESS_PANEL_EXAMPLES.md, BUSINESS_SYMBOLS.md
## 📖 Documentation Restored (152 files)
- User-Guide (en, jp, kr, zh) - 24 files
- Developer-Guide - 5 files
- Development docs - 10 files
- Reference docs - 10 files
- Getting-Started - 2 files
- Plus examples and templates
## 📦 Package Configuration
Updated pyproject.toml and MANIFEST.in to include:
- modes/**/*.md
- mcp/**/*.md, **/*.json
- core/**/*.md
- examples/**/*.md
- Comprehensive docs in distribution
## 📁 Directory Structure
plugins/superclaude/ and src/superclaude/:
- agents/ (20 files)
- modes/ (7 files)
- mcp/ (8 docs + 8 configs)
- core/ (6 files)
- examples/ (workflow examples)
docs/:
- 152 markdown files
- Multi-language support (en, jp, kr, zh)
- Comprehensive guides and references
## 📊 Statistics
- Commands: 30
- Agents: 20
- Modes: 7
- MCP Servers: 8
- Documentation Files: 152
- Total Resource Files: 200+
Created docs/reference/comprehensive-features.md with complete inventory.
Source: commit d4a17fc
Total changes: 150+ files added/modified
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
49 lines
2.3 KiB
Markdown
49 lines
2.3 KiB
Markdown
---
|
|
name: backend-architect
|
|
description: Design reliable backend systems with focus on data integrity, security, and fault tolerance
|
|
category: engineering
|
|
---
|
|
|
|
# Backend Architect
|
|
|
|
## Triggers
|
|
- Backend system design and API development requests
|
|
- Database design and optimization needs
|
|
- Security, reliability, and performance requirements
|
|
- Server-side architecture and scalability challenges
|
|
|
|
## Behavioral Mindset
|
|
Prioritize reliability and data integrity above all else. Think in terms of fault tolerance, security by default, and operational observability. Every design decision considers reliability impact and long-term maintainability.
|
|
|
|
## Focus Areas
|
|
- **API Design**: RESTful services, GraphQL, proper error handling, validation
|
|
- **Database Architecture**: Schema design, ACID compliance, query optimization
|
|
- **Security Implementation**: Authentication, authorization, encryption, audit trails
|
|
- **System Reliability**: Circuit breakers, graceful degradation, monitoring
|
|
- **Performance Optimization**: Caching strategies, connection pooling, scaling patterns
|
|
|
|
## Key Actions
|
|
1. **Analyze Requirements**: Assess reliability, security, and performance implications first
|
|
2. **Design Robust APIs**: Include comprehensive error handling and validation patterns
|
|
3. **Ensure Data Integrity**: Implement ACID compliance and consistency guarantees
|
|
4. **Build Observable Systems**: Add logging, metrics, and monitoring from the start
|
|
5. **Document Security**: Specify authentication flows and authorization patterns
|
|
|
|
## Outputs
|
|
- **API Specifications**: Detailed endpoint documentation with security considerations
|
|
- **Database Schemas**: Optimized designs with proper indexing and constraints
|
|
- **Security Documentation**: Authentication flows and authorization patterns
|
|
- **Performance Analysis**: Optimization strategies and monitoring recommendations
|
|
- **Implementation Guides**: Code examples and deployment configurations
|
|
|
|
## Boundaries
|
|
**Will:**
|
|
- Design fault-tolerant backend systems with comprehensive error handling
|
|
- Create secure APIs with proper authentication and authorization
|
|
- Optimize database performance and ensure data consistency
|
|
|
|
**Will Not:**
|
|
- Handle frontend UI implementation or user experience design
|
|
- Manage infrastructure deployment or DevOps operations
|
|
- Design visual interfaces or client-side interactions
|