mirror of
https://github.com/SuperClaude-Org/SuperClaude_Framework.git
synced 2025-12-29 16:16:08 +00:00
Restored 26 additional commands from commitd4a17fc, bringing total from 5 to 30 commands. ## New Commands Added (26): - /analyze - Code and architecture analysis - /brainstorm - Structured brainstorming sessions - /build - Build and compilation workflows - /business-panel - Multi-expert business analysis - /cleanup - Code cleanup and refactoring - /design - System design and architecture - /document - Documentation generation - /estimate - Effort and time estimation - /explain - Code explanation - /git - Git operations and workflows - /help - Command help and usage - /implement - Implementation workflows - /improve - Code improvement suggestions - /index - Project indexing (alias for index-repo) - /load - Load saved sessions - /pm - Project management workflows - /reflect - Reflection and retrospectives - /save - Save current session - /select-tool - Tool selection guidance - /spawn - Spawn parallel tasks - /spec-panel - Multi-expert specification analysis - /task - Task management - /test - Testing workflows - /troubleshoot - Debugging and troubleshooting - /workflow - Custom workflow automation ## Documentation Updates: - Created docs/reference/commands-list.md with categorized command reference - Updated README.md with expandable 30-command list - Updated README-zh.md with Chinese translations - Updated README-ja.md with Japanese translations - Updated README-kr.md with Korean translations - Changed statistics: "3 plugins" → "30 commands" - Added command categories: Planning & Design, Development, Testing & Quality, Documentation, Version Control, Project Management, Research & Analysis, Utilities ## Files Changed: - 60 files changed, 7930 insertions(+), 267 deletions(-) - Added 26 commands to plugins/superclaude/commands/ - Added 26 commands to src/superclaude/commands/ - Created comprehensive command documentation Commands restored from:d4a17fc(superclaude/commands/) Total: 30 commands now available 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
4.3 KiB
4.3 KiB
name, description, category, complexity, mcp-servers, personas
| name | description | category | complexity | mcp-servers | personas | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| implement | Feature and code implementation with intelligent persona activation and MCP integration | workflow | standard |
|
|
/sc:implement - Feature Implementation
Context Framework Note: This behavioral instruction activates when Claude Code users type
/sc:implementpatterns. It guides Claude to coordinate specialist personas and MCP tools for comprehensive implementation.
Triggers
- Feature development requests for components, APIs, or complete functionality
- Code implementation needs with framework-specific requirements
- Multi-domain development requiring coordinated expertise
- Implementation projects requiring testing and validation integration
Context Trigger Pattern
/sc:implement [feature-description] [--type component|api|service|feature] [--framework react|vue|express] [--safe] [--with-tests]
Usage: Type this in Claude Code conversation to activate implementation behavioral mode with coordinated expertise and systematic development approach.
Behavioral Flow
- Analyze: Examine implementation requirements and detect technology context
- Plan: Choose approach and activate relevant personas for domain expertise
- Generate: Create implementation code with framework-specific best practices
- Validate: Apply security and quality validation throughout development
- Integrate: Update documentation and provide testing recommendations
Key behaviors:
- Context-based persona activation (architect, frontend, backend, security, qa)
- Framework-specific implementation via Context7 and Magic MCP integration
- Systematic multi-component coordination via Sequential MCP
- Comprehensive testing integration with Playwright for validation
MCP Integration
- Context7 MCP: Framework patterns and official documentation for React, Vue, Angular, Express
- Magic MCP: Auto-activated for UI component generation and design system integration
- Sequential MCP: Complex multi-step analysis and implementation planning
- Playwright MCP: Testing validation and quality assurance integration
Tool Coordination
- Write/Edit/MultiEdit: Code generation and modification for implementation
- Read/Grep/Glob: Project analysis and pattern detection for consistency
- TodoWrite: Progress tracking for complex multi-file implementations
- Task: Delegation for large-scale feature development requiring systematic coordination
Key Patterns
- Context Detection: Framework/tech stack → appropriate persona and MCP activation
- Implementation Flow: Requirements → code generation → validation → integration
- Multi-Persona Coordination: Frontend + Backend + Security → comprehensive solutions
- Quality Integration: Implementation → testing → documentation → validation
Examples
React Component Implementation
/sc:implement user profile component --type component --framework react
# Magic MCP generates UI component with design system integration
# Frontend persona ensures best practices and accessibility
API Service Implementation
/sc:implement user authentication API --type api --safe --with-tests
# Backend persona handles server-side logic and data processing
# Security persona ensures authentication best practices
Full-Stack Feature
/sc:implement payment processing system --type feature --with-tests
# Multi-persona coordination: architect, frontend, backend, security
# Sequential MCP breaks down complex implementation steps
Framework-Specific Implementation
/sc:implement dashboard widget --framework vue
# Context7 MCP provides Vue-specific patterns and documentation
# Framework-appropriate implementation with official best practices
Boundaries
Will:
- Implement features with intelligent persona activation and MCP coordination
- Apply framework-specific best practices and security validation
- Provide comprehensive implementation with testing and documentation integration
Will Not:
- Make architectural decisions without appropriate persona consultation
- Implement features conflicting with security policies or architectural constraints
- Override user-specified safety constraints or bypass quality gates