From 90716ab7b86a7bf8f4fc5bc514f2b0a46f25082c Mon Sep 17 00:00:00 2001 From: NomenAK Date: Mon, 14 Jul 2025 18:34:01 +0200 Subject: [PATCH] docs: comprehensive documentation update and command system enhancement MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Update all command documentation with improved clarity and examples - Enhance user guides with simplified activation patterns - Improve installation and setup documentation - Refine command system implementation in setup components - Update changelog with recent improvements ๐Ÿค– Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude --- CHANGELOG.md | 44 ++ Docs/commands-guide.md | 246 +++++----- Docs/flags-guide.md | 86 ++-- Docs/installation-guide.md | 8 +- Docs/personas-guide.md | 164 +++---- Docs/superclaude-user-guide.md | 664 +++++++++++++-------------- README.md | 8 +- SuperClaude/Commands/analyze.md | 4 +- SuperClaude/Commands/build.md | 4 +- SuperClaude/Commands/cleanup.md | 4 +- SuperClaude/Commands/design.md | 4 +- SuperClaude/Commands/document.md | 4 +- SuperClaude/Commands/estimate.md | 4 +- SuperClaude/Commands/explain.md | 4 +- SuperClaude/Commands/git.md | 4 +- SuperClaude/Commands/improve.md | 4 +- SuperClaude/Commands/index.md | 4 +- SuperClaude/Commands/load.md | 4 +- SuperClaude/Commands/spawn.md | 4 +- SuperClaude/Commands/task.md | 12 +- SuperClaude/Commands/test.md | 4 +- SuperClaude/Commands/troubleshoot.md | 4 +- setup/components/commands.py | 116 ++++- 23 files changed, 769 insertions(+), 635 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index e69de29..a3eda37 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -0,0 +1,44 @@ +# Changelog + +All notable changes to SuperClaude will be documented in this file. + +The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), +and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). + +## [Unreleased] + +### Changed +- **BREAKING**: Commands now use `/sc:` namespace to avoid conflicts with user custom commands +- Commands are now installed in `~/.claude/commands/sc/` subdirectory +- All 15 commands updated: `/analyze` ’ `/sc:analyze`, `/build` ’ `/sc:build`, etc. +- Automatic migration from old command locations to new `sc/` subdirectory + +### Added +- Migration logic to move existing commands to new namespace automatically +- Enhanced uninstaller to handle both old and new command locations +- Improved command conflict prevention +- Better command organization and discoverability + +### Technical Details +- Commands now accessible as `/sc:analyze`, `/sc:build`, `/sc:improve`, etc. +- Migration preserves existing functionality while preventing naming conflicts +- Installation process detects and migrates existing commands automatically +- Tab completion support for `/sc:` prefix to discover all SuperClaude commands + +## [3.0.0] - 2025-07-14 + +### Added +- Initial release of SuperClaude v3.0 +- 15 specialized slash commands for development tasks +- Smart persona auto-activation system +- MCP server integration (Context7, Sequential, Magic, Playwright) +- Unified CLI installer with multiple installation profiles +- Comprehensive documentation and user guides +- Token optimization framework +- Task management system + +### Features +- **Commands**: analyze, build, cleanup, design, document, estimate, explain, git, improve, index, load, spawn, task, test, troubleshoot +- **Personas**: architect, frontend, backend, analyzer, security, mentor, refactorer, performance, qa, devops, scribe +- **MCP Servers**: Official library documentation, complex analysis, UI components, browser automation +- **Installation**: Quick, minimal, and developer profiles with component selection \ No newline at end of file diff --git a/Docs/commands-guide.md b/Docs/commands-guide.md index ec36b42..d295e25 100644 --- a/Docs/commands-guide.md +++ b/Docs/commands-guide.md @@ -18,11 +18,11 @@ **Start here** (no reading required): ```bash -/help # See what's available -/analyze src/ # Smart analysis of your code -/build # Intelligent project building -/improve messy-file.js # Clean up code automatically -/troubleshoot "error" # Get help with problems +/sc:help # See what's available +/sc:analyze src/ # Smart analysis of your code +/sc:build # Intelligent project building +/sc:improve messy-file.js # Clean up code automatically +/sc:troubleshoot "error" # Get help with problems ``` **That's honestly enough to get started.** Everything else below is here when you get curious about what other tools are available. @@ -70,11 +70,11 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Basic syntax**: ```bash -/build # Build current project -/build --type prod # Production build -/build --clean # Clean build (remove old artifacts) -/build --optimize # Enable optimizations -/build src/ # Build specific directory +/sc:build # Build current project +/sc:build --type prod # Production build +/sc:build --clean # Clean build (remove old artifacts) +/sc:build --optimize # Enable optimizations +/sc:build src/ # Build specific directory ``` **Useful flags**: @@ -85,9 +85,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Real examples**: ```bash -/build --type prod --optimize # Production build with optimizations -/build --clean --verbose # Clean build with detailed output -/build src/components # Build just the components folder +/sc:build --type prod --optimize # Production build with optimizations +/sc:build --clean --verbose # Clean build with detailed output +/sc:build src/components # Build just the components folder ``` **Gotchas**: @@ -108,9 +108,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Basic syntax**: ```bash -/design user-auth-system # Design a user authentication system -/design --type api auth # Design just the API part -/design --format spec payment # Create formal specification +/sc:design user-auth-system # Design a user authentication system +/sc:design --type api auth # Design just the API part +/sc:design --format spec payment # Create formal specification ``` **Useful flags**: @@ -120,9 +120,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Real examples**: ```bash -/design --type api user-management # Design user management API -/design --format spec chat-system # Create chat system specification -/design --type database ecommerce # Design database schema +/sc:design --type api user-management # Design user management API +/sc:design --format spec chat-system # Create chat system specification +/sc:design --type database ecommerce # Design database schema ``` **Gotchas**: @@ -145,9 +145,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Basic syntax**: ```bash -/analyze src/ # Analyze entire src directory -/analyze --focus security # Focus on security issues -/analyze --depth deep app.js # Deep analysis of specific file +/sc:analyze src/ # Analyze entire src directory +/sc:analyze --focus security # Focus on security issues +/sc:analyze --depth deep app.js # Deep analysis of specific file ``` **Useful flags**: @@ -157,9 +157,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Real examples**: ```bash -/analyze --focus security --depth deep # Deep security analysis -/analyze --focus performance src/api/ # Performance analysis of API -/analyze --format report . # Generate analysis report +/sc:analyze --focus security --depth deep # Deep security analysis +/sc:analyze --focus performance src/api/ # Performance analysis of API +/sc:analyze --format report . # Generate analysis report ``` **Gotchas**: @@ -180,9 +180,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Basic syntax**: ```bash -/troubleshoot "login not working" # Investigate login issue -/troubleshoot --logs error.log # Analyze error logs -/troubleshoot performance # Performance troubleshooting +/sc:troubleshoot "login not working" # Investigate login issue +/sc:troubleshoot --logs error.log # Analyze error logs +/sc:troubleshoot performance # Performance troubleshooting ``` **Useful flags**: @@ -192,9 +192,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Real examples**: ```bash -/troubleshoot "API returning 500" --logs server.log -/troubleshoot --focus database "slow queries" -/troubleshoot "build failing" --systematic +/sc:troubleshoot "API returning 500" --logs server.log +/sc:troubleshoot --focus database "slow queries" +/sc:troubleshoot "build failing" --systematic ``` **Gotchas**: @@ -215,9 +215,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Basic syntax**: ```bash -/explain async/await # Explain async/await concept -/explain --code src/utils.js # Explain specific code file -/explain --beginner React hooks # Beginner-friendly explanation +/sc:explain async/await # Explain async/await concept +/sc:explain --code src/utils.js # Explain specific code file +/sc:explain --beginner React hooks # Beginner-friendly explanation ``` **Useful flags**: @@ -228,9 +228,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Real examples**: ```bash -/explain --beginner "what is REST API" -/explain --code src/auth.js --advanced -/explain --examples "React context patterns" +/sc:explain --beginner "what is REST API" +/sc:explain --code src/auth.js --advanced +/sc:explain --examples "React context patterns" ``` **Gotchas**: @@ -251,9 +251,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Basic syntax**: ```bash -/improve src/legacy/ # Improve legacy code -/improve --type performance # Focus on performance -/improve --safe src/utils.js # Safe, low-risk improvements only +/sc:improve src/legacy/ # Improve legacy code +/sc:improve --type performance # Focus on performance +/sc:improve --safe src/utils.js # Safe, low-risk improvements only ``` **Useful flags**: @@ -263,9 +263,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Real examples**: ```bash -/improve --type performance --safe src/api/ -/improve --preview src/components/LegacyComponent.js -/improve --type style . --safe +/sc:improve --type performance --safe src/api/ +/sc:improve --preview src/components/LegacyComponent.js +/sc:improve --type style . --safe ``` **Gotchas**: @@ -286,9 +286,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Basic syntax**: ```bash -/cleanup src/ # Clean up src directory -/cleanup --dead-code # Focus on dead code removal -/cleanup --imports package.js # Clean up imports in specific file +/sc:cleanup src/ # Clean up src directory +/sc:cleanup --dead-code # Focus on dead code removal +/sc:cleanup --imports package.js # Clean up imports in specific file ``` **Useful flags**: @@ -299,9 +299,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Real examples**: ```bash -/cleanup --dead-code --safe src/utils/ -/cleanup --imports src/components/ -/cleanup --files . --safe +/sc:cleanup --dead-code --safe src/utils/ +/sc:cleanup --imports src/components/ +/sc:cleanup --files . --safe ``` **Gotchas**: @@ -322,10 +322,10 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Basic syntax**: ```bash -/test # Run all tests -/test --type unit # Run only unit tests -/test --coverage # Generate coverage report -/test --watch src/ # Watch mode for development +/sc:test # Run all tests +/sc:test --type unit # Run only unit tests +/sc:test --coverage # Generate coverage report +/sc:test --watch src/ # Watch mode for development ``` **Useful flags**: @@ -336,9 +336,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Real examples**: ```bash -/test --type unit --coverage -/test --watch src/components/ -/test --type e2e --fix +/sc:test --type unit --coverage +/sc:test --watch src/components/ +/sc:test --type e2e --fix ``` **Gotchas**: @@ -359,9 +359,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Basic syntax**: ```bash -/document src/api/auth.js # Document authentication module -/document --type api # API documentation -/document --style brief README # Brief README file +/sc:document src/api/auth.js # Document authentication module +/sc:document --type api # API documentation +/sc:document --style brief README # Brief README file ``` **Useful flags**: @@ -371,9 +371,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Real examples**: ```bash -/document --type api src/controllers/ -/document --style detailed --type guide user-onboarding -/document --type inline src/utils/helpers.js +/sc:document --type api src/controllers/ +/sc:document --style detailed --type guide user-onboarding +/sc:document --type inline src/utils/helpers.js ``` **Gotchas**: @@ -394,9 +394,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Basic syntax**: ```bash -/estimate "add user authentication" # Estimate auth feature -/estimate --detailed shopping-cart # Detailed breakdown -/estimate --complexity user-dashboard # Complexity analysis +/sc:estimate "add user authentication" # Estimate auth feature +/sc:estimate --detailed shopping-cart # Detailed breakdown +/sc:estimate --complexity user-dashboard # Complexity analysis ``` **Useful flags**: @@ -406,9 +406,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Real examples**: ```bash -/estimate --detailed "implement payment system" -/estimate --complexity --team-size 3 "migrate to microservices" -/estimate "add real-time chat" --detailed +/sc:estimate --detailed "implement payment system" +/sc:estimate --complexity --team-size 3 "migrate to microservices" +/sc:estimate "add real-time chat" --detailed ``` **Gotchas**: @@ -429,9 +429,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Basic syntax**: ```bash -/task create "implement user dashboard" # Create new task -/task status # Check task status -/task breakdown "payment integration" # Break down into subtasks +/sc:task create "implement user dashboard" # Create new task +/sc:task status # Check task status +/sc:task breakdown "payment integration" # Break down into subtasks ``` **Useful flags**: @@ -442,9 +442,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Real examples**: ```bash -/task create "migrate from REST to GraphQL" --priority high -/task breakdown "e-commerce checkout flow" -/task status +/sc:task create "migrate from REST to GraphQL" --priority high +/sc:task breakdown "e-commerce checkout flow" +/sc:task status ``` **Gotchas**: @@ -465,9 +465,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Basic syntax**: ```bash -/spawn deploy-pipeline # Orchestrate deployment -/spawn --parallel migrate-data # Parallel data migration -/spawn setup-dev-environment # Complex environment setup +/sc:spawn deploy-pipeline # Orchestrate deployment +/sc:spawn --parallel migrate-data # Parallel data migration +/sc:spawn setup-dev-environment # Complex environment setup ``` **Useful flags**: @@ -477,9 +477,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Real examples**: ```bash -/spawn --parallel "test and deploy to staging" -/spawn setup-ci-cd --monitor -/spawn --sequential database-migration +/sc:spawn --parallel "test and deploy to staging" +/sc:spawn setup-ci-cd --monitor +/sc:spawn --sequential database-migration ``` **Gotchas**: @@ -500,9 +500,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Basic syntax**: ```bash -/git commit # Smart commit with auto-generated message -/git --smart-commit add . # Add and commit with smart message -/git branch feature/new-auth # Create and switch to new branch +/sc:git commit # Smart commit with auto-generated message +/sc:git --smart-commit add . # Add and commit with smart message +/sc:git branch feature/new-auth # Create and switch to new branch ``` **Useful flags**: @@ -512,9 +512,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Real examples**: ```bash -/git --smart-commit "fixed login bug" -/git branch feature/user-dashboard --branch-strategy -/git merge develop --interactive +/sc:git --smart-commit "fixed login bug" +/sc:git branch feature/user-dashboard --branch-strategy +/sc:git merge develop --interactive ``` **Gotchas**: @@ -534,9 +534,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Basic syntax**: ```bash -/index # List all commands -/index testing # Find commands related to testing -/index --category analysis # Commands in analysis category +/sc:index # List all commands +/sc:index testing # Find commands related to testing +/sc:index --category analysis # Commands in analysis category ``` **Useful flags**: @@ -545,9 +545,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Real examples**: ```bash -/index --search "performance" -/index --category quality -/index git +/sc:index --search "performance" +/sc:index --category quality +/sc:index git ``` **Gotchas**: @@ -567,9 +567,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Basic syntax**: ```bash -/load # Load current project context -/load src/ # Load specific directory context -/load --deep # Deep analysis of project structure +/sc:load # Load current project context +/sc:load src/ # Load specific directory context +/sc:load --deep # Deep analysis of project structure ``` **Useful flags**: @@ -579,9 +579,9 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh **Real examples**: ```bash -/load --deep --summary -/load src/components/ --focus architecture -/load . --focus dependencies +/sc:load --deep --summary +/sc:load src/components/ --focus architecture +/sc:load . --focus dependencies ``` **Gotchas**: @@ -594,55 +594,55 @@ A practical guide to all 15 SuperClaude slash commands. We'll be honest about wh ### Effective Flag Combinations ```bash # Safe improvement workflow -/improve --preview src/component.js # See what would change -/improve --safe src/component.js # Apply safe changes only +/sc:improve --preview src/component.js # See what would change +/sc:improve --safe src/component.js # Apply safe changes only # Comprehensive analysis -/analyze --focus security --depth deep -/test --coverage -/document --type api +/sc:analyze --focus security --depth deep +/sc:test --coverage +/sc:document --type api # Smart git workflow -/git add . -/git --smart-commit --branch-strategy +/sc:git add . +/sc:git --smart-commit --branch-strategy # Project understanding workflow -/load --deep --summary -/analyze --focus architecture -/document --type guide +/sc:load --deep --summary +/sc:analyze --focus architecture +/sc:document --type guide ``` ### Common Workflows **New Project Onboarding**: ```bash -/load --deep --summary -/analyze --focus architecture -/test --coverage -/document README +/sc:load --deep --summary +/sc:analyze --focus architecture +/sc:test --coverage +/sc:document README ``` **Bug Investigation**: ```bash -/troubleshoot "specific error message" --logs -/analyze --focus security -/test --type unit affected-component +/sc:troubleshoot "specific error message" --logs +/sc:analyze --focus security +/sc:test --type unit affected-component ``` **Code Quality Improvement**: ```bash -/analyze --focus quality -/improve --preview src/ -/cleanup --safe -/test --coverage +/sc:analyze --focus quality +/sc:improve --preview src/ +/sc:cleanup --safe +/sc:test --coverage ``` **Pre-deployment Checklist**: ```bash -/test --type all --coverage -/analyze --focus security -/build --type prod --optimize -/git --smart-commit +/sc:test --type all --coverage +/sc:analyze --focus security +/sc:build --type prod --optimize +/sc:git --smart-commit ``` ### Troubleshooting Command Issues diff --git a/Docs/flags-guide.md b/Docs/flags-guide.md index 251df6f..8bb95b9 100644 --- a/Docs/flags-guide.md +++ b/Docs/flags-guide.md @@ -23,10 +23,10 @@ ```bash # These work great with zero flag knowledge: -/analyze src/ # Auto-picks the right analysis flags -/build # Auto-optimizes based on your project -/improve messy-code.js # Auto-activates quality and safety flags -/troubleshoot "weird error" # Auto-activates debugging and analysis flags +/sc:analyze src/ # Auto-picks the right analysis flags +/sc:build # Auto-optimizes based on your project +/sc:improve messy-code.js # Auto-activates quality and safety flags +/sc:troubleshoot "weird error" # Auto-activates debugging and analysis flags ``` **See? No flags needed.** Everything below is for when you get curious about what's happening behind the scenes. @@ -41,9 +41,9 @@ A practical guide to SuperClaude's flag system. Flags are like command-line opti **Basic syntax** (but you usually don't need to know this): ```bash -/command --flag-name -/command --flag-name value -/analyze src/ --focus security --depth deep +/sc:command --flag-name +/sc:command --flag-name value +/sc:analyze src/ --focus security --depth deep ``` **How flags actually work in practice**: @@ -234,38 +234,38 @@ Direct SuperClaude's attention to specific areas. ### Quick Analysis ```bash -/analyze src/ --focus quality # Quick quality check -/analyze --uc --focus security # Fast security scan +/sc:analyze src/ --focus quality # Quick quality check +/sc:analyze --uc --focus security # Fast security scan ``` ### Deep Investigation ```bash -/troubleshoot "bug" --think --seq # Systematic debugging -/analyze --think-hard --focus architecture # Architectural analysis +/sc:troubleshoot "bug" --think --seq # Systematic debugging +/sc:analyze --think-hard --focus architecture # Architectural analysis ``` ### Large Project Work ```bash -/analyze monorepo/ --delegate auto --uc # Efficient large analysis -/improve legacy/ --wave-mode auto --safe-mode # Safe systematic improvement +/sc:analyze monorepo/ --delegate auto --uc # Efficient large analysis +/sc:improve legacy/ --wave-mode auto --safe-mode # Safe systematic improvement ``` ### Learning & Documentation ```bash -/explain React hooks --c7 --verbose # Detailed explanation with docs -/document api/ --persona-scribe # Professional documentation +/sc:explain React hooks --c7 --verbose # Detailed explanation with docs +/sc:document api/ --persona-scribe # Professional documentation ``` ### Performance-Focused ```bash -/analyze --focus performance --play # Performance analysis with testing -/build --uc --no-mcp # Fast build without extra features +/sc:analyze --focus performance --play # Performance analysis with testing +/sc:build --uc --no-mcp # Fast build without extra features ``` ### Security-Focused ```bash -/analyze --focus security --think --validate # Thorough security analysis -/scan --persona-security --safe-mode # Conservative security scan +/sc:analyze --focus security --think --validate # Thorough security analysis +/sc:scan --persona-security --safe-mode # Conservative security scan ``` ## Practical Examples ๐Ÿ’ก @@ -273,13 +273,13 @@ Direct SuperClaude's attention to specific areas. ### Before/After: Basic Analysis **Before** (basic): ```bash -/analyze auth.js +/sc:analyze auth.js # โ†’ Simple file analysis ``` **After** (with flags): ```bash -/analyze auth.js --focus security --think --c7 +/sc:analyze auth.js --focus security --think --c7 # โ†’ Security-focused analysis with deep thinking and official docs # โ†’ Much more thorough, finds security patterns, checks against best practices ``` @@ -287,13 +287,13 @@ Direct SuperClaude's attention to specific areas. ### Before/After: Large Project **Before** (slow): ```bash -/analyze huge-monorepo/ +/sc:analyze huge-monorepo/ # โ†’ Tries to analyze everything at once, may timeout or use too many tokens ``` **After** (efficient): ```bash -/analyze huge-monorepo/ --delegate auto --uc --focus architecture +/sc:analyze huge-monorepo/ --delegate auto --uc --focus architecture # โ†’ Delegates work to sub-agents, compresses output, focuses on architecture # โ†’ Faster, more focused, better results ``` @@ -301,13 +301,13 @@ Direct SuperClaude's attention to specific areas. ### Before/After: Improvement Work **Before** (risky): ```bash -/improve legacy-system/ +/sc:improve legacy-system/ # โ†’ May make too many changes, could break things ``` **After** (safe): ```bash -/improve legacy-system/ --safe-mode --loop --validate --preview +/sc:improve legacy-system/ --safe-mode --loop --validate --preview # โ†’ Safe changes only, iterative approach, validates first, shows preview # โ†’ Much safer, progressive improvement ``` @@ -318,22 +318,22 @@ SuperClaude automatically adds flags based on context. Here's when: ### Complexity-Based ```bash -/analyze huge-codebase/ +/sc:analyze huge-codebase/ # Auto-adds: --delegate auto --uc # Why: >50 files detected, context management needed -/troubleshoot "complex system issue" +/sc:troubleshoot "complex system issue" # Auto-adds: --think --seq # Why: Multi-component problem detected ``` ### Domain-Based ```bash -/build react-app/ +/sc:build react-app/ # Auto-adds: --c7 --persona-frontend # Why: Frontend framework detected -/analyze --focus security +/sc:analyze --focus security # Auto-adds: --persona-security --validate # Why: Security focus triggers security specialist ``` @@ -341,12 +341,12 @@ SuperClaude automatically adds flags based on context. Here's when: ### Performance-Based ```bash # When context usage >75% -/analyze large-project/ +/sc:analyze large-project/ # Auto-adds: --uc # Why: Token optimization needed # When risk score >0.7 -/improve production-code/ +/sc:improve production-code/ # Auto-adds: --safe-mode --validate # Why: High-risk operation detected ``` @@ -357,19 +357,19 @@ SuperClaude automatically adds flags based on context. Here's when: **Comprehensive Code Review**: ```bash -/review codebase/ --persona-qa --think-hard --focus quality --validate --c7 +/sc:review codebase/ --persona-qa --think-hard --focus quality --validate --c7 # โ†’ QA specialist + deep thinking + quality focus + validation + docs ``` **Legacy System Modernization**: ```bash -/improve legacy/ --wave-mode force --persona-architect --safe-mode --loop --c7 +/sc:improve legacy/ --wave-mode force --persona-architect --safe-mode --loop --c7 # โ†’ Wave orchestration + architect perspective + safety + iteration + docs ``` **Security Audit**: ```bash -/scan --persona-security --ultrathink --focus security --validate --seq +/sc:scan --persona-security --ultrathink --focus security --validate --seq # โ†’ Security specialist + maximum thinking + security focus + validation + systematic analysis ``` @@ -377,13 +377,13 @@ SuperClaude automatically adds flags based on context. Here's when: **For Speed**: ```bash -/analyze --no-mcp --uc --scope file +/sc:analyze --no-mcp --uc --scope file # โ†’ Disable extra features, compress output, limit scope ``` **For Thoroughness**: ```bash -/analyze --all-mcp --think-hard --delegate auto +/sc:analyze --all-mcp --think-hard --delegate auto # โ†’ All capabilities, deep thinking, parallel processing ``` @@ -391,17 +391,17 @@ SuperClaude automatically adds flags based on context. Here's when: **Bug Investigation Workflow**: ```bash -/troubleshoot "specific error" --seq --think --validate -/analyze affected-files/ --focus quality --persona-analyzer -/test --play --coverage +/sc:troubleshoot "specific error" --seq --think --validate +/sc:analyze affected-files/ --focus quality --persona-analyzer +/sc:test --play --coverage ``` **Feature Development Workflow**: ```bash -/design new-feature --persona-architect --c7 -/build --magic --persona-frontend --validate -/test --play --coverage -/document --persona-scribe --c7 +/sc:design new-feature --persona-architect --c7 +/sc:build --magic --persona-frontend --validate +/sc:test --play --coverage +/sc:document --persona-scribe --c7 ``` ## Quick Reference ๐Ÿ“‹ diff --git a/Docs/installation-guide.md b/Docs/installation-guide.md index 6ac7267..f68505e 100644 --- a/Docs/installation-guide.md +++ b/Docs/installation-guide.md @@ -257,10 +257,10 @@ Try these commands to get started: ```bash # In Claude Code, try these: -/help # See available commands -/analyze README.md # Analyze a file -/build --help # See build options -/improve --help # See improvement options +/sc:help # See available commands +/sc:analyze README.md # Analyze a file +/sc:build --help # See build options +/sc:improve --help # See improvement options ``` **Don't worry if it seems overwhelming** - SuperClaude enhances Claude Code gradually. You can use as much or as little as you want. diff --git a/Docs/personas-guide.md b/Docs/personas-guide.md index 1acf952..383a765 100644 --- a/Docs/personas-guide.md +++ b/Docs/personas-guide.md @@ -20,10 +20,10 @@ ```bash # These automatically activate the right experts: -/analyze payment-system/ # โ†’ Security + backend experts auto-activate -/build react-app/ # โ†’ Frontend specialist takes over -/improve slow-queries.sql # โ†’ Performance optimizer jumps in -/troubleshoot "auth failing" # โ†’ Debug specialist + security expert coordinate +/sc:analyze payment-system/ # โ†’ Security + backend experts auto-activate +/sc:build react-app/ # โ†’ Frontend specialist takes over +/sc:improve slow-queries.sql # โ†’ Performance optimizer jumps in +/sc:troubleshoot "auth failing" # โ†’ Debug specialist + security expert coordinate ``` **See the pattern?** You focus on what you want to do, SuperClaude figures out who should help. Everything below is for when you get curious about who's on the team. @@ -74,9 +74,9 @@ Think of SuperClaude personas as having a team of specialists on demand. Each pe **Example workflows**: ```bash -/design microservices-migration --persona-architect -/analyze --focus architecture large-system/ -/estimate "redesign auth system" --persona-architect +/sc:design microservices-migration --persona-architect +/sc:analyze --focus architecture large-system/ +/sc:estimate "redesign auth system" --persona-architect ``` **What they prioritize**: @@ -111,9 +111,9 @@ Think of SuperClaude personas as having a team of specialists on demand. Each pe **Example workflows**: ```bash -/build dashboard --persona-frontend -/improve --focus accessibility components/ -/analyze --persona-frontend --focus performance +/sc:build dashboard --persona-frontend +/sc:improve --focus accessibility components/ +/sc:analyze --persona-frontend --focus performance ``` **What they prioritize**: @@ -149,9 +149,9 @@ Think of SuperClaude personas as having a team of specialists on demand. Each pe **Example workflows**: ```bash -/design user-api --persona-backend -/analyze --focus security api/ -/improve --persona-backend database-layer/ +/sc:design user-api --persona-backend +/sc:analyze --focus security api/ +/sc:improve --persona-backend database-layer/ ``` **What they prioritize**: @@ -187,9 +187,9 @@ Think of SuperClaude personas as having a team of specialists on demand. Each pe **Example workflows**: ```bash -/scan --persona-security --focus security -/analyze auth-system/ --persona-security -/improve --focus security --persona-security +/sc:scan --persona-security --focus security +/sc:analyze auth-system/ --persona-security +/sc:improve --focus security --persona-security ``` **What they prioritize**: @@ -225,9 +225,9 @@ Think of SuperClaude personas as having a team of specialists on demand. Each pe **Example workflows**: ```bash -/analyze --focus performance --persona-performance -/improve --type performance slow-endpoints/ -/test --benchmark --persona-performance +/sc:analyze --focus performance --persona-performance +/sc:improve --type performance slow-endpoints/ +/sc:test --benchmark --persona-performance ``` **What they prioritize**: @@ -263,9 +263,9 @@ Think of SuperClaude personas as having a team of specialists on demand. Each pe **Example workflows**: ```bash -/troubleshoot "auth randomly fails" --persona-analyzer -/analyze --persona-analyzer mysterious-bug/ -/explain --detailed "why is this slow" --persona-analyzer +/sc:troubleshoot "auth randomly fails" --persona-analyzer +/sc:analyze --persona-analyzer mysterious-bug/ +/sc:explain --detailed "why is this slow" --persona-analyzer ``` **What they prioritize**: @@ -301,9 +301,9 @@ Think of SuperClaude personas as having a team of specialists on demand. Each pe **Example workflows**: ```bash -/test --persona-qa comprehensive-suite -/analyze --focus quality --persona-qa -/review --persona-qa critical-features/ +/sc:test --persona-qa comprehensive-suite +/sc:analyze --focus quality --persona-qa +/sc:review --persona-qa critical-features/ ``` **What they prioritize**: @@ -339,9 +339,9 @@ Think of SuperClaude personas as having a team of specialists on demand. Each pe **Example workflows**: ```bash -/improve --type quality --persona-refactorer -/cleanup legacy-module/ --persona-refactorer -/analyze --focus maintainability --persona-refactorer +/sc:improve --type quality --persona-refactorer +/sc:cleanup legacy-module/ --persona-refactorer +/sc:analyze --focus maintainability --persona-refactorer ``` **What they prioritize**: @@ -377,9 +377,9 @@ Think of SuperClaude personas as having a team of specialists on demand. Each pe **Example workflows**: ```bash -/deploy production --persona-devops -/analyze infrastructure/ --persona-devops -/improve deployment-pipeline --persona-devops +/sc:deploy production --persona-devops +/sc:analyze infrastructure/ --persona-devops +/sc:improve deployment-pipeline --persona-devops ``` **What they prioritize**: @@ -415,9 +415,9 @@ Think of SuperClaude personas as having a team of specialists on demand. Each pe **Example workflows**: ```bash -/explain React hooks --persona-mentor -/document --type guide --persona-mentor -/analyze complex-algorithm.js --persona-mentor +/sc:explain React hooks --persona-mentor +/sc:document --type guide --persona-mentor +/sc:analyze complex-algorithm.js --persona-mentor ``` **What they prioritize**: @@ -451,9 +451,9 @@ Think of SuperClaude personas as having a team of specialists on demand. Each pe **Example workflows**: ```bash -/document api/ --persona-scribe -/git commit --persona-scribe -/explain --persona-scribe=es complex-feature +/sc:document api/ --persona-scribe +/sc:git commit --persona-scribe +/sc:explain --persona-scribe=es complex-feature ``` **What they prioritize**: @@ -510,31 +510,31 @@ Personas often work together automatically. Here are common collaboration patter ### Design & Implementation ```bash -/design user-dashboard +/sc:design user-dashboard # Auto-activates: ๐Ÿ—๏ธ architect (system design) + ๐ŸŽจ frontend (UI design) ``` ### Security Review ```bash -/analyze --focus security api/ +/sc:analyze --focus security api/ # Auto-activates: ๐Ÿ›ก๏ธ security (primary) + โš™๏ธ backend (API expertise) ``` ### Performance Optimization ```bash -/improve --focus performance slow-app/ +/sc:improve --focus performance slow-app/ # Auto-activates: โšก performance (primary) + ๐ŸŽจ frontend (if UI) or โš™๏ธ backend (if API) ``` ### Quality Improvement ```bash -/improve --focus quality legacy-code/ +/sc:improve --focus quality legacy-code/ # Auto-activates: ๐Ÿ”„ refactorer (primary) + ๐Ÿงช qa (testing) + ๐Ÿ—๏ธ architect (design) ``` ### Documentation & Learning ```bash -/document complex-feature --type guide +/sc:document complex-feature --type guide # Auto-activates: โœ๏ธ scribe (writing) + ๐Ÿ‘จโ€๐Ÿซ mentor (educational approach) ``` @@ -544,13 +544,13 @@ Personas often work together automatically. Here are common collaboration patter **Before** (generic): ```bash -/analyze auth.js +/sc:analyze auth.js # โ†’ Basic analysis, generic advice ``` **After** (security persona): ```bash -/analyze auth.js --persona-security +/sc:analyze auth.js --persona-security # โ†’ Security-focused analysis # โ†’ Threat modeling perspective # โ†’ OWASP compliance checking @@ -561,7 +561,7 @@ Personas often work together automatically. Here are common collaboration patter **Frontend work detection**: ```bash -/build react-components/ +/sc:build react-components/ # Auto-activates: ๐ŸŽจ frontend # โ†’ UI-focused build optimization # โ†’ Accessibility checking @@ -571,7 +571,7 @@ Personas often work together automatically. Here are common collaboration patter **Complex debugging**: ```bash -/troubleshoot "payment processing randomly fails" +/sc:troubleshoot "payment processing randomly fails" # Auto-activates: ๐Ÿ” analyzer # โ†’ Systematic investigation approach # โ†’ Evidence collection methodology @@ -583,7 +583,7 @@ Personas often work together automatically. Here are common collaboration patter **Force security perspective**: ```bash -/analyze react-app/ --persona-security +/sc:analyze react-app/ --persona-security # Even though it's frontend code, analyze from security perspective # โ†’ XSS vulnerability checking # โ†’ Authentication flow analysis @@ -592,7 +592,7 @@ Personas often work together automatically. Here are common collaboration patter **Get architectural advice on small changes**: ```bash -/improve small-utility.js --persona-architect +/sc:improve small-utility.js --persona-architect # Apply architectural thinking to small code # โ†’ Design pattern opportunities # โ†’ Future extensibility @@ -611,30 +611,30 @@ Personas often work together automatically. Here are common collaboration patter **How to override**: ```bash # Explicit persona selection -/analyze frontend-code/ --persona-security # Security view of frontend -/improve backend-api/ --persona-performance # Performance view of backend +/sc:analyze frontend-code/ --persona-security # Security view of frontend +/sc:improve backend-api/ --persona-performance # Performance view of backend # Multiple persona flags (last one wins) -/analyze --persona-frontend --persona-security # Uses security persona +/sc:analyze --persona-frontend --persona-security # Uses security persona ``` ### Persona-Specific Flags and Settings **Security persona + validation**: ```bash -/analyze --persona-security --focus security --validate +/sc:analyze --persona-security --focus security --validate # โ†’ Maximum security focus with validation ``` **Performance persona + benchmarking**: ```bash -/test --persona-performance --benchmark --focus performance +/sc:test --persona-performance --benchmark --focus performance # โ†’ Performance-focused testing with metrics ``` **Mentor persona + detailed explanations**: ```bash -/explain complex-concept --persona-mentor --verbose +/sc:explain complex-concept --persona-mentor --verbose # โ†’ Educational explanation with full detail ``` @@ -643,12 +643,12 @@ Personas often work together automatically. Here are common collaboration patter **When you need multiple perspectives**: ```bash # Sequential analysis with different personas -/analyze --persona-security api/auth.js -/analyze --persona-performance api/auth.js -/analyze --persona-refactorer api/auth.js +/sc:analyze --persona-security api/auth.js +/sc:analyze --persona-performance api/auth.js +/sc:analyze --persona-refactorer api/auth.js # Or let SuperClaude coordinate automatically -/analyze --focus quality api/auth.js +/sc:analyze --focus quality api/auth.js # Auto-coordinates: security + performance + refactorer insights ``` @@ -657,56 +657,56 @@ Personas often work together automatically. Here are common collaboration patter ### ๐Ÿ—๏ธ Architect Workflows ```bash # System design -/design microservices-architecture --persona-architect -/estimate "migrate monolith to microservices" --persona-architect +/sc:design microservices-architecture --persona-architect +/sc:estimate "migrate monolith to microservices" --persona-architect # Architecture review -/analyze --focus architecture --persona-architect large-system/ -/review --persona-architect critical-components/ +/sc:analyze --focus architecture --persona-architect large-system/ +/sc:review --persona-architect critical-components/ ``` ### ๐ŸŽจ Frontend Workflows ```bash # Component development -/build dashboard-components/ --persona-frontend -/improve --focus accessibility --persona-frontend ui/ +/sc:build dashboard-components/ --persona-frontend +/sc:improve --focus accessibility --persona-frontend ui/ # Performance optimization -/analyze --focus performance --persona-frontend bundle/ -/test --persona-frontend --focus performance +/sc:analyze --focus performance --persona-frontend bundle/ +/sc:test --persona-frontend --focus performance ``` ### โš™๏ธ Backend Workflows ```bash # API development -/design rest-api --persona-backend -/build api-endpoints/ --persona-backend +/sc:design rest-api --persona-backend +/sc:build api-endpoints/ --persona-backend # Reliability improvements -/improve --focus reliability --persona-backend services/ -/analyze --persona-backend --focus security api/ +/sc:improve --focus reliability --persona-backend services/ +/sc:analyze --persona-backend --focus security api/ ``` ### ๐Ÿ›ก๏ธ Security Workflows ```bash # Security assessment -/scan --persona-security --focus security entire-app/ -/analyze --persona-security auth-flow/ +/sc:scan --persona-security --focus security entire-app/ +/sc:analyze --persona-security auth-flow/ # Vulnerability fixing -/improve --focus security --persona-security vulnerable-code/ -/review --persona-security --focus security critical-paths/ +/sc:improve --focus security --persona-security vulnerable-code/ +/sc:review --persona-security --focus security critical-paths/ ``` ### ๐Ÿ” Analyzer Workflows ```bash # Bug investigation -/troubleshoot "intermittent failures" --persona-analyzer -/analyze --persona-analyzer --focus debugging problem-area/ +/sc:troubleshoot "intermittent failures" --persona-analyzer +/sc:analyze --persona-analyzer --focus debugging problem-area/ # System understanding -/explain --persona-analyzer complex-system/ -/load --persona-analyzer unfamiliar-codebase/ +/sc:explain --persona-analyzer complex-system/ +/sc:load --persona-analyzer unfamiliar-codebase/ ``` ## Quick Reference ๐Ÿ“‹ @@ -808,14 +808,14 @@ Personas often work together automatically. Here are common collaboration patter **How to override effectively**: ```bash # Force specific perspective -/analyze frontend-code/ --persona-security # Security view of frontend +/sc:analyze frontend-code/ --persona-security # Security view of frontend # Combine multiple perspectives -/analyze api/ --persona-security -/analyze api/ --persona-performance # Run separately for different views +/sc:analyze api/ --persona-security +/sc:analyze api/ --persona-performance # Run separately for different views # Use general analysis -/analyze --no-persona # Disable persona auto-activation +/sc:analyze --no-persona # Disable persona auto-activation ``` ## Tips for Effective Persona Usage ๐Ÿ’ก diff --git a/Docs/superclaude-user-guide.md b/Docs/superclaude-user-guide.md index 06158c1..c50e050 100644 --- a/Docs/superclaude-user-guide.md +++ b/Docs/superclaude-user-guide.md @@ -46,10 +46,10 @@ A comprehensive guide to understanding and using SuperClaude v3.0 effectively. B ```bash # Try these commands in Claude Code: -/help # See what's available -/analyze README.md # SuperClaude analyzes your project -/build # Smart build with auto-optimization -/improve messy-file.js # Clean up code automatically +/sc:help # See what's available +/sc:analyze README.md # SuperClaude analyzes your project +/sc:build # Smart build with auto-optimization +/sc:improve messy-file.js # Clean up code automatically ``` **What just happened?** SuperClaude automatically: @@ -290,7 +290,7 @@ The magic happens when components coordinate: **Example: Security Analysis Request** ```bash -/analyze auth-system/ --focus security +/sc:analyze auth-system/ --focus security ``` **What happens automatically:** @@ -328,7 +328,7 @@ SuperClaude operates in three distinct modes that optimize different aspects of ```bash # SuperClaude automatically creates and manages session tasks -/build large-project/ +/sc:build large-project/ # โ†’ Creates: "Analyze project structure", "Run build process", "Validate output" ``` @@ -339,9 +339,9 @@ SuperClaude operates in three distinct modes that optimize different aspects of - **Usage**: Long-term feature development ```bash -/task create "implement user dashboard" --priority high -/task breakdown "payment integration" -/task status # Check current project tasks +/sc:task create "implement user dashboard" --priority high +/sc:task breakdown "payment integration" +/sc:task status # Check current project tasks ``` **Layer 3: Complex Orchestration (/spawn command)** @@ -350,8 +350,8 @@ SuperClaude operates in three distinct modes that optimize different aspects of - **Usage**: Operations involving multiple tools/systems ```bash -/spawn deploy-pipeline --parallel -/spawn setup-dev-environment --monitor +/sc:spawn deploy-pipeline --parallel +/sc:spawn setup-dev-environment --monitor ``` **Layer 4: Iterative Enhancement (/loop command)** @@ -360,7 +360,7 @@ SuperClaude operates in three distinct modes that optimize different aspects of - **Usage**: Quality improvement and refinement ```bash -/improve messy-code.js --loop --iterations 3 +/sc:improve messy-code.js --loop --iterations 3 # โ†’ Iteratively improves code with validation between cycles ``` @@ -432,8 +432,8 @@ When introspection mode is active, you'll see these markers: **Manual activation**: ```bash -/analyze complex-system/ --introspect -/troubleshoot "framework confusion" --introspection +/sc:analyze complex-system/ --introspect +/sc:troubleshoot "framework confusion" --introspection ``` ### Token Efficiency Mode โšก @@ -485,8 +485,8 @@ When introspection mode is active, you'll see these markers: **Manual activation**: ```bash -/analyze huge-codebase/ --uc # Ultra-compressed mode -/improve legacy-system/ --uc --delegate auto # Efficient large operations +/sc:analyze huge-codebase/ --uc # Ultra-compressed mode +/sc:improve legacy-system/ --uc --delegate auto # Efficient large operations ``` **Performance Metrics**: @@ -500,7 +500,7 @@ When introspection mode is active, you'll see these markers: The three modes often work together: ```bash -/improve large-legacy-system/ --wave-mode auto --uc --introspect +/sc:improve large-legacy-system/ --wave-mode auto --uc --introspect ``` **What happens**: @@ -550,20 +550,20 @@ The detection engine analyzes every request through multiple lenses: **High-Confidence Triggers** (90%+ activation): ```bash -/analyze auth-system/ --focus security +/sc:analyze auth-system/ --focus security # โ†’ ๐Ÿ›ก๏ธ security persona + Sequential MCP + --validate flag ``` **Context-Based Activation**: ```bash -/build react-components/ +/sc:build react-components/ # โ†’ ๐ŸŽจ frontend persona + Magic MCP + --c7 flag (React docs) ``` **Performance-Based Activation**: ```bash # When context usage >75% -/analyze large-project/ +/sc:analyze large-project/ # โ†’ Auto-adds --uc flag for compression ``` @@ -585,7 +585,7 @@ The routing system uses dynamic decision trees to map detected patterns to optim **Multi-Server Operations**: ```bash -/design user-dashboard --type api +/sc:design user-dashboard --type api ``` **Orchestrator coordinates**: - ๐Ÿ—๏ธ architect persona (system design) @@ -648,14 +648,14 @@ The orchestrator optimizes for sub-100ms performance targets through several str **Sub-Agent Delegation**: ```bash # Auto-activates when >7 directories or >50 files detected -/analyze monorepo/ +/sc:analyze monorepo/ # โ†’ --delegate auto flag + parallel processing ``` **Wave Orchestration**: ```bash # Auto-activates when complexity >0.7 + files >20 + operation types >2 -/improve legacy-system/ +/sc:improve legacy-system/ # โ†’ --wave-mode auto + multi-stage execution ``` @@ -663,7 +663,7 @@ The orchestrator optimizes for sub-100ms performance targets through several str #### Example 1: Security Analysis Request ```bash -/scan user-auth/ --focus security +/sc:scan user-auth/ --focus security ``` **Orchestrator Analysis**: @@ -681,7 +681,7 @@ The orchestrator optimizes for sub-100ms performance targets through several str #### Example 2: Frontend Performance Optimization ```bash -/improve slow-dashboard/ --focus performance +/sc:improve slow-dashboard/ --focus performance ``` **Orchestrator Analysis**: @@ -699,7 +699,7 @@ The orchestrator optimizes for sub-100ms performance targets through several str #### Example 3: Large Codebase Analysis ```bash -/analyze enterprise-monorepo/ +/sc:analyze enterprise-monorepo/ ``` **Orchestrator Analysis**: @@ -785,7 +785,7 @@ These principles guide how SuperClaude approaches development problems: **In practice**: ```bash -/improve slow-api/ --focus performance +/sc:improve slow-api/ --focus performance # โ†’ Measures current performance, identifies bottlenecks, optimizes based on data ``` @@ -818,7 +818,7 @@ SuperClaude approaches problems like an experienced developer: Because SuperClaude follows consistent rules, you can predict how it will approach problems: ```bash -/improve legacy-authentication/ +/sc:improve legacy-authentication/ ``` **You can expect**: - Reading existing code before suggesting changes @@ -839,7 +839,7 @@ The principles ensure high-quality outcomes: You always understand what SuperClaude is doing and why: ```bash -/analyze --introspect complex-system/ +/sc:analyze --introspect complex-system/ ``` **Shows you**: - Decision-making process @@ -950,9 +950,9 @@ If you haven't installed SuperClaude yet, see the [Installation Guide](installat #### Quick Verification ```bash # Test basic functionality -/help # Should show SuperClaude commands -/analyze README.md # Try analyzing a simple file -/build --help # Check command options +/sc:help # Should show SuperClaude commands +/sc:analyze README.md # Try analyzing a simple file +/sc:build --help # Check command options ``` #### Understanding Auto-Activation @@ -960,13 +960,13 @@ Try these commands to see how SuperClaude automatically chooses the right tools: ```bash # Frontend work โ†’ frontend persona + Magic MCP -/build src/components/ +/sc:build src/components/ # Security analysis โ†’ security persona + Sequential MCP -/scan auth/ --focus security +/sc:scan auth/ --focus security # Performance investigation โ†’ performance persona + Playwright MCP -/analyze --focus performance slow-endpoints/ +/sc:analyze --focus performance slow-endpoints/ ``` Watch for auto-activated flags and personas in the output. This shows SuperClaude's intelligent routing in action. @@ -978,19 +978,19 @@ When starting work on an unfamiliar project: ```bash # 1. Load project context -/load --deep --summary +/sc:load --deep --summary # โ†’ Gives overview of structure, dependencies, patterns # 2. Analyze architecture -/analyze --focus architecture +/sc:analyze --focus architecture # โ†’ ๐Ÿ—๏ธ architect persona provides system understanding # 3. Check code quality -/scan --focus quality +/sc:scan --focus quality # โ†’ ๐Ÿงช qa persona identifies potential issues # 4. Review documentation -/document README --type guide +/sc:document README --type guide # โ†’ โœ๏ธ scribe persona improves project documentation ``` @@ -999,19 +999,19 @@ For developing new features: ```bash # 1. Design phase -/design user-dashboard --type component +/sc:design user-dashboard --type component # โ†’ ๐Ÿ—๏ธ architect + ๐ŸŽจ frontend personas coordinate # 2. Implementation -/build dashboard-components/ +/sc:build dashboard-components/ # โ†’ ๐ŸŽจ frontend persona + Magic MCP for UI generation # 3. Testing -/test --type e2e dashboard/ +/sc:test --type e2e dashboard/ # โ†’ ๐Ÿงช qa persona + Playwright MCP for testing # 4. Documentation -/document dashboard/ --type api +/sc:document dashboard/ --type api # โ†’ โœ๏ธ scribe persona creates comprehensive docs ``` @@ -1020,19 +1020,19 @@ For systematic debugging: ```bash # 1. Problem investigation -/troubleshoot "login randomly fails" --think +/sc:troubleshoot "login randomly fails" --think # โ†’ ๐Ÿ” analyzer persona + Sequential MCP for methodology # 2. Root cause analysis -/analyze auth-flow/ --focus debugging +/sc:analyze auth-flow/ --focus debugging # โ†’ Systematic investigation with evidence collection # 3. Fix implementation -/improve auth/ --safe-mode --validate +/sc:improve auth/ --safe-mode --validate # โ†’ Safe improvements with validation # 4. Verification testing -/test auth-flow/ --coverage +/sc:test auth-flow/ --coverage # โ†’ Comprehensive testing to ensure fix works ``` @@ -1041,19 +1041,19 @@ For improving existing code: ```bash # 1. Quality assessment -/analyze legacy-code/ --focus quality +/sc:analyze legacy-code/ --focus quality # โ†’ ๐Ÿ”„ refactorer persona identifies improvement opportunities # 2. Safe improvements -/improve --preview legacy-code/ +/sc:improve --preview legacy-code/ # โ†’ See what would change before applying # 3. Apply improvements -/improve --safe legacy-code/ +/sc:improve --safe legacy-code/ # โ†’ Apply only low-risk improvements # 4. Validate changes -/test --coverage improved-code/ +/sc:test --coverage improved-code/ # โ†’ Ensure improvements don't break functionality ``` @@ -1062,28 +1062,28 @@ For improving existing code: #### Security-First Development ```bash # Development with security focus -/scan --persona-security --focus security -/build --validate --safe-mode -/test --type security -/deploy --persona-security --validate +/sc:scan --persona-security --focus security +/sc:build --validate --safe-mode +/sc:test --type security +/sc:deploy --persona-security --validate ``` #### Performance-Optimized Workflow ```bash # Performance-focused development -/analyze --focus performance --persona-performance -/improve --type performance --benchmark -/test --focus performance --play -/deploy --monitor-performance +/sc:analyze --focus performance --persona-performance +/sc:improve --type performance --benchmark +/sc:test --focus performance --play +/sc:deploy --monitor-performance ``` #### Team Collaboration Workflow ```bash # Collaborative development patterns -/review team-code/ --persona-qa --focus quality -/document features/ --persona-scribe --type guide -/git --smart-commit --branch-strategy -/task status # Check team progress +/sc:review team-code/ --persona-qa --focus quality +/sc:document features/ --persona-scribe --type guide +/sc:git --smart-commit --branch-strategy +/sc:task status # Check team progress ``` ### Advanced Workflow Patterns ๐Ÿš€ @@ -1093,15 +1093,15 @@ For working with enterprise-scale projects: ```bash # Efficient large-scale analysis -/analyze monorepo/ --delegate auto --uc --focus architecture +/sc:analyze monorepo/ --delegate auto --uc --focus architecture # โ†’ Parallel processing + compression + architectural focus # Systematic improvements -/improve legacy-system/ --wave-mode auto --safe-mode +/sc:improve legacy-system/ --wave-mode auto --safe-mode # โ†’ Multi-stage improvements with safety checks # Comprehensive quality review -/scan enterprise-app/ --delegate folders --focus quality +/sc:scan enterprise-app/ --delegate folders --focus quality # โ†’ Distributed quality analysis ``` @@ -1110,19 +1110,19 @@ For updating old codebases: ```bash # Assessment phase -/analyze legacy/ --persona-architect --ultrathink +/sc:analyze legacy/ --persona-architect --ultrathink # โ†’ Deep architectural analysis # Planning phase -/design modernization-strategy --type architecture +/sc:design modernization-strategy --type architecture # โ†’ Comprehensive modernization plan # Implementation phase -/improve legacy/ --wave-mode systematic --safe-mode --loop +/sc:improve legacy/ --wave-mode systematic --safe-mode --loop # โ†’ Iterative, safe improvements with validation # Migration support -/migrate --type framework legacy-to-modern/ +/sc:migrate --type framework legacy-to-modern/ # โ†’ Framework migration assistance ``` @@ -1131,16 +1131,16 @@ For projects spanning multiple technical domains: ```bash # Coordinate across domains -/analyze fullstack-app/ --all-mcp --delegate auto +/sc:analyze fullstack-app/ --all-mcp --delegate auto # โ†’ All MCP servers + parallel processing # Domain-specific improvements -/improve frontend/ --persona-frontend --magic -/improve backend/ --persona-backend --c7 -/improve infrastructure/ --persona-devops --seq +/sc:improve frontend/ --persona-frontend --magic +/sc:improve backend/ --persona-backend --c7 +/sc:improve infrastructure/ --persona-devops --seq # Integration validation -/test --type integration --play +/sc:test --type integration --play # โ†’ Comprehensive integration testing ``` @@ -1149,36 +1149,36 @@ For projects spanning multiple technical domains: #### Start Small, Scale Up ```bash # Begin with focused scope -/analyze single-component.js --focus quality +/sc:analyze single-component.js --focus quality # Expand as needed -/analyze entire-module/ --focus quality --delegate files +/sc:analyze entire-module/ --focus quality --delegate files # Scale to full system -/analyze whole-project/ --delegate auto --uc +/sc:analyze whole-project/ --delegate auto --uc ``` #### Use Progressive Enhancement ```bash # Basic command -/build project/ +/sc:build project/ # Add intelligence -/build project/ --think --c7 +/sc:build project/ --think --c7 # Full orchestration -/build project/ --wave-mode auto --all-mcp --delegate auto +/sc:build project/ --wave-mode auto --all-mcp --delegate auto ``` #### Combine Complementary Personas ```bash # Security + Performance analysis -/analyze api/ --persona-security -/analyze api/ --persona-performance +/sc:analyze api/ --persona-security +/sc:analyze api/ --persona-performance # Architecture + Quality review -/review system/ --persona-architect --focus architecture -/review system/ --persona-qa --focus quality +/sc:review system/ --persona-architect --focus architecture +/sc:review system/ --persona-qa --focus quality ``` ### Troubleshooting Workflows ๐Ÿšจ @@ -1186,39 +1186,39 @@ For projects spanning multiple technical domains: #### When Commands Don't Work as Expected ```bash # Debug with introspection -/troubleshoot "command issues" --introspect +/sc:troubleshoot "command issues" --introspect # โ†’ Meta-cognitive analysis of what went wrong # Try different approaches -/analyze problem/ --persona-analyzer --seq +/sc:analyze problem/ --persona-analyzer --seq # โ†’ Systematic investigation methodology # Check framework status -/load framework-status/ --summary +/sc:load framework-status/ --summary # โ†’ Understand current SuperClaude state ``` #### When Performance is Slow ```bash # Optimize for speed -/analyze large-project/ --no-mcp --uc --scope module +/sc:analyze large-project/ --no-mcp --uc --scope module # โ†’ Disable extra features, compress output, limit scope # Use delegation for large tasks -/improve huge-codebase/ --delegate auto --concurrency 5 +/sc:improve huge-codebase/ --delegate auto --concurrency 5 # โ†’ Parallel processing with controlled concurrency ``` #### When Results Aren't Focused Enough ```bash # Use specific focus flags -/analyze code/ --focus security --scope file +/sc:analyze code/ --focus security --scope file # Activate appropriate personas manually -/analyze frontend-code/ --persona-security # Security view of frontend +/sc:analyze frontend-code/ --persona-security # Security view of frontend # Combine multiple approaches -/analyze --focus performance --persona-performance --play +/sc:analyze --focus performance --persona-performance --play ``` ### Building Your Own Workflows ๐Ÿ› ๏ธ @@ -1242,13 +1242,13 @@ Try different combinations to find what works best: ```bash # For learning: verbose explanations with docs -/explain concept --persona-mentor --verbose --c7 +/sc:explain concept --persona-mentor --verbose --c7 # For safety: maximum validation and checking -/improve critical-code/ --safe-mode --validate --preview +/sc:improve critical-code/ --safe-mode --validate --preview # For efficiency: compressed output with parallel processing -/analyze big-project/ --uc --delegate auto --concurrency 3 +/sc:analyze big-project/ --uc --delegate auto --concurrency 3 ``` Remember: SuperClaude learns from successful patterns, so the more you use effective combinations, the better it gets at auto-activating the right approach for your needs. @@ -1265,7 +1265,7 @@ SuperClaude automatically coordinates components based on context. Here's how it #### Frontend Development Request ```bash -/build react-dashboard/ +/sc:build react-dashboard/ ``` **Automatic coordination**: @@ -1279,7 +1279,7 @@ SuperClaude automatically coordinates components based on context. Here's how it #### Security Analysis Request ```bash -/scan user-authentication/ --focus security +/sc:scan user-authentication/ --focus security ``` **Automatic coordination**: @@ -1293,7 +1293,7 @@ SuperClaude automatically coordinates components based on context. Here's how it #### Performance Investigation ```bash -/troubleshoot "API responses are slow" +/sc:troubleshoot "API responses are slow" ``` **Automatic coordination**: @@ -1313,38 +1313,38 @@ Sometimes you want to override auto-coordination for specific needs: #### Override Persona Selection ```bash # View frontend code from security perspective -/analyze react-components/ --persona-security +/sc:analyze react-components/ --persona-security # โ†’ Security analysis of UI components (XSS, data exposure, etc.) # Apply architectural thinking to small utility -/improve utility-function.js --persona-architect +/sc:improve utility-function.js --persona-architect # โ†’ Design patterns and extensibility for simple code ``` #### Control MCP Server Usage ```bash # Disable all MCP servers for speed -/analyze large-codebase/ --no-mcp +/sc:analyze large-codebase/ --no-mcp # โ†’ 40-60% faster execution, native tools only # Enable all MCP servers for comprehensive analysis -/analyze complex-system/ --all-mcp +/sc:analyze complex-system/ --all-mcp # โ†’ Maximum capabilities, higher token usage # Use specific MCP combinations -/build ui-components/ --magic --c7 --no-seq +/sc:build ui-components/ --magic --c7 --no-seq # โ†’ UI generation + docs, skip complex analysis ``` #### Combine Multiple Perspectives ```bash # Sequential analysis with different personas -/analyze payment-system/ --persona-security # Security view -/analyze payment-system/ --persona-performance # Performance view -/analyze payment-system/ --persona-architect # Architecture view +/sc:analyze payment-system/ --persona-security # Security view +/sc:analyze payment-system/ --persona-performance # Performance view +/sc:analyze payment-system/ --persona-architect # Architecture view # Or coordinate automatically -/review payment-system/ --focus quality +/sc:review payment-system/ --focus quality # โ†’ Auto-coordinates security + performance + architecture insights ``` @@ -1355,33 +1355,33 @@ Flags work together to create powerful combinations: #### Safety-First Patterns ```bash # Maximum safety for critical code -/improve production-auth/ --safe-mode --validate --preview +/sc:improve production-auth/ --safe-mode --validate --preview # โ†’ Conservative changes + risk assessment + preview before applying # Safe exploration of large changes -/improve legacy-system/ --wave-mode auto --safe-mode --validate +/sc:improve legacy-system/ --wave-mode auto --safe-mode --validate # โ†’ Multi-stage improvements + safety checks + validation gates ``` #### Performance-Optimized Patterns ```bash # Fast execution for large operations -/analyze huge-project/ --uc --no-mcp --scope module +/sc:analyze huge-project/ --uc --no-mcp --scope module # โ†’ Compressed output + native tools + limited scope # Efficient parallel processing -/improve monorepo/ --delegate auto --uc --concurrency 5 +/sc:improve monorepo/ --delegate auto --uc --concurrency 5 # โ†’ Parallel processing + compression + controlled resource usage ``` #### Learning-Focused Patterns ```bash # Educational explanations with full context -/explain complex-concept --persona-mentor --verbose --c7 +/sc:explain complex-concept --persona-mentor --verbose --c7 # โ†’ Educational approach + detailed explanations + official docs # Deep understanding with transparency -/analyze mysterious-code/ --persona-analyzer --think-hard --introspect +/sc:analyze mysterious-code/ --persona-analyzer --think-hard --introspect # โ†’ Investigation methodology + deep analysis + thinking transparency ``` @@ -1391,7 +1391,7 @@ MCP servers often work together automatically: #### Documentation + Analysis ```bash -/improve old-react-code/ +/sc:improve old-react-code/ ``` **MCP coordination**: - Context7: Gets current React best practices @@ -1401,7 +1401,7 @@ MCP servers often work together automatically: #### Testing + Performance ```bash -/test dashboard/ --focus performance +/sc:test dashboard/ --focus performance ``` **MCP coordination**: - Sequential: Plans comprehensive test strategy @@ -1411,7 +1411,7 @@ MCP servers often work together automatically: #### Complex Problem Solving ```bash -/troubleshoot "complex multi-service issue" --ultrathink +/sc:troubleshoot "complex multi-service issue" --ultrathink ``` **MCP coordination**: - Sequential: Structures systematic investigation @@ -1425,7 +1425,7 @@ Personas automatically collaborate on complex requests: #### Architecture + Security ```bash -/design payment-api --type secure +/sc:design payment-api --type secure ``` **Persona collaboration**: - ๐Ÿ—๏ธ architect: System design and scalability @@ -1435,7 +1435,7 @@ Personas automatically collaborate on complex requests: #### Frontend + Performance ```bash -/build dashboard --focus performance +/sc:build dashboard --focus performance ``` **Persona collaboration**: - ๐ŸŽจ frontend: UI/UX and accessibility @@ -1445,7 +1445,7 @@ Personas automatically collaborate on complex requests: #### Quality + Refactoring ```bash -/improve legacy-code/ --focus quality +/sc:improve legacy-code/ --focus quality ``` **Persona collaboration**: - ๐Ÿ”„ refactorer: Code quality and patterns @@ -1459,7 +1459,7 @@ Personas automatically collaborate on complex requests: For complex multi-stage operations: ```bash -/improve enterprise-system/ --wave-mode systematic +/sc:improve enterprise-system/ --wave-mode systematic ``` **Wave coordination**: @@ -1473,7 +1473,7 @@ For complex multi-stage operations: For parallel processing: ```bash -/analyze large-monorepo/ --delegate folders +/sc:analyze large-monorepo/ --delegate folders ``` **Delegation coordination**: @@ -1501,31 +1501,31 @@ SuperClaude adapts coordination based on context: #### When Auto-Coordination Goes Wrong ```bash # Too many tools activated (slow/expensive) -/analyze simple-file.js --no-mcp --answer-only +/sc:analyze simple-file.js --no-mcp --answer-only # โ†’ Minimal tooling for simple tasks # Wrong persona activated -/analyze backend-api/ --persona-security +/sc:analyze backend-api/ --persona-security # โ†’ Override with explicit persona choice # Not enough analysis depth -/troubleshoot complex-issue --ultrathink --all-mcp +/sc:troubleshoot complex-issue --ultrathink --all-mcp # โ†’ Force maximum capabilities ``` #### Optimizing Coordination ```bash # Start simple, add complexity as needed -/analyze code.js # Basic analysis -/analyze code.js --think # Add thinking -/analyze code.js --think --c7 # Add documentation -/analyze code.js --think --c7 --seq # Add systematic analysis +/sc:analyze code.js # Basic analysis +/sc:analyze code.js --think # Add thinking +/sc:analyze code.js --think --c7 # Add documentation +/sc:analyze code.js --think --c7 --seq # Add systematic analysis ``` #### Understanding Coordination Decisions ```bash # See why certain tools were chosen -/analyze complex-system/ --introspect +/sc:analyze complex-system/ --introspect # โ†’ Shows decision-making process and tool selection reasoning ``` @@ -1565,7 +1565,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 1: Project Understanding ```bash -/load --deep --summary +/sc:load --deep --summary ``` **What happens**: - ๐Ÿ” analyzer persona activates (investigation needed) @@ -1577,7 +1577,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 2: Code Quality Assessment ```bash -/scan --focus quality +/sc:scan --focus quality ``` **Auto-coordination**: - ๐Ÿงช qa persona activates (quality focus) @@ -1589,7 +1589,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 3: Architecture Understanding ```bash -/analyze --focus architecture --persona-architect +/sc:analyze --focus architecture --persona-architect ``` **What happens**: - ๐Ÿ—๏ธ architect persona provides system design perspective @@ -1601,7 +1601,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 4: Getting Started Guide ```bash -/document onboarding --type guide --persona-scribe +/sc:document onboarding --type guide --persona-scribe ``` **What happens**: - โœ๏ธ scribe persona creates professional documentation @@ -1619,7 +1619,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 1: Security-Focused Analysis ```bash -/scan auth-system/ --persona-security --focus security +/sc:scan auth-system/ --persona-security --focus security ``` **Auto-coordination**: - ๐Ÿ›ก๏ธ security persona activates (security expertise) @@ -1631,7 +1631,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 2: Root Cause Investigation ```bash -/troubleshoot "JWT token exposure in logs" --think --seq +/sc:troubleshoot "JWT token exposure in logs" --think --seq ``` **What happens**: - ๐Ÿ” analyzer persona provides investigation methodology @@ -1643,7 +1643,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 3: Secure Implementation ```bash -/improve auth-system/ --focus security --safe-mode --validate +/sc:improve auth-system/ --focus security --safe-mode --validate ``` **Auto-coordination**: - ๐Ÿ›ก๏ธ security persona maintains security focus @@ -1655,7 +1655,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 4: Security Testing ```bash -/test auth-system/ --type security --play +/sc:test auth-system/ --type security --play ``` **What happens**: - ๐Ÿงช qa persona provides testing expertise @@ -1673,7 +1673,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 1: Performance Analysis ```bash -/analyze dashboard/ --focus performance --persona-performance +/sc:analyze dashboard/ --focus performance --persona-performance ``` **Auto-coordination**: - โšก performance persona activates (performance expertise) @@ -1685,7 +1685,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 2: Frontend Performance Deep Dive ```bash -/analyze frontend/ --persona-frontend --focus performance --play +/sc:analyze frontend/ --persona-frontend --focus performance --play ``` **What happens**: - ๐ŸŽจ frontend persona provides UI/UX perspective @@ -1697,7 +1697,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 3: Backend API Performance ```bash -/analyze api/ --persona-backend --focus performance +/sc:analyze api/ --persona-backend --focus performance ``` **Auto-coordination**: - โš™๏ธ backend persona provides server-side expertise @@ -1709,7 +1709,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 4: Systematic Optimization ```bash -/improve dashboard/ --focus performance --loop --iterations 3 +/sc:improve dashboard/ --focus performance --loop --iterations 3 ``` **What happens**: - โšก performance persona leads optimization @@ -1721,7 +1721,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 5: Performance Testing Validation ```bash -/test dashboard/ --focus performance --play --benchmark +/sc:test dashboard/ --focus performance --play --benchmark ``` **What happens**: - Playwright MCP executes comprehensive performance testing @@ -1739,7 +1739,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 1: Legacy Assessment ```bash -/analyze legacy-app/ --persona-architect --ultrathink +/sc:analyze legacy-app/ --persona-architect --ultrathink ``` **Auto-coordination**: - ๐Ÿ—๏ธ architect persona provides structural analysis @@ -1751,7 +1751,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 2: Modernization Planning ```bash -/design modernization-strategy --type architecture --persona-architect +/sc:design modernization-strategy --type architecture --persona-architect ``` **What happens**: - ๐Ÿ—๏ธ architect persona designs migration strategy @@ -1763,7 +1763,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 3: Safe Incremental Improvements ```bash -/improve legacy-components/ --safe-mode --wave-mode systematic --loop +/sc:improve legacy-components/ --safe-mode --wave-mode systematic --loop ``` **Auto-coordination**: - ๐Ÿ”„ refactorer persona leads code improvements @@ -1776,7 +1776,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 4: Testing Modernization ```bash -/test modernized-app/ --type integration --coverage --play +/sc:test modernized-app/ --type integration --coverage --play ``` **What happens**: - ๐Ÿงช qa persona ensures quality throughout modernization @@ -1794,7 +1794,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 1: Requirements Analysis ```bash -/design user-service-api --type api --persona-backend +/sc:design user-service-api --type api --persona-backend ``` **Auto-coordination**: - โš™๏ธ backend persona provides API design expertise @@ -1806,7 +1806,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 2: Security Review ```bash -/review api-design/ --persona-security --focus security +/sc:review api-design/ --persona-security --focus security ``` **What happens**: - ๐Ÿ›ก๏ธ security persona evaluates API security @@ -1818,7 +1818,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 3: Performance Considerations ```bash -/analyze api-design/ --persona-performance --focus performance +/sc:analyze api-design/ --persona-performance --focus performance ``` **Auto-coordination**: - โšก performance persona evaluates scalability @@ -1830,7 +1830,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 4: Documentation for Multiple Teams ```bash -/document api/ --type api --persona-scribe --detailed +/sc:document api/ --type api --persona-scribe --detailed ``` **What happens**: - โœ๏ธ scribe persona creates professional API documentation @@ -1842,7 +1842,7 @@ Real-world scenarios showing SuperClaude in action. These examples demonstrate h #### Step 5: Implementation Validation ```bash -/build api-implementation/ --validate --test-coverage +/sc:build api-implementation/ --validate --test-coverage ``` **Auto-coordination**: - โš™๏ธ backend persona implements API patterns @@ -1886,12 +1886,12 @@ Based on real-world usage patterns and successful workflows, here are practical #### Begin with Simple Commands ```bash # Start here - basic functionality -/help -/analyze README.md -/build --help +/sc:help +/sc:analyze README.md +/sc:build --help # Not here - complex orchestration -/improve entire-codebase/ --wave-mode force --all-mcp --delegate auto +/sc:improve entire-codebase/ --wave-mode force --all-mcp --delegate auto ``` **Why**: Understanding basic behavior before adding complexity prevents confusion and helps you learn the framework gradually. @@ -1899,11 +1899,11 @@ Based on real-world usage patterns and successful workflows, here are practical #### Trust Auto-Activation First ```bash # Let SuperClaude choose tools -/analyze auth-system/ +/sc:analyze auth-system/ # โ†’ Watch what auto-activates (likely security persona + validation) # Then experiment with manual control -/analyze auth-system/ --persona-performance +/sc:analyze auth-system/ --persona-performance # โ†’ See different perspective on same code ``` @@ -1912,13 +1912,13 @@ Based on real-world usage patterns and successful workflows, here are practical #### Use Preview and Safe Modes ```bash # See what would happen first -/improve messy-code.js --preview +/sc:improve messy-code.js --preview # Apply changes safely -/improve messy-code.js --safe-mode +/sc:improve messy-code.js --safe-mode # For critical code, use both -/improve production-auth/ --preview --safe-mode --validate +/sc:improve production-auth/ --preview --safe-mode --validate ``` **Why**: Prevents unintended changes and helps you understand what SuperClaude will do before it does it. @@ -1928,16 +1928,16 @@ Based on real-world usage patterns and successful workflows, here are practical #### Start Simple, Add Complexity ```bash # Basic command -/analyze complex-system/ +/sc:analyze complex-system/ # Add thinking if needed -/analyze complex-system/ --think +/sc:analyze complex-system/ --think # Add documentation if external libraries involved -/analyze complex-system/ --think --c7 +/sc:analyze complex-system/ --think --c7 # Full analysis for critical systems -/analyze complex-system/ --think-hard --c7 --seq --validate +/sc:analyze complex-system/ --think-hard --c7 --seq --validate ``` **Why**: Incremental complexity helps you understand what each flag adds and avoids over-engineering simple problems. @@ -1945,16 +1945,16 @@ Based on real-world usage patterns and successful workflows, here are practical #### Common Flag Combinations That Work ```bash # Safe improvement workflow -/improve --preview โ†’ /improve --safe-mode โ†’ /test --coverage +/sc:improve --preview โ†’ /improve --safe-mode โ†’ /test --coverage # Deep investigation workflow -/troubleshoot issue --think --seq โ†’ /analyze affected-code/ --focus quality +/sc:troubleshoot issue --think --seq โ†’ /analyze affected-code/ --focus quality # Learning and documentation workflow -/explain concept --persona-mentor --verbose --c7 +/sc:explain concept --persona-mentor --verbose --c7 # Performance optimization workflow -/analyze --focus performance --persona-performance --play +/sc:analyze --focus performance --persona-performance --play ``` **Why**: These combinations are proven patterns that work well together and don't conflict. @@ -1962,14 +1962,14 @@ Based on real-world usage patterns and successful workflows, here are practical #### Avoid Flag Conflicts ```bash # โŒ Conflicting flags -/analyze code/ --no-mcp --c7 # --no-mcp overrides --c7 +/sc:analyze code/ --no-mcp --c7 # --no-mcp overrides --c7 # โŒ Counterproductive combinations -/analyze small-file.js --ultrathink --all-mcp # Overkill for simple tasks +/sc:analyze small-file.js --ultrathink --all-mcp # Overkill for simple tasks # โœ… Sensible combinations -/analyze large-system/ --think --delegate auto # Appropriate for complexity -/analyze simple-utility.js --answer-only # Appropriate for simplicity +/sc:analyze large-system/ --think --delegate auto # Appropriate for complexity +/sc:analyze simple-utility.js --answer-only # Appropriate for simplicity ``` **Why**: Understanding flag precedence and interactions prevents unexpected behavior and wasted resources. @@ -1979,9 +1979,9 @@ Based on real-world usage patterns and successful workflows, here are practical #### Let Domain Auto-Activation Work ```bash # These will automatically get the right persona -/build react-components/ # โ†’ frontend persona -/scan auth/ --focus security # โ†’ security persona -/troubleshoot slow-api/ # โ†’ performance + analyzer personas +/sc:build react-components/ # โ†’ frontend persona +/sc:scan auth/ --focus security # โ†’ security persona +/sc:troubleshoot slow-api/ # โ†’ performance + analyzer personas ``` **Why**: Auto-activation is based on proven patterns and usually selects the most appropriate expertise. @@ -1989,9 +1989,9 @@ Based on real-world usage patterns and successful workflows, here are practical #### Manual Override for Different Perspectives ```bash # Get different viewpoints on same code -/analyze payment-flow/ --persona-security # Security perspective -/analyze payment-flow/ --persona-performance # Performance perspective -/analyze payment-flow/ --persona-architect # Architecture perspective +/sc:analyze payment-flow/ --persona-security # Security perspective +/sc:analyze payment-flow/ --persona-performance # Performance perspective +/sc:analyze payment-flow/ --persona-architect # Architecture perspective ``` **Why**: Different personas provide unique insights that can reveal issues or opportunities others might miss. @@ -1999,16 +1999,16 @@ Based on real-world usage patterns and successful workflows, here are practical #### Use Appropriate Personas for Project Phases ```bash # Planning phase -/design new-feature --persona-architect +/sc:design new-feature --persona-architect # Implementation phase -/build feature/ --persona-frontend # or backend, etc. +/sc:build feature/ --persona-frontend # or backend, etc. # Testing phase -/test feature/ --persona-qa +/sc:test feature/ --persona-qa # Documentation phase -/document feature/ --persona-scribe +/sc:document feature/ --persona-scribe ``` **Why**: Each project phase benefits from different types of expertise and perspectives. @@ -2024,13 +2024,13 @@ Based on real-world usage patterns and successful workflows, here are practical #### Optimize for Performance vs. Capabilities ```bash # Fast execution for simple tasks -/analyze simple-script.js --no-mcp +/sc:analyze simple-script.js --no-mcp # Comprehensive analysis for complex problems -/analyze complex-system/ --all-mcp --think-hard +/sc:analyze complex-system/ --all-mcp --think-hard # Balanced approach for most work -/analyze typical-component/ --c7 # Just documentation lookup +/sc:analyze typical-component/ --c7 # Just documentation lookup ``` **Why**: Matching MCP usage to task complexity optimizes both speed and quality of results. @@ -2040,16 +2040,16 @@ Based on real-world usage patterns and successful workflows, here are practical #### Use Progressive Enhancement ```bash # Level 1: Basic analysis -/analyze component.js +/sc:analyze component.js # Level 2: Add thinking if complex -/analyze component.js --think +/sc:analyze component.js --think # Level 3: Add documentation for frameworks -/analyze component.js --think --c7 +/sc:analyze component.js --think --c7 # Level 4: Full analysis for critical code -/analyze component.js --think-hard --c7 --seq --validate +/sc:analyze component.js --think-hard --c7 --seq --validate ``` **Why**: Start with what you need and add complexity only when necessary. Prevents over-engineering and saves time. @@ -2057,14 +2057,14 @@ Based on real-world usage patterns and successful workflows, here are practical #### Batch Related Operations ```bash # โœ… Efficient: Related operations together -/analyze auth-system/ --focus security -/improve auth-system/ --focus security --safe-mode -/test auth-system/ --type security +/sc:analyze auth-system/ --focus security +/sc:improve auth-system/ --focus security --safe-mode +/sc:test auth-system/ --type security # โŒ Inefficient: Scattered operations -/analyze auth-system/ -/review different-system/ -/improve auth-system/ # Context lost between operations +/sc:analyze auth-system/ +/sc:review different-system/ +/sc:improve auth-system/ # Context lost between operations ``` **Why**: Batching related work maintains context and allows SuperClaude to build on previous analysis. @@ -2072,16 +2072,16 @@ Based on real-world usage patterns and successful workflows, here are practical #### Use Appropriate Scope ```bash # File-level for specific issues -/improve single-component.js --focus performance +/sc:improve single-component.js --focus performance # Module-level for related functionality -/analyze user-auth/ --scope module +/sc:analyze user-auth/ --scope module # Project-level for architectural concerns -/analyze --scope project --focus architecture +/sc:analyze --scope project --focus architecture # System-level only when necessary -/analyze --scope system --delegate auto --uc +/sc:analyze --scope system --delegate auto --uc ``` **Why**: Matching scope to problem prevents both under-analysis and resource waste. @@ -2091,14 +2091,14 @@ Based on real-world usage patterns and successful workflows, here are practical #### Manage Context and Token Usage ```bash # For large operations, use compression -/analyze huge-codebase/ --uc --delegate auto +/sc:analyze huge-codebase/ --uc --delegate auto # For repeated analysis, cache results -/load project-context/ # Cache project understanding -/analyze specific-issue/ # Build on cached context +/sc:load project-context/ # Cache project understanding +/sc:analyze specific-issue/ # Build on cached context # For simple questions, minimize overhead -/explain quick-concept --answer-only --no-mcp +/sc:explain quick-concept --answer-only --no-mcp ``` **Why**: Token efficiency keeps operations fast and prevents context overflow in large projects. @@ -2106,13 +2106,13 @@ Based on real-world usage patterns and successful workflows, here are practical #### Use Delegation for Large Projects ```bash # Automatically delegate when appropriate -/analyze monorepo/ --delegate auto +/sc:analyze monorepo/ --delegate auto # Manual delegation for specific needs -/analyze large-project/ --delegate folders --concurrency 3 +/sc:analyze large-project/ --delegate folders --concurrency 3 # Skip delegation for small projects -/analyze small-app/ --no-delegate +/sc:analyze small-app/ --no-delegate ``` **Why**: Delegation provides significant speedup (40-70%) for large-scale operations while maintaining quality. @@ -2120,15 +2120,15 @@ Based on real-world usage patterns and successful workflows, here are practical #### Optimize Command Sequences ```bash # โœ… Efficient sequence -/load project/ # Understand context once -/analyze --focus quality # Build on understanding -/improve --safe-mode # Apply improvements -/test --coverage # Validate changes +/sc:load project/ # Understand context once +/sc:analyze --focus quality # Build on understanding +/sc:improve --safe-mode # Apply improvements +/sc:test --coverage # Validate changes # โŒ Inefficient sequence -/analyze file1.js -/analyze file2.js # Duplicate setup -/analyze file3.js # Lost optimization opportunities +/sc:analyze file1.js +/sc:analyze file2.js # Duplicate setup +/sc:analyze file3.js # Lost optimization opportunities ``` **Why**: Sequential commands can build on each other's context and analysis for better results. @@ -2138,13 +2138,13 @@ Based on real-world usage patterns and successful workflows, here are practical #### Always Validate Important Changes ```bash # For production code -/improve production-auth/ --safe-mode --validate --preview +/sc:improve production-auth/ --safe-mode --validate --preview # For experimental features -/improve experimental-feature/ --validate +/sc:improve experimental-feature/ --validate # For learning/exploration -/improve test-code/ --preview # See what it would do +/sc:improve test-code/ --preview # See what it would do ``` **Why**: Validation prevents breaking changes and helps you understand the impact of modifications. @@ -2152,13 +2152,13 @@ Based on real-world usage patterns and successful workflows, here are practical #### Use Quality Gates Effectively ```bash # Let quality gates run automatically -/build production-app/ # 8-step validation process runs +/sc:build production-app/ # 8-step validation process runs # Add extra validation for critical systems -/build payment-system/ --validate --safe-mode +/sc:build payment-system/ --validate --safe-mode # Skip validation only for experimental work -/build prototype/ --no-validate # Use sparingly +/sc:build prototype/ --no-validate # Use sparingly ``` **Why**: Quality gates catch issues early when they're cheaper and easier to fix. @@ -2166,12 +2166,12 @@ Based on real-world usage patterns and successful workflows, here are practical #### Maintain Evidence Trail ```bash # Commands that provide evidence -/analyze --focus performance # โ†’ Performance metrics -/test --coverage # โ†’ Coverage reports -/scan --focus security # โ†’ Security assessment +/sc:analyze --focus performance # โ†’ Performance metrics +/sc:test --coverage # โ†’ Coverage reports +/sc:scan --focus security # โ†’ Security assessment # Use introspection for complex decisions -/analyze complex-system/ --introspect # โ†’ Decision reasoning +/sc:analyze complex-system/ --introspect # โ†’ Decision reasoning ``` **Why**: Evidence-based development leads to better decisions and easier debugging when issues arise. @@ -2181,13 +2181,13 @@ Based on real-world usage patterns and successful workflows, here are practical #### Use Mentor Persona for Learning ```bash # Learn new concepts -/explain GraphQL --persona-mentor --verbose +/sc:explain GraphQL --persona-mentor --verbose # Understand complex code -/analyze complex-algorithm.js --persona-mentor +/sc:analyze complex-algorithm.js --persona-mentor # Get step-by-step guidance -/build new-feature/ --persona-mentor --plan +/sc:build new-feature/ --persona-mentor --plan ``` **Why**: Mentor persona optimizes for understanding and knowledge transfer rather than just task completion. @@ -2195,13 +2195,13 @@ Based on real-world usage patterns and successful workflows, here are practical #### Experiment with Different Approaches ```bash # Try different personas on same problem -/analyze api-design/ --persona-architect -/analyze api-design/ --persona-security -/analyze api-design/ --persona-performance +/sc:analyze api-design/ --persona-architect +/sc:analyze api-design/ --persona-security +/sc:analyze api-design/ --persona-performance # Compare tool combinations -/build app/ --magic --c7 -/build app/ --no-mcp --uc # Faster but simpler +/sc:build app/ --magic --c7 +/sc:build app/ --no-mcp --uc # Faster but simpler ``` **Why**: Understanding different approaches helps you choose the best tools for different situations. @@ -2210,12 +2210,12 @@ Based on real-world usage patterns and successful workflows, here are practical ```bash # Identify what works for your workflow # Security-focused API development -/design api --persona-security --validate -/build api --persona-backend --c7 -/test api --type security --play +/sc:design api --persona-security --validate +/sc:build api --persona-backend --c7 +/sc:test api --type security --play # Create your own efficient combinations -/analyze code/ --think --c7 --safe-mode # Your personal "thorough analysis" +/sc:analyze code/ --think --c7 --safe-mode # Your personal "thorough analysis" ``` **Why**: Developing your own proven patterns increases productivity and ensures consistent quality. @@ -2225,38 +2225,38 @@ Based on real-world usage patterns and successful workflows, here are practical #### Don't Over-Engineer Simple Tasks ```bash # โŒ Overkill for simple tasks -/analyze simple-utility.js --ultrathink --all-mcp --wave-mode force +/sc:analyze simple-utility.js --ultrathink --all-mcp --wave-mode force # โœ… Appropriate for simple tasks -/analyze simple-utility.js --focus quality +/sc:analyze simple-utility.js --focus quality ``` #### Don't Ignore Auto-Activation Wisdom ```bash # โŒ Fighting the system -/build react-app/ --persona-backend --no-magic # Wrong tools for the job +/sc:build react-app/ --persona-backend --no-magic # Wrong tools for the job # โœ… Working with the system -/build react-app/ # Let frontend persona and Magic activate automatically +/sc:build react-app/ # Let frontend persona and Magic activate automatically ``` #### Don't Skip Safety for Speed ```bash # โŒ Risky for important code -/improve production-auth/ --force --no-validate +/sc:improve production-auth/ --force --no-validate # โœ… Balanced approach -/improve production-auth/ --safe-mode --validate # Safer but still efficient +/sc:improve production-auth/ --safe-mode --validate # Safer but still efficient ``` #### Don't Use Flags You Don't Understand ```bash # โŒ Cargo cult flag usage -/command --random-flags-that-look-important +/sc:command --random-flags-that-look-important # โœ… Understand what each flag does -/command --think # Because I need deeper analysis -/command --c7 # Because I'm working with external libraries +/sc:command --think # Because I need deeper analysis +/sc:command --c7 # Because I'm working with external libraries ``` ### Measuring Success ๐Ÿ“Š @@ -2285,26 +2285,26 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Diagnosis**: ```bash # Check what auto-activated -/analyze code.js --introspect +/sc:analyze code.js --introspect # โ†’ Shows decision-making process # Try with explicit control -/analyze code.js --persona-analyzer --think --seq +/sc:analyze code.js --persona-analyzer --think --seq # โ†’ Override auto-activation ``` **Solutions**: ```bash # Be more specific about what you want -/improve code.js --focus performance --safe-mode +/sc:improve code.js --focus performance --safe-mode # Use preview to understand what will happen -/improve code.js --preview +/sc:improve code.js --preview # Start simple and add complexity -/analyze code.js # Basic -/analyze code.js --think # Add depth -/analyze code.js --think --c7 # Add documentation +/sc:analyze code.js # Basic +/sc:analyze code.js --think # Add depth +/sc:analyze code.js --think --c7 # Add documentation ``` **Common Causes**: @@ -2319,27 +2319,27 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Diagnosis**: ```bash # Check what's activated -/analyze large-project/ --introspect +/sc:analyze large-project/ --introspect # โ†’ See what tools and servers are being used # Monitor resource usage -/analyze large-project/ --verbose +/sc:analyze large-project/ --verbose # โ†’ Shows detailed execution steps ``` **Solutions**: ```bash # Optimize for speed -/analyze large-project/ --uc --no-mcp --scope module +/sc:analyze large-project/ --uc --no-mcp --scope module # Use delegation for large operations -/analyze huge-codebase/ --delegate auto --concurrency 3 +/sc:analyze huge-codebase/ --delegate auto --concurrency 3 # Reduce scope -/analyze specific-component.js # Instead of entire project +/sc:analyze specific-component.js # Instead of entire project # Disable expensive features -/analyze code/ --no-mcp --answer-only +/sc:analyze code/ --no-mcp --answer-only ``` **Performance Optimization Priority**: @@ -2356,16 +2356,16 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Solutions**: ```bash # Use compression -/analyze large-system/ --uc +/sc:analyze large-system/ --uc # Be more specific about focus -/analyze system/ --focus security # Instead of general analysis +/sc:analyze system/ --focus security # Instead of general analysis # Use answer-only for simple questions -/explain concept --answer-only +/sc:explain concept --answer-only # Limit scope -/analyze --scope file specific-issue.js +/sc:analyze --scope file specific-issue.js ``` ### Flag Issues ๐Ÿ @@ -2377,13 +2377,13 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Common Conflicts**: ```bash # โŒ These conflict -/command --no-mcp --c7 # --no-mcp overrides --c7 -/command --answer-only --plan # --answer-only skips planning -/command --uc --verbose # --uc overrides --verbose +/sc:command --no-mcp --c7 # --no-mcp overrides --c7 +/sc:command --answer-only --plan # --answer-only skips planning +/sc:command --uc --verbose # --uc overrides --verbose # โœ… These work together -/command --think --c7 --seq # Complementary capabilities -/command --safe-mode --validate --preview # Layered safety +/sc:command --think --c7 --seq # Complementary capabilities +/sc:command --safe-mode --validate --preview # Layered safety ``` **Flag Precedence Order**: @@ -2396,7 +2396,7 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Diagnosis**: ```bash # Check what flags are actually active -/command args --introspect +/sc:command args --introspect # โ†’ Shows final flag configuration after precedence resolution ``` @@ -2407,22 +2407,22 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Solutions**: ```bash # Override auto-activation explicitly -/analyze frontend-code/ --persona-security # Force security view -/build project/ --no-mcp # Force native tools only +/sc:analyze frontend-code/ --persona-security # Force security view +/sc:build project/ --no-mcp # Force native tools only # Use more specific language -/analyze "security vulnerabilities in auth system" # Clear intent +/sc:analyze "security vulnerabilities in auth system" # Clear intent # vs -/analyze auth system # Ambiguous +/sc:analyze auth system # Ambiguous # Check what keywords trigger auto-activation -/help analyze # Shows auto-activation patterns +/sc:help analyze # Shows auto-activation patterns ``` **Auto-Activation Debugging**: ```bash # See why certain flags activated -/troubleshoot "why did --think-hard activate?" --introspect +/sc:troubleshoot "why did --think-hard activate?" --introspect ``` ### Persona Issues ๐ŸŽญ @@ -2434,23 +2434,23 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Diagnosis**: ```bash # Check what triggered persona activation -/analyze code/ --introspect +/sc:analyze code/ --introspect # โ†’ Shows persona selection reasoning ``` **Solutions**: ```bash # Override with explicit persona -/analyze backend-api/ --persona-security # Security view of backend code -/analyze ui-component/ --persona-performance # Performance view of frontend +/sc:analyze backend-api/ --persona-security # Security view of backend code +/sc:analyze ui-component/ --persona-performance # Performance view of frontend # Use more specific language -/analyze "security issues in payment processing" # Triggers security persona -/analyze "slow database queries" # Triggers performance persona +/sc:analyze "security issues in payment processing" # Triggers security persona +/sc:analyze "slow database queries" # Triggers performance persona # Try different personas for different perspectives -/analyze payment-system/ --persona-security # Security view -/analyze payment-system/ --persona-architect # Architecture view +/sc:analyze payment-system/ --persona-security # Security view +/sc:analyze payment-system/ --persona-architect # Architecture view ``` #### Persona Doesn't Seem Active @@ -2460,22 +2460,22 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Check Persona Activation**: ```bash # Verify persona is active -/analyze auth/ --persona-security --introspect +/sc:analyze auth/ --persona-security --introspect # โ†’ Should show security-focused reasoning # Check if domain keywords are clear -/scan authentication --focus security # Should auto-activate security persona +/sc:scan authentication --focus security # Should auto-activate security persona ``` **Solutions**: ```bash # Be explicit about persona and focus -/analyze code/ --persona-security --focus security +/sc:analyze code/ --persona-security --focus security # Use appropriate commands for personas -/scan --persona-security # Security scanning -/test --persona-qa # Quality-focused testing -/document --persona-scribe # Professional documentation +/sc:scan --persona-security # Security scanning +/sc:test --persona-qa # Quality-focused testing +/sc:document --persona-scribe # Professional documentation ``` ### MCP Server Issues ๐Ÿ”ง @@ -2487,28 +2487,28 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Diagnosis**: ```bash # Check MCP server status -/troubleshoot "MCP servers not working" --introspect +/sc:troubleshoot "MCP servers not working" --introspect # Verify MCP installation -/load --summary # Should show available MCP servers +/sc:load --summary # Should show available MCP servers # Test specific servers -/analyze react-app/ --c7 # Should use Context7 -/troubleshoot issue --seq # Should use Sequential -/build ui/ --magic # Should use Magic -/test app/ --play # Should use Playwright +/sc:analyze react-app/ --c7 # Should use Context7 +/sc:troubleshoot issue --seq # Should use Sequential +/sc:build ui/ --magic # Should use Magic +/sc:test app/ --play # Should use Playwright ``` **Common Solutions**: ```bash # Force MCP activation -/analyze code/ --all-mcp +/sc:analyze code/ --all-mcp # Check if servers are disabled -/analyze code/ --c7 # If this doesn't work, Context7 may be unavailable +/sc:analyze code/ --c7 # If this doesn't work, Context7 may be unavailable # Use fallback approaches -/analyze react-app/ --no-mcp # Use native tools if MCP unavailable +/sc:analyze react-app/ --no-mcp # Use native tools if MCP unavailable ``` #### MCP Servers Too Slow @@ -2518,13 +2518,13 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Solutions**: ```bash # Disable MCP for speed -/analyze large-project/ --no-mcp +/sc:analyze large-project/ --no-mcp # Use selective MCP activation -/analyze react-code/ --magic --no-seq # Only UI generation, skip analysis +/sc:analyze react-code/ --magic --no-seq # Only UI generation, skip analysis # Optimize MCP usage -/analyze code/ --uc --c7 # Compression + documentation only +/sc:analyze code/ --uc --c7 # Compression + documentation only ``` ### Performance Issues โšก @@ -2536,17 +2536,17 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Solutions**: ```bash # Enable compression automatically -/analyze huge-project/ --uc +/sc:analyze huge-project/ --uc # Reduce scope -/analyze --scope module specific-area/ -/analyze --scope file specific-file.js +/sc:analyze --scope module specific-area/ +/sc:analyze --scope file specific-file.js # Use delegation -/analyze large-codebase/ --delegate auto --uc +/sc:analyze large-codebase/ --delegate auto --uc # Disable expensive features -/analyze code/ --no-mcp --answer-only +/sc:analyze code/ --no-mcp --answer-only ``` #### Memory or Resource Issues @@ -2556,15 +2556,15 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Solutions**: ```bash # Reduce concurrency -/analyze large-project/ --delegate auto --concurrency 1 +/sc:analyze large-project/ --delegate auto --concurrency 1 # Use safe mode -/improve large-system/ --safe-mode # More conservative resource usage +/sc:improve large-system/ --safe-mode # More conservative resource usage # Break work into smaller chunks -/analyze module1/ -/analyze module2/ -/analyze module3/ +/sc:analyze module1/ +/sc:analyze module2/ +/sc:analyze module3/ # Instead of /analyze entire-project/ ``` @@ -2577,16 +2577,16 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Always Use Safety Features**: ```bash # Preview before applying -/improve important-code/ --preview +/sc:improve important-code/ --preview # Use safe mode for critical code -/improve production-auth/ --safe-mode +/sc:improve production-auth/ --safe-mode # Add validation -/improve system/ --validate --safe-mode +/sc:improve system/ --validate --safe-mode # Use iterative approach -/improve complex-system/ --loop --safe-mode +/sc:improve complex-system/ --loop --safe-mode ``` #### Changes Breaking Functionality @@ -2596,13 +2596,13 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Prevention**: ```bash # Always use preview first -/improve code/ --preview +/sc:improve code/ --preview # Use safe mode -/improve code/ --safe-mode +/sc:improve code/ --safe-mode # Test after changes -/improve code/ --safe-mode && /test code/ +/sc:improve code/ --safe-mode && /test code/ ``` **Recovery**: @@ -2619,14 +2619,14 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Solutions**: ```bash # Load project context first -/load --deep --summary +/sc:load --deep --summary # Be explicit about project type -/analyze react-typescript-app/ --c7 # Include tech stack in description +/sc:analyze react-typescript-app/ --c7 # Include tech stack in description # Use appropriate personas -/analyze node-api/ --persona-backend -/analyze react-ui/ --persona-frontend +/sc:analyze node-api/ --persona-backend +/sc:analyze react-ui/ --persona-frontend ``` #### Inconsistent Results @@ -2636,20 +2636,20 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Diagnosis**: ```bash # Check what's auto-activating differently -/command args --introspect +/sc:command args --introspect # Use explicit flags for consistency -/analyze code/ --persona-analyzer --think --c7 # Explicit configuration +/sc:analyze code/ --persona-analyzer --think --c7 # Explicit configuration ``` **Solutions**: ```bash # Be more explicit about requirements -/improve code/ --focus performance --persona-performance --safe-mode +/sc:improve code/ --focus performance --persona-performance --safe-mode # Use consistent flag patterns -/analyze --think --c7 # Your standard thorough analysis -/improve --safe-mode # Your standard safe improvement +/sc:analyze --think --c7 # Your standard thorough analysis +/sc:improve --safe-mode # Your standard safe improvement ``` ### Getting Help ๐Ÿ†˜ @@ -2665,15 +2665,15 @@ When SuperClaude doesn't work as expected, here's how to diagnose and fix common **Escalation Path**: ```bash # Get framework help -/troubleshoot "SuperClaude framework issues" --introspect +/sc:troubleshoot "SuperClaude framework issues" --introspect # Check documentation -/help # Command overview -/analyze --help # Specific command help +/sc:help # Command overview +/sc:analyze --help # Specific command help # Test basic functionality -/analyze README.md # Simple test -/build --help # Check if commands work +/sc:analyze README.md # Simple test +/sc:build --help # Check if commands work ``` #### Reporting Issues @@ -2688,7 +2688,7 @@ When reporting problems, include: **Useful Debug Information**: ```bash # Get diagnostic information -/troubleshoot "describe your issue" --introspect --verbose +/sc:troubleshoot "describe your issue" --introspect --verbose # โ†’ Provides detailed context for bug reports ``` @@ -2854,7 +2854,7 @@ We actively monitor: #### How to Keep Current ```bash # Check for updates regularly -/help # Shows current version and update availability +/sc:help # Shows current version and update availability # Monitor development progress # - GitHub releases: Feature announcements and changelogs diff --git a/README.md b/README.md index 20338f6..48c016e 100644 --- a/README.md +++ b/README.md @@ -40,10 +40,10 @@ This is what we've been working on to make Claude Code more helpful for developm ### Commands ๐Ÿ› ๏ธ We focused on 15 essential commands for the most common tasks: -**Development**: `/build`, `/dev-setup` -**Analysis**: `/analyze`, `/review`, `/troubleshoot` -**Quality**: `/improve`, `/scan`, `/test` -**Others**: `/document`, `/deploy`, `/git`, `/migrate`, `/estimate`, `/task`, `/design` +**Development**: `/sc:build`, `/sc:dev-setup` +**Analysis**: `/sc:analyze`, `/sc:review`, `/sc:troubleshoot` +**Quality**: `/sc:improve`, `/sc:scan`, `/sc:test` +**Others**: `/sc:document`, `/sc:deploy`, `/sc:git`, `/sc:migrate`, `/sc:estimate`, `/sc:task`, `/sc:design` ### Smart Personas ๐ŸŽญ Auto-activating specialists that adapt Claude's behavior: diff --git a/SuperClaude/Commands/analyze.md b/SuperClaude/Commands/analyze.md index 9953f18..f8b16f1 100644 --- a/SuperClaude/Commands/analyze.md +++ b/SuperClaude/Commands/analyze.md @@ -3,14 +3,14 @@ allowed-tools: [Read, Grep, Glob, Bash, TodoWrite] description: "Analyze code quality, security, performance, and architecture" --- -# /analyze - Code Analysis +# /sc:analyze - Code Analysis ## Purpose Execute comprehensive code analysis across quality, security, performance, and architecture domains. ## Usage ``` -/analyze [target] [--focus quality|security|performance|architecture] [--depth quick|deep] +/sc:analyze [target] [--focus quality|security|performance|architecture] [--depth quick|deep] ``` ## Arguments diff --git a/SuperClaude/Commands/build.md b/SuperClaude/Commands/build.md index fc8765b..67fc634 100644 --- a/SuperClaude/Commands/build.md +++ b/SuperClaude/Commands/build.md @@ -3,14 +3,14 @@ allowed-tools: [Read, Bash, Glob, TodoWrite, Edit] description: "Build, compile, and package projects with error handling and optimization" --- -# /build - Project Building +# /sc:build - Project Building ## Purpose Build, compile, and package projects with comprehensive error handling and optimization. ## Usage ``` -/build [target] [--type dev|prod|test] [--clean] [--optimize] +/sc:build [target] [--type dev|prod|test] [--clean] [--optimize] ``` ## Arguments diff --git a/SuperClaude/Commands/cleanup.md b/SuperClaude/Commands/cleanup.md index 7a140c9..6f9999e 100644 --- a/SuperClaude/Commands/cleanup.md +++ b/SuperClaude/Commands/cleanup.md @@ -3,14 +3,14 @@ allowed-tools: [Read, Grep, Glob, Bash, Edit, MultiEdit] description: "Clean up code, remove dead code, and optimize project structure" --- -# /cleanup - Code and Project Cleanup +# /sc:cleanup - Code and Project Cleanup ## Purpose Systematically clean up code, remove dead code, optimize imports, and improve project structure. ## Usage ``` -/cleanup [target] [--type code|imports|files|all] [--safe|--aggressive] +/sc:cleanup [target] [--type code|imports|files|all] [--safe|--aggressive] ``` ## Arguments diff --git a/SuperClaude/Commands/design.md b/SuperClaude/Commands/design.md index 2598a9c..04fe8af 100644 --- a/SuperClaude/Commands/design.md +++ b/SuperClaude/Commands/design.md @@ -3,14 +3,14 @@ allowed-tools: [Read, Grep, Glob, Write, Edit, TodoWrite] description: "Design system architecture, APIs, and component interfaces" --- -# /design - System and Component Design +# /sc:design - System and Component Design ## Purpose Design system architecture, APIs, component interfaces, and technical specifications. ## Usage ``` -/design [target] [--type architecture|api|component|database] [--format diagram|spec|code] +/sc:design [target] [--type architecture|api|component|database] [--format diagram|spec|code] ``` ## Arguments diff --git a/SuperClaude/Commands/document.md b/SuperClaude/Commands/document.md index eac9a7f..e714f84 100644 --- a/SuperClaude/Commands/document.md +++ b/SuperClaude/Commands/document.md @@ -3,14 +3,14 @@ allowed-tools: [Read, Grep, Glob, Write, Edit] description: "Create focused documentation for specific components or features" --- -# /document - Focused Documentation +# /sc:document - Focused Documentation ## Purpose Generate precise, focused documentation for specific components, functions, or features. ## Usage ``` -/document [target] [--type inline|external|api|guide] [--style brief|detailed] +/sc:document [target] [--type inline|external|api|guide] [--style brief|detailed] ``` ## Arguments diff --git a/SuperClaude/Commands/estimate.md b/SuperClaude/Commands/estimate.md index d2b6943..7555d86 100644 --- a/SuperClaude/Commands/estimate.md +++ b/SuperClaude/Commands/estimate.md @@ -3,14 +3,14 @@ allowed-tools: [Read, Grep, Glob, Bash] description: "Provide development estimates for tasks, features, or projects" --- -# /estimate - Development Estimation +# /sc:estimate - Development Estimation ## Purpose Generate accurate development estimates for tasks, features, or projects based on complexity analysis. ## Usage ``` -/estimate [target] [--type time|effort|complexity|cost] [--unit hours|days|weeks] +/sc:estimate [target] [--type time|effort|complexity|cost] [--unit hours|days|weeks] ``` ## Arguments diff --git a/SuperClaude/Commands/explain.md b/SuperClaude/Commands/explain.md index 26c63a3..0c085a1 100644 --- a/SuperClaude/Commands/explain.md +++ b/SuperClaude/Commands/explain.md @@ -3,14 +3,14 @@ allowed-tools: [Read, Grep, Glob, Bash] description: "Provide clear explanations of code, concepts, or system behavior" --- -# /explain - Code and Concept Explanation +# /sc:explain - Code and Concept Explanation ## Purpose Deliver clear, comprehensive explanations of code functionality, concepts, or system behavior. ## Usage ``` -/explain [target] [--level basic|intermediate|advanced] [--format text|diagram|examples] +/sc:explain [target] [--level basic|intermediate|advanced] [--format text|diagram|examples] ``` ## Arguments diff --git a/SuperClaude/Commands/git.md b/SuperClaude/Commands/git.md index 332bd1f..ebffeb2 100644 --- a/SuperClaude/Commands/git.md +++ b/SuperClaude/Commands/git.md @@ -3,14 +3,14 @@ allowed-tools: [Bash, Read, Glob, TodoWrite, Edit] description: "Git operations with intelligent commit messages and branch management" --- -# /git - Git Operations +# /sc:git - Git Operations ## Purpose Execute Git operations with intelligent commit messages, branch management, and workflow optimization. ## Usage ``` -/git [operation] [args] [--smart-commit] [--branch-strategy] +/sc:git [operation] [args] [--smart-commit] [--branch-strategy] ``` ## Arguments diff --git a/SuperClaude/Commands/improve.md b/SuperClaude/Commands/improve.md index 59e03ad..6521423 100644 --- a/SuperClaude/Commands/improve.md +++ b/SuperClaude/Commands/improve.md @@ -3,14 +3,14 @@ allowed-tools: [Read, Grep, Glob, Edit, MultiEdit, TodoWrite] description: "Apply systematic improvements to code quality, performance, and maintainability" --- -# /improve - Code Improvement +# /sc:improve - Code Improvement ## Purpose Apply systematic improvements to code quality, performance, maintainability, and best practices. ## Usage ``` -/improve [target] [--type quality|performance|maintainability|style] [--safe] +/sc:improve [target] [--type quality|performance|maintainability|style] [--safe] ``` ## Arguments diff --git a/SuperClaude/Commands/index.md b/SuperClaude/Commands/index.md index bbea06b..e2e2838 100644 --- a/SuperClaude/Commands/index.md +++ b/SuperClaude/Commands/index.md @@ -3,14 +3,14 @@ allowed-tools: [Read, Grep, Glob, Bash, Write] description: "Generate comprehensive project documentation and knowledge base" --- -# /index - Project Documentation +# /sc:index - Project Documentation ## Purpose Create and maintain comprehensive project documentation, indexes, and knowledge bases. ## Usage ``` -/index [target] [--type docs|api|structure|readme] [--format md|json|yaml] +/sc:index [target] [--type docs|api|structure|readme] [--format md|json|yaml] ``` ## Arguments diff --git a/SuperClaude/Commands/load.md b/SuperClaude/Commands/load.md index 054a370..5b1055b 100644 --- a/SuperClaude/Commands/load.md +++ b/SuperClaude/Commands/load.md @@ -3,14 +3,14 @@ allowed-tools: [Read, Grep, Glob, Bash, Write] description: "Load and analyze project context, configurations, and dependencies" --- -# /load - Project Context Loading +# /sc:load - Project Context Loading ## Purpose Load and analyze project context, configurations, dependencies, and environment setup. ## Usage ``` -/load [target] [--type project|config|deps|env] [--cache] +/sc:load [target] [--type project|config|deps|env] [--cache] ``` ## Arguments diff --git a/SuperClaude/Commands/spawn.md b/SuperClaude/Commands/spawn.md index ae51cd2..6e53a62 100644 --- a/SuperClaude/Commands/spawn.md +++ b/SuperClaude/Commands/spawn.md @@ -3,14 +3,14 @@ allowed-tools: [Read, Grep, Glob, Bash, TodoWrite, Edit, MultiEdit, Write] description: "Break complex tasks into coordinated subtasks with efficient execution" --- -# /spawn - Task Orchestration +# /sc:spawn - Task Orchestration ## Purpose Decompose complex requests into manageable subtasks and coordinate their execution. ## Usage ``` -/spawn [task] [--sequential|--parallel] [--validate] +/sc:spawn [task] [--sequential|--parallel] [--validate] ``` ## Arguments diff --git a/SuperClaude/Commands/task.md b/SuperClaude/Commands/task.md index 5728e4b..491bcaa 100644 --- a/SuperClaude/Commands/task.md +++ b/SuperClaude/Commands/task.md @@ -8,14 +8,14 @@ personas: [architect, analyzer, project-manager] mcp-servers: [sequential, context7] --- -# /task - Enhanced Task Management +# /sc:task - Enhanced Task Management ## Purpose Execute complex tasks with intelligent workflow management, cross-session persistence, hierarchical task organization, and advanced orchestration capabilities. ## Usage ``` -/task [action] [target] [--strategy systematic|agile|enterprise] [--persist] [--hierarchy] [--delegate] +/sc:task [action] [target] [--strategy systematic|agile|enterprise] [--persist] [--hierarchy] [--delegate] ``` ## Actions @@ -124,22 +124,22 @@ Execute complex tasks with intelligent workflow management, cross-session persis ### Create Project-Level Task Hierarchy ``` -/task create "Implement user authentication system" --hierarchy --persist --strategy systematic +/sc:task create "Implement user authentication system" --hierarchy --persist --strategy systematic ``` ### Execute with Multi-Agent Delegation ``` -/task execute AUTH-001 --delegate --wave-mode --validate +/sc:task execute AUTH-001 --delegate --wave-mode --validate ``` ### Analytics and Optimization ``` -/task analytics --project AUTH --optimization-recommendations +/sc:task analytics --project AUTH --optimization-recommendations ``` ### Cross-Session Task Management ``` -/task status --all-sessions --detailed-breakdown +/sc:task status --all-sessions --detailed-breakdown ``` ## Claude Code Integration diff --git a/SuperClaude/Commands/test.md b/SuperClaude/Commands/test.md index 9b0fb40..a049cfa 100644 --- a/SuperClaude/Commands/test.md +++ b/SuperClaude/Commands/test.md @@ -3,14 +3,14 @@ allowed-tools: [Read, Bash, Glob, TodoWrite, Edit, Write] description: "Execute tests, generate test reports, and maintain test coverage" --- -# /test - Testing and Quality Assurance +# /sc:test - Testing and Quality Assurance ## Purpose Execute tests, generate comprehensive test reports, and maintain test coverage standards. ## Usage ``` -/test [target] [--type unit|integration|e2e|all] [--coverage] [--watch] +/sc:test [target] [--type unit|integration|e2e|all] [--coverage] [--watch] ``` ## Arguments diff --git a/SuperClaude/Commands/troubleshoot.md b/SuperClaude/Commands/troubleshoot.md index 7a79e58..2a8587b 100644 --- a/SuperClaude/Commands/troubleshoot.md +++ b/SuperClaude/Commands/troubleshoot.md @@ -3,14 +3,14 @@ allowed-tools: [Read, Grep, Glob, Bash, TodoWrite] description: "Diagnose and resolve issues in code, builds, or system behavior" --- -# /troubleshoot - Issue Diagnosis and Resolution +# /sc:troubleshoot - Issue Diagnosis and Resolution ## Purpose Systematically diagnose and resolve issues in code, builds, deployments, or system behavior. ## Usage ``` -/troubleshoot [issue] [--type bug|build|performance|deployment] [--trace] +/sc:troubleshoot [issue] [--type bug|build|performance|deployment] [--trace] ``` ## Arguments diff --git a/setup/components/commands.py b/setup/components/commands.py index 2c222ad..142ccec 100644 --- a/setup/components/commands.py +++ b/setup/components/commands.py @@ -71,7 +71,7 @@ class CommandsComponent(Component): errors.append(f"Missing command files: {missing_files}") # Check write permissions to install directory - commands_dir = self.install_dir / "commands" + commands_dir = self.install_dir / "commands" / "sc" has_perms, missing = SecurityValidator.check_permissions( self.install_dir, {'write'} ) @@ -92,7 +92,7 @@ class CommandsComponent(Component): for filename in self.command_files: source = source_dir / filename - target = self.install_dir / "commands" / filename + target = self.install_dir / "commands" / "sc" / filename files.append((source, target)) return files @@ -119,6 +119,9 @@ class CommandsComponent(Component): try: self.logger.info("Installing SuperClaude command definitions...") + # Check for and migrate existing commands from old location + self._migrate_existing_commands() + # Validate installation success, errors = self.validate_prerequisites() if not success: @@ -131,7 +134,7 @@ class CommandsComponent(Component): # Validate all files for security source_dir = self._get_source_dir() - commands_dir = self.install_dir / "commands" + commands_dir = self.install_dir / "commands" / "sc" is_safe, security_errors = SecurityValidator.validate_component_files( files_to_install, source_dir, commands_dir ) @@ -185,8 +188,8 @@ class CommandsComponent(Component): try: self.logger.info("Uninstalling SuperClaude commands component...") - # Remove command files - commands_dir = self.install_dir / "commands" + # Remove command files from sc subdirectory + commands_dir = self.install_dir / "commands" / "sc" removed_count = 0 for filename in self.command_files: @@ -197,13 +200,39 @@ class CommandsComponent(Component): else: self.logger.warning(f"Could not remove {filename}") - # Remove commands directory if empty + # Also check and remove any old commands in root commands directory + old_commands_dir = self.install_dir / "commands" + old_removed_count = 0 + + for filename in self.command_files: + old_file_path = old_commands_dir / filename + if old_file_path.exists() and old_file_path.is_file(): + if self.file_manager.remove_file(old_file_path): + old_removed_count += 1 + self.logger.debug(f"Removed old {filename}") + else: + self.logger.warning(f"Could not remove old {filename}") + + if old_removed_count > 0: + self.logger.info(f"Also removed {old_removed_count} commands from old location") + + removed_count += old_removed_count + + # Remove sc subdirectory if empty try: if commands_dir.exists(): remaining_files = list(commands_dir.iterdir()) if not remaining_files: commands_dir.rmdir() - self.logger.debug("Removed empty commands directory") + self.logger.debug("Removed empty sc commands directory") + + # Also remove parent commands directory if empty + parent_commands_dir = self.install_dir / "commands" + if parent_commands_dir.exists(): + remaining_files = list(parent_commands_dir.iterdir()) + if not remaining_files: + parent_commands_dir.rmdir() + self.logger.debug("Removed empty parent commands directory") except Exception as e: self.logger.warning(f"Could not remove commands directory: {e}") @@ -242,7 +271,7 @@ class CommandsComponent(Component): self.logger.info(f"Updating commands component from {current_version} to {target_version}") # Create backup of existing command files - commands_dir = self.install_dir / "commands" + commands_dir = self.install_dir / "commands" / "sc" backup_files = [] if commands_dir.exists(): @@ -287,10 +316,10 @@ class CommandsComponent(Component): """Validate commands component installation""" errors = [] - # Check if commands directory exists - commands_dir = self.install_dir / "commands" + # Check if sc commands directory exists + commands_dir = self.install_dir / "commands" / "sc" if not commands_dir.exists(): - errors.append("Commands directory not found") + errors.append("SC commands directory not found") return False, errors # Check if all command files exist @@ -343,6 +372,67 @@ class CommandsComponent(Component): "files_installed": len(self.command_files), "command_files": self.command_files, "estimated_size": self.get_size_estimate(), - "install_directory": str(self.install_dir / "commands"), + "install_directory": str(self.install_dir / "commands" / "sc"), "dependencies": self.get_dependencies() - } \ No newline at end of file + } + + def _migrate_existing_commands(self) -> None: + """Migrate existing commands from old location to new sc subdirectory""" + try: + old_commands_dir = self.install_dir / "commands" + new_commands_dir = self.install_dir / "commands" / "sc" + + # Check if old commands exist in root commands directory + migrated_count = 0 + commands_to_migrate = [] + + if old_commands_dir.exists(): + for filename in self.command_files: + old_file_path = old_commands_dir / filename + if old_file_path.exists() and old_file_path.is_file(): + commands_to_migrate.append(filename) + + if commands_to_migrate: + self.logger.info(f"Found {len(commands_to_migrate)} existing commands to migrate to sc/ subdirectory") + + # Ensure new directory exists + if not self.file_manager.ensure_directory(new_commands_dir): + self.logger.error(f"Could not create sc commands directory: {new_commands_dir}") + return + + # Move files from old to new location + for filename in commands_to_migrate: + old_file_path = old_commands_dir / filename + new_file_path = new_commands_dir / filename + + try: + # Copy file to new location + if self.file_manager.copy_file(old_file_path, new_file_path): + # Remove old file + if self.file_manager.remove_file(old_file_path): + migrated_count += 1 + self.logger.debug(f"Migrated {filename} to sc/ subdirectory") + else: + self.logger.warning(f"Could not remove old {filename}") + else: + self.logger.warning(f"Could not copy {filename} to sc/ subdirectory") + except Exception as e: + self.logger.warning(f"Error migrating {filename}: {e}") + + if migrated_count > 0: + self.logger.success(f"Successfully migrated {migrated_count} commands to /sc: namespace") + self.logger.info("Commands are now available as /sc:analyze, /sc:build, etc.") + + # Try to remove old commands directory if empty + try: + if old_commands_dir.exists(): + remaining_files = [f for f in old_commands_dir.iterdir() if f.is_file()] + if not remaining_files: + # Only remove if no user files remain + old_commands_dir.rmdir() + self.logger.debug("Removed empty old commands directory") + except Exception as e: + self.logger.debug(f"Could not remove old commands directory: {e}") + + except Exception as e: + self.logger.warning(f"Error during command migration: {e}") \ No newline at end of file