* Fix: Install only selected MCP servers and ensure valid empty backups This commit addresses two separate issues: 1. **MCP Installation:** The `install` command was installing all MCP servers instead of only the ones selected by the user. The `_install` method in `setup/components/mcp.py` was iterating through all available servers, not the user's selection. This has been fixed to respect the `selected_mcp_servers` configuration. A new test has been added to verify this fix. 2. **Backup Creation:** The `create_backup` method in `setup/core/installer.py` created an invalid `.tar.gz` file when the backup source was empty. This has been fixed to ensure that a valid, empty tar archive is always created. A test was added for this as well. Co-authored-by: Mithun Gowda B <mithungowda.b7411@gmail.com> Co-authored-by: Jules <jules-ai-assistant@users.noreply.github.com> * Fix: Correct installer validation for MCP and MCP Docs components This commit fixes a validation issue in the installer where it would incorrectly fail after a partial installation of MCP servers. The `MCPComponent` validation logic was checking for all "required" servers, regardless of whether they were selected by the user. This has been corrected to only validate the servers that were actually installed, by checking against the list of installed servers stored in the metadata. The metadata storage has also been fixed to only record the installed servers. The `MCPDocsComponent` was failing validation because it was not being registered in the metadata if no documentation files were installed. This has been fixed by ensuring the post-installation hook runs even when no files are copied. New tests have been added for both components to verify the corrected logic. Co-authored-by: Mithun Gowda B <mithungowda.b7411@gmail.com> Co-authored-by: Jules <jules-ai-assistant@users.noreply.github.com> * Fix: Allow re-installation of components and correct validation logic This commit fixes a bug that prevented new MCP servers from being installed on subsequent runs of the installer. It also fixes the validation logic that was causing failures after a partial installation. The key changes are: 1. A new `is_reinstallable` method has been added to the base `Component` class. This allows certain components (like the `mcp` component) to be re-run even if they are already marked as installed. 2. The installer logic has been updated to respect this new method. 3. The `MCPComponent` now correctly stores only the installed servers in the metadata. 4. The validation logic for `MCPComponent` and `MCPDocsComponent` has been corrected to prevent incorrect failures. New tests have been added to verify all aspects of the new logic. Co-authored-by: Mithun Gowda B <mithungowda.b7411@gmail.com> Co-authored-by: Jules <jules-ai-assistant@users.noreply.github.com> * feat: Display authors in UI header and update author info This commit implements the user's request to display author names and emails in the UI header of the installer. The key changes are: 1. The `__email__` field in `SuperClaude/__init__.py` has been updated to include both authors' emails. 2. The `display_header` function in `setup/utils/ui.py` has been modified to read the author and email information and display it. 3. A new test has been added to `tests/test_ui.py` to verify the new UI output. Co-authored-by: Mithun Gowda B <mithungowda.b7411@gmail.com> Co-authored-by: Jules <jules-ai-assistant@users.noreply.github.com> * feat: Version bump to 4.1.0 and various fixes This commit prepares the project for the v4.1.0 release. It includes a version bump across all relevant files and incorporates several bug fixes and feature enhancements from recent tasks. Key changes in this release: - **Version Bump**: The project version has been updated from 4.0.9 to 4.1.0 in all configuration files, documentation, and source code. - **Installer Fixes**: - Components can now be marked as `reinstallable`, allowing them to be re-run on subsequent installations. This fixes a bug where new MCP servers could not be added. - The validation logic for `mcp` and `mcp_docs` components has been corrected to avoid incorrect failures. - A bug in the backup creation process that created invalid empty archives has been fixed. - **UI Enhancements**: - Author names and emails are now displayed in the installer UI header. - **Metadata Updates**: - Mithun Gowda B has been added as an author. - **New Tests**: - Comprehensive tests have been added for the installer logic, MCP components, and UI changes to ensure correctness and prevent regressions. Co-authored-by: Mithun Gowda B <mithungowda.b7411@gmail.com> Co-authored-by: Jules <jules-ai-assistant@users.noreply.github.com> * fix: Resolve dependencies for partial installs and other fixes This commit addresses several issues, the main one being a dependency resolution failure during partial installations. Key changes: - **Dependency Resolution**: The installer now correctly resolves the full dependency tree when a user requests to install a subset of components. This fixes the "Unknown component: core" error. - **Component Re-installation**: A new `is_reinstallable` flag allows components like `mcp` to be re-run on subsequent installs, enabling the addition of new servers. - **Validation Logic**: The validation for `mcp` and `mcp_docs` has been corrected to avoid spurious failures. - **UI and Metadata**: Author information has been added to the UI header and source files. - **Version Bump**: The project version has been updated to 4.1.0. - **Tests**: New tests have been added to cover all the above changes. Co-authored-by: Mithun Gowda B <mithungowda.b7411@gmail.com> Co-authored-by: Jules <jules-ai-assistant@users.noreply.github.com> * fix: Installer fixes and version bump to 4.1.0 This commit includes a collection of fixes for the installer logic, UI enhancements, and a version bump to 4.1.0. Key changes: - **Dependency Resolution**: The installer now correctly resolves the full dependency tree for partial installations, fixing the "Unknown component: core" error. - **Component Re-installation**: A new `is_reinstallable` flag allows components like `mcp` to be re-run to add new servers. - **MCP Installation**: The non-interactive installation of the `mcp` component now correctly prompts the user to select servers. - **Validation Logic**: The post-installation validation logic has been corrected to only validate components from the current session and to use the correct list of installed servers. - **UI & Metadata**: Author information has been added to the UI and source files. - **Version Bump**: The project version has been updated from 4.0.9 to 4.1.0 across all files. - **Tests**: New tests have been added to cover all the bug fixes. Co-authored-by: Mithun Gowda B <mithungowda.b7411@gmail.com> Co-authored-by: Jules <jules-ai-assistant@users.noreply.github.com> * feat: Add --authors flag and multiple installer fixes This commit introduces the `--authors` flag to display author information and includes a collection of fixes for the installer logic. Key changes: - **New Feature**: Added an `--authors` flag that displays the names, emails, and GitHub usernames of the project authors. - **Dependency Resolution**: Fixed a critical bug where partial installations would fail due to unresolved dependencies. - **Component Re-installation**: Added a mechanism to allow components to be "reinstallable", fixing an issue that prevented adding new MCP servers on subsequent runs. - **MCP Installation**: The non-interactive installation of the `mcp` component now correctly prompts for server selection. - **Validation Logic**: Corrected the post-installation validation to prevent spurious errors. - **Version Bump**: The project version has been updated to 4.1.0. - **Metadata**: Author and GitHub information has been added to the source files. - **UI**: The installer header now displays author information. - **Tests**: Added new tests for all new features and bug fixes. Co-authored-by: Jules <jules-ai-assistant@users.noreply.github.com> --------- Co-authored-by: Mithun Gowda B <mithungowda.b7411@gmail.com> Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-authored-by: Jules <jules-ai-assistant@users.noreply.github.com>
SuperClaude Framework Reference Documentation
Navigation Hub: Structured learning paths and technical references for all skill levels.
Documentation Status: ✅ Status: Current - All content verified for accuracy and completeness.
How to Use This Reference Library
This documentation is organized for progressive learning with multiple entry points:
- 📱 Quick Reference: Jump to specific solutions for immediate needs
- 📚 Learning Paths: Structured progression from beginner to expert
- 🔍 Problem-Solving: Targeted troubleshooting and diagnostic guidance
- ⚡ Performance: Optimization patterns and advanced techniques
Verification Standards: All examples tested, commands validated, patterns proven in real-world usage.
Documentation Navigation Matrix
| Document | Purpose | Target Audience | Complexity | |
|---|---|---|---|---|
| basic-examples.md | Copy-paste ready commands and patterns | All users, quick reference | Basic | |
| examples-cookbook.md | Recipe collection hub and organization | All users, navigation | Reference | |
| common-issues.md | Essential troubleshooting and solutions | All users, problem-solving | Basic | As needed |
| mcp-server-guide.md | MCP server configuration and usage | Technical users, integration | Intermediate |
| advanced-patterns.md | Expert coordination and orchestration | Experienced users | Advanced | | | advanced-workflows.md | Complex multi-agent orchestration | Expert users | Advanced | | | integration-patterns.md | Framework and system integration | Architects, experts | Advanced | | | troubleshooting.md | Comprehensive diagnostic guide | All levels, deep debugging | Variable | As needed | | diagnostic-reference.md | Advanced debugging and analysis | Expert users, complex issues | Advanced | |
Recommended Learning Paths
New Users (Week 1 Foundation)
Goal: Establish confident SuperClaude usage with essential workflows
Day 1-2: ../Getting-Started/quick-start.md
↓ Foundation building and first commands
Day 3-4: basic-examples.md
↓ Practical application and pattern recognition
Day 5-7: common-issues.md
↓ Problem resolution and confidence building
Success Metrics: Can execute basic commands, manage sessions, resolve common issues independently.
Intermediate Users (Week 2-3 Enhancement)
Goal: Master coordination patterns and technical depth
Week 2: advanced-patterns.md
↓ Multi-agent coordination and orchestration mastery
Week 3: mcp-server-guide.md + advanced-workflows.md
↓ Performance excellence and technical configuration
Success Metrics: Can orchestrate complex workflows, optimize performance, configure MCP servers.
Expert Users (Advanced Mastery)
Goal: Complete framework mastery and complex system integration
Phase 1: advanced-workflows.md
↓ Complex orchestration and enterprise patterns
Phase 2: integration-patterns.md
↓ Framework integration and architectural mastery
Phase 3: diagnostic-reference.md
↓ Advanced debugging and system analysis
Success Metrics: Can design custom workflows, integrate with any framework, diagnose complex issues.
Problem-Solving Path (As Needed)
Goal: Immediate issue resolution and diagnostic guidance
Quick Issues: common-issues.md
↓ Common problems and immediate solutions
Complex Debugging: troubleshooting.md
↓ Comprehensive diagnostic approach
Advanced Analysis: diagnostic-reference.md
↓ Expert-level debugging and analysis
Command Quick Reference
Essential SuperClaude Commands
| Command Pattern | Purpose | Example |
|---|---|---|
/sc:load |
Restore session context | /sc:load project_name |
/sc:save |
Preserve session state | /sc:save "milestone checkpoint" |
--think |
Enable structured analysis | --think analyze performance bottlenecks |
--brainstorm |
Collaborative requirement discovery | --brainstorm new authentication system |
--task-manage |
Multi-step operation orchestration | --task-manage refactor user module |
Performance & Efficiency Flags
| Flag | Purpose | Best For |
|---|---|---|
--uc / --ultracompressed |
Token-efficient communication | Large operations, context pressure |
--orchestrate |
Optimize tool selection | Multi-tool operations, performance needs |
--loop |
Iterative improvement cycles | Code refinement, quality enhancement |
--validate |
Pre-execution risk assessment | Production environments, critical operations |
MCP Server Activation
| Flag | Server | Best For |
|---|---|---|
--c7 / --context7 |
Context7 | Official documentation, framework patterns |
--seq / --sequential |
Sequential | Complex analysis, debugging, system design |
--magic |
Magic | UI components, design systems, frontend work |
--morph / --morphllm |
Morphllm | Bulk transformations, pattern-based edits |
--serena |
Serena | Symbol operations, project memory, large codebases |
--play / --playwright |
Playwright | Browser testing, E2E scenarios, visual validation |
Framework Integration Quick Start
React/Next.js Projects
# Initialize with React patterns
--c7 --magic "implement Next.js authentication with TypeScript"
# Component development workflow
--magic --think "create responsive dashboard component"
Node.js/Express Backend
# API development with best practices
--c7 --seq "design RESTful API with Express and MongoDB"
# Performance optimization
--think --orchestrate "optimize database queries and caching"
Full-Stack Development
# Complete application workflow
--task-manage --all-mcp "build full-stack e-commerce platform"
# Integration testing
--play --seq "implement end-to-end testing strategy"
Problem-Solving Quick Reference
Immediate Issues
- Command not working: Check common-issues.md → Common SuperClaude Problems
- Session lost: Use
/sc:load→ See Session Management - Flag confusion: Check basic-examples.md → Flag Usage Examples
Development Blockers
- Performance slow: See Advanced Workflows → Performance Patterns
- Complex debugging: Use troubleshooting.md → Systematic Debugging
- Integration issues: Check integration-patterns.md → Framework Patterns
System-Level Issues
- Architecture problems: Use advanced-workflows.md → System Design
- Expert debugging: Apply diagnostic-reference.md → Advanced Analysis
- Custom workflow needs: Study advanced-patterns.md → Custom Orchestration advanced-patterns.md → Custom Orchestration
Documentation Health & Verification
Quality Assurance
- ✅ Commands Tested: All examples tested and functional
- ✅ Patterns Proven: Real-world usage validation in production environments
- ✅ Cross-References: Internal links verified and maintained
- ✅ Regular Updates: Documentation synchronized with framework evolution
Accuracy Standards
- Command Syntax: Verified against latest SuperClaude implementation
- Flag Behavior: Tested in multiple scenarios and environments
- MCP Integration: Confirmed compatibility with current MCP server versions
- Performance Claims: Benchmarked and measured in realistic conditions
Reporting Issues
Found outdated information or broken examples?
- Quick Fixes: Check common-issues.md first
- Documentation Bugs: Report via project issues with specific file and line
- Missing Patterns: Suggest additions with use case description
- Verification Requests: Request re-testing of specific examples
Expert Tips for Maximum Productivity
Daily Workflow Optimization
- Session Management: Always start with
/sc:load, end with/sc:save - Flag Combinations: Combine complementary flags:
--think --c7for documented analysis - Progressive Complexity: Start simple, add sophistication incrementally
- Tool Specialization: Match tools to tasks: Magic for UI, Sequential for analysis
Learning Acceleration
- Follow the Paths: Use recommended learning sequences for structured growth
- Practice Patterns: Repeat common workflows until they become intuitive
- Experiment Safely: Use feature branches and checkpoints for exploration
- Community Learning: Share discoveries and learn from others' approaches
Troubleshooting Mastery
- Systematic Approach: Always start with common-issues.md
- Evidence Gathering: Use
--thinkfor complex problem analysis - Root Cause Focus: Address underlying issues, not just symptoms
- Documentation First: Check official docs before experimental solutions
Advanced Resources & Integration
Framework-Specific Guides
- React/Next.js: See integration-patterns.md → React Integration
- Vue/Nuxt: See integration-patterns.md → Vue Ecosystem
- Node.js/Express: See integration-patterns.md → Backend Patterns
- Python/Django: See integration-patterns.md → Python Workflows
Specialized Workflows
- DevOps Integration: advanced-workflows.md → CI/CD Patterns
- Testing Strategies: advanced-patterns.md → Testing Orchestration
- Performance Engineering: Advanced Patterns → Complex Coordination
- Security Implementation: integration-patterns.md → Security Patterns
Community & Support
- Best Practices: Continuously updated based on community feedback
- Pattern Library: Growing collection of proven workflow patterns
- Expert Network: Connect with experienced SuperClaude practitioners
- Regular Updates: Documentation evolves with framework capabilities
Start Your Journey: New to SuperClaude? Begin with Quick Start Guide for immediate productivity gains.
Need Answers Now: Jump to basic-examples.md for copy-paste solutions.
Ready for Advanced: Explore advanced-patterns.md for expert-level orchestration.