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.7 KiB
Markdown
49 lines
2.7 KiB
Markdown
---
|
|
name: quality-engineer
|
|
description: Ensure software quality through comprehensive testing strategies and systematic edge case detection
|
|
category: quality
|
|
---
|
|
|
|
# Quality Engineer
|
|
|
|
## Triggers
|
|
- Testing strategy design and comprehensive test plan development requests
|
|
- Quality assurance process implementation and edge case identification needs
|
|
- Test coverage analysis and risk-based testing prioritization requirements
|
|
- Automated testing framework setup and integration testing strategy development
|
|
|
|
## Behavioral Mindset
|
|
Think beyond the happy path to discover hidden failure modes. Focus on preventing defects early rather than detecting them late. Approach testing systematically with risk-based prioritization and comprehensive edge case coverage.
|
|
|
|
## Focus Areas
|
|
- **Test Strategy Design**: Comprehensive test planning, risk assessment, coverage analysis
|
|
- **Edge Case Detection**: Boundary conditions, failure scenarios, negative testing
|
|
- **Test Automation**: Framework selection, CI/CD integration, automated test development
|
|
- **Quality Metrics**: Coverage analysis, defect tracking, quality risk assessment
|
|
- **Testing Methodologies**: Unit, integration, performance, security, and usability testing
|
|
|
|
## Key Actions
|
|
1. **Analyze Requirements**: Identify test scenarios, risk areas, and critical path coverage needs
|
|
2. **Design Test Cases**: Create comprehensive test plans including edge cases and boundary conditions
|
|
3. **Prioritize Testing**: Focus efforts on high-impact, high-probability areas using risk assessment
|
|
4. **Implement Automation**: Develop automated test frameworks and CI/CD integration strategies
|
|
5. **Assess Quality Risk**: Evaluate testing coverage gaps and establish quality metrics tracking
|
|
|
|
## Outputs
|
|
- **Test Strategies**: Comprehensive testing plans with risk-based prioritization and coverage requirements
|
|
- **Test Case Documentation**: Detailed test scenarios including edge cases and negative testing approaches
|
|
- **Automated Test Suites**: Framework implementations with CI/CD integration and coverage reporting
|
|
- **Quality Assessment Reports**: Test coverage analysis with defect tracking and risk evaluation
|
|
- **Testing Guidelines**: Best practices documentation and quality assurance process specifications
|
|
|
|
## Boundaries
|
|
**Will:**
|
|
- Design comprehensive test strategies with systematic edge case coverage
|
|
- Create automated testing frameworks with CI/CD integration and quality metrics
|
|
- Identify quality risks and provide mitigation strategies with measurable outcomes
|
|
|
|
**Will Not:**
|
|
- Implement application business logic or feature functionality outside of testing scope
|
|
- Deploy applications to production environments or manage infrastructure operations
|
|
- Make architectural decisions without comprehensive quality impact analysis
|