External/SuperClaude
1
0
Fork 0
mirror of https://github.com/SuperClaude-Org/SuperClaude_Framework.git synced 2025-12-29 16:16:08 +00:00
Code Issues Packages Projects Releases Wiki Activity
SuperClaude/SuperClaude/Commands/improve.md
NomenAK 40840dae0b Restructure documentation: Create focused guide ecosystem from oversized user guide 
- Transform 28K+ token superclaude-user-guide.md into 4.5K token overview (84% reduction)
- Extract specialized guides: examples-cookbook.md, troubleshooting-guide.md, best-practices.md, session-management.md, technical-architecture.md
- Add comprehensive cross-references between all guides for improved navigation
- Maintain professional documentation quality with technical-writer agent approach
- Remove template files and consolidate agent naming (backend-engineer → backend-architect, etc.)
- Update all existing guides with cross-references and related guides sections
- Create logical learning paths from beginner to advanced users
- Eliminate content duplication while preserving all valuable information

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-08-15 21:30:29 +02:00

3.9 KiB
Raw Blame History

name description category complexity mcp-servers personas
improve Apply systematic improvements to code quality, performance, and maintainability workflow standard
sequential
context7
architect
performance
quality
security

/sc:improve - Code Improvement

Triggers

  • Code quality enhancement and refactoring requests
  • Performance optimization and bottleneck resolution needs
  • Maintainability improvements and technical debt reduction
  • Best practices application and coding standards enforcement

Usage

/sc:improve [target] [--type quality|performance|maintainability|style] [--safe] [--interactive]

Behavioral Flow

  1. Analyze: Examine codebase for improvement opportunities and quality issues
  2. Plan: Choose improvement approach and activate relevant personas for expertise
  3. Execute: Apply systematic improvements with domain-specific best practices
  4. Validate: Ensure improvements preserve functionality and meet quality standards
  5. Document: Generate improvement summary and recommendations for future work

Key behaviors:

  • Multi-persona coordination (architect, performance, quality, security) based on improvement type
  • Framework-specific optimization via Context7 integration for best practices
  • Systematic analysis via Sequential MCP for complex multi-component improvements
  • Safe refactoring with comprehensive validation and rollback capabilities

MCP Integration

  • Sequential MCP: Auto-activated for complex multi-step improvement analysis and planning
  • Context7 MCP: Framework-specific best practices and optimization patterns
  • Persona Coordination: Architect (structure), Performance (speed), Quality (maintainability), Security (safety)

Tool Coordination

  • Read/Grep/Glob: Code analysis and improvement opportunity identification
  • Edit/MultiEdit: Safe code modification and systematic refactoring
  • TodoWrite: Progress tracking for complex multi-file improvement operations
  • Task: Delegation for large-scale improvement workflows requiring systematic coordination

Key Patterns

  • Quality Improvement: Code analysis → technical debt identification → refactoring application
  • Performance Optimization: Profiling analysis → bottleneck identification → optimization implementation
  • Maintainability Enhancement: Structure analysis → complexity reduction → documentation improvement
  • Security Hardening: Vulnerability analysis → security pattern application → validation verification

Examples

Code Quality Enhancement

/sc:improve src/ --type quality --safe
# Systematic quality analysis with safe refactoring application
# Improves code structure, reduces technical debt, enhances readability

Performance Optimization

/sc:improve api-endpoints --type performance --interactive
# Performance persona analyzes bottlenecks and optimization opportunities
# Interactive guidance for complex performance improvement decisions

Maintainability Improvements

/sc:improve legacy-modules --type maintainability --preview
# Architect persona analyzes structure and suggests maintainability improvements
# Preview mode shows changes before application for review

Security Hardening

/sc:improve auth-service --type security --validate
# Security persona identifies vulnerabilities and applies security patterns
# Comprehensive validation ensures security improvements are effective

Boundaries

Will:

  • Apply systematic improvements with domain-specific expertise and validation
  • Provide comprehensive analysis with multi-persona coordination and best practices
  • Execute safe refactoring with rollback capabilities and quality preservation

Will Not:

  • Apply risky improvements without proper analysis and user confirmation
  • Make architectural changes without understanding full system impact
  • Override established coding standards or project-specific conventions