diff --git a/Docs/Developer-Guide/README.md b/Docs/Developer-Guide/README.md index 75c6f10..47532ac 100644 --- a/Docs/Developer-Guide/README.md +++ b/Docs/Developer-Guide/README.md @@ -51,7 +51,7 @@ SuperClaude is a collection of `.md` instruction files that Claude Code reads to **IMPORTANT**: SuperClaude is NOT a CLI tool or executable software. When you see `/sc:` commands in documentation, these are **context trigger patterns** you type in Claude Code conversations, not terminal commands. ### Agent Context Files -Specialized instruction sets that provide domain expertise when activated by `@agents-[name]` or automatically by keywords. +Specialized instruction sets that provide domain expertise when activated by `@agent-[name]` or automatically by keywords. ### Command Context Files Workflow patterns triggered by `/sc:[command]` **context patterns** (not CLI commands) that guide Claude Code through structured development tasks when you type them in Claude Code conversations. diff --git a/Docs/Developer-Guide/technical-architecture.md b/Docs/Developer-Guide/technical-architecture.md index 8ae4053..70fa9f6 100644 --- a/Docs/Developer-Guide/technical-architecture.md +++ b/Docs/Developer-Guide/technical-architecture.md @@ -50,7 +50,7 @@ This guide documents how SuperClaude's Context-Oriented Configuration Framework | File Type | Purpose | Activation | Example | |-----------|---------|------------|---------| | **Commands** | Define workflow patterns | `/sc:[command]` (context trigger) | User types `/sc:implement` → reads `implement.md` | -| **Agents** | Provide domain expertise | `@agents-[name]` or auto | `@agents-security` → reads `security-engineer.md` | +| **Agents** | Provide domain expertise | `@agent-[name]` or auto | `@agent-security` → reads `security-engineer.md` | | **Modes** | Modify interaction style | Flags or triggers | `--brainstorm` → activates brainstorming mode | | **Core** | Set fundamental rules | Always active | `RULES.md` always loaded | @@ -113,7 +113,7 @@ Core philosophy and approach ### Agent Activation Logic -- **Manual**: User types `@agents-python-expert "task"` +- **Manual**: User types `@agent-python-expert "task"` - **Automatic**: Keywords in request trigger agent loading - **Contextual**: File types or patterns activate relevant agents @@ -231,7 +231,7 @@ User Input (in Claude Code): "/sc:analyze src/ --focus security" ### Context Priority 1. **Explicit Commands**: `/sc:` commands take precedence -2. **Manual Agents**: `@agents-` override auto-activation +2. **Manual Agents**: `@agent-` override auto-activation 3. **Flags**: Modify behavior of commands/agents 4. **Auto-Activation**: Based on keywords/context 5. **Default Behavior**: Standard Claude Code diff --git a/Docs/Developer-Guide/testing-debugging.md b/Docs/Developer-Guide/testing-debugging.md index ab46282..7b97060 100644 --- a/Docs/Developer-Guide/testing-debugging.md +++ b/Docs/Developer-Guide/testing-debugging.md @@ -164,7 +164,7 @@ PYTHONPATH=/path/to/SuperClaude_Framework python3 -m setup install --components ### Issue: Agents Not Activating -**Symptom**: `@agents-` invocations don't work in Claude Code +**Symptom**: `@agent-` invocations don't work in Claude Code **Verification**: ```bash diff --git a/Docs/Getting-Started/installation.md b/Docs/Getting-Started/installation.md index 97e5906..a6cd1b1 100644 --- a/Docs/Getting-Started/installation.md +++ b/Docs/Getting-Started/installation.md @@ -30,7 +30,7 @@ SuperClaude install --dry-run |------|------------|--------|----------| | **Installation** | Terminal | `SuperClaude [command]` | `SuperClaude install` | | **Slash Commands** | Claude Code | `/sc:[command]` | `/sc:brainstorm "idea"` | -| **Agents** | Claude Code | `@agents-[type]` | `@agents-security "review"` | +| **Agents** | Claude Code | `@agent-[type]` | `@agent-security "review"` | ## Requirements @@ -116,7 +116,7 @@ SuperClaude install --list-components **What's Installed:** - Framework files in `~/.claude/` - 21 slash commands (`/sc:*`) -- 15 agents (`@agents-*`) +- 15 agents (`@agent-*`) - 6 behavioral modes - MCP server configurations (if selected) diff --git a/Docs/Getting-Started/quick-start.md b/Docs/Getting-Started/quick-start.md index 43c0836..41cd03f 100644 --- a/Docs/Getting-Started/quick-start.md +++ b/Docs/Getting-Started/quick-start.md @@ -27,7 +27,7 @@ pip install SuperClaude && SuperClaude install /sc:workflow "add user authentication" # Invoke specialist persona -@agents-security "review authentication implementation" +@agent-security "review authentication implementation" ``` **What Happens with Context Framework:** @@ -52,7 +52,7 @@ pip install SuperClaude && SuperClaude install SuperClaude enhances Claude Code with: **21 Slash Commands** for workflow automation (/sc:brainstorm, /sc:implement, /sc:analyze) -**13 AI Specialists** with domain expertise (@agents-architect, @agents-security, @agents-frontend) +**13 AI Specialists** with domain expertise (@agent-architect, @agent-security, @agent-frontend) **6 Behavioral Modes** for different contexts (brainstorming, introspection, orchestration) **6 MCP Servers** for enhanced capabilities (Context7, Sequential, Magic, Playwright) @@ -70,7 +70,7 @@ You type `/sc:implement "user login"` → Claude reads context from `implement.m **Technical Architecture:** 1. **Context Loading** (Claude Code imports behavioral .md files via CLAUDE.md) -2. **Pattern Recognition** (Recognizes /sc: and @agents- trigger patterns) +2. **Pattern Recognition** (Recognizes /sc: and @agent- trigger patterns) 3. **Behavioral Activation** (Applies corresponding behavioral instructions from context files) 4. **MCP Integration** (Uses configured external tools when available) 5. **Response Enhancement** (Follows framework patterns for comprehensive responses) @@ -155,7 +155,7 @@ SuperClaude transforms Claude Code from a general-purpose AI assistant into a ** - Need systematic workflows and quality gates - Working on complex, multi-component systems - Require session persistence across development cycles -- Want specialized domain expertise (invoke with @agents-[specialist] or auto-activation) +- Want specialized domain expertise (invoke with @agent-[specialist] or auto-activation) **Use Standard Claude Code When:** - Simple questions or explanations diff --git a/Docs/README.md b/Docs/README.md index 19536e5..acdda36 100644 --- a/Docs/README.md +++ b/Docs/README.md @@ -33,7 +33,7 @@ pip install SuperClaude && SuperClaude install | Guide | Purpose | Use For | |-------|---------|---------| | **[Commands Guide](User-Guide/commands.md)** | Master all `/sc:` commands | Daily development | -| **[Agents Guide](User-Guide/agents.md)** | 15 domain specialists (`@agents-*`) | Expert assistance | +| **[Agents Guide](User-Guide/agents.md)** | 15 domain specialists (`@agent-*`) | Expert assistance | | **[Flags Guide](User-Guide/flags.md)** | Command behavior modification | Optimization | | **[Modes Guide](User-Guide/modes.md)** | 6 behavioral modes | Workflow optimization | @@ -59,7 +59,7 @@ pip install SuperClaude && SuperClaude install ### Framework Components - **21 Commands** (`/sc:*`) - Workflow automation patterns -- **15 Agents** (`@agents-*`) - Domain specialists +- **15 Agents** (`@agent-*`) - Domain specialists - **6 Modes** - Behavioral modification patterns - **6 MCP Servers** - Optional external tools @@ -78,8 +78,8 @@ python3 -m SuperClaude --version # Check installation /sc:brainstorm "project idea" # Start new project /sc:implement "feature" # Build features /sc:analyze src/ # Analyze code -@agents-python-expert "optimize this" # Manual specialist -@agents-security "review authentication" # Security review +@agent-python-expert "optimize this" # Manual specialist +@agent-security "review authentication" # Security review ``` ## 📊 Framework vs Software Comparison diff --git a/Docs/Reference/advanced-patterns.md b/Docs/Reference/advanced-patterns.md index 628eec4..e9d81f7 100644 --- a/Docs/Reference/advanced-patterns.md +++ b/Docs/Reference/advanced-patterns.md @@ -23,8 +23,8 @@ **Security + Backend Pattern:** ```bash # Security-focused backend development -@agents-security "define authentication requirements" -@agents-backend-architect "design API with security requirements" +@agent-security "define authentication requirements" +@agent-backend-architect "design API with security requirements" /sc:implement "secure API endpoints" # What happens: @@ -37,9 +37,9 @@ **Frontend + UX + Accessibility Pattern:** ```bash # Comprehensive frontend development -@agents-frontend-architect "design component architecture" +@agent-frontend-architect "design component architecture" /sc:implement "accessible React components" --magic -@agents-quality-engineer "review accessibility compliance" +@agent-quality-engineer "review accessibility compliance" # Context layering: # - Frontend patterns guide structure @@ -52,7 +52,7 @@ **Explicit Control Pattern:** ```bash # Manually control which contexts load -@agents-python-expert "implement data pipeline" +@agent-python-expert "implement data pipeline" # Only Python context, no auto-activation # vs Automatic selection @@ -64,7 +64,7 @@ ```bash # Prevent unwanted agent activation /sc:implement "simple utility" --no-mcp -@agents-backend-architect "keep it simple" +@agent-backend-architect "keep it simple" # Limits context to specified agent only ``` @@ -96,7 +96,7 @@ /sc:design "feature architecture" # Creates structure -@agents-backend-architect "review design" +@agent-backend-architect "review design" # Expert review /sc:implement "feature based on design" @@ -116,7 +116,7 @@ /sc:improve code/ --fix # First improvement pass -@agents-refactoring-expert "suggest further improvements" +@agent-refactoring-expert "suggest further improvements" # Expert suggestions /sc:improve code/ --fix --focus maintainability @@ -172,7 +172,7 @@ /sc:analyze . --quick --focus architecture # Step 2: Identify problem areas -@agents-quality-engineer "identify high-risk modules" +@agent-quality-engineer "identify high-risk modules" # Step 3: Deep dive into specific areas /sc:analyze high-risk-module/ --think-hard --focus quality @@ -187,11 +187,11 @@ # Developing interconnected modules # Frontend module /sc:implement "user interface module" -@agents-frontend-architect "ensure consistency" +@agent-frontend-architect "ensure consistency" # Backend module /sc:implement "API module" -@agents-backend-architect "ensure compatibility" +@agent-backend-architect "ensure compatibility" # Integration layer /sc:implement "frontend-backend integration" @@ -203,13 +203,13 @@ ```bash # Projects with multiple technologies # Python backend -@agents-python-expert "implement FastAPI backend" +@agent-python-expert "implement FastAPI backend" # React frontend -@agents-frontend-architect "implement React frontend" +@agent-frontend-architect "implement React frontend" # DevOps setup -@agents-devops-architect "create deployment configuration" +@agent-devops-architect "create deployment configuration" # Integration documentation /sc:document --type integration @@ -224,8 +224,8 @@ /sc:load legacy-system/ /sc:analyze . --focus architecture --verbose -@agents-refactoring-expert "identify modernization opportunities" -@agents-system-architect "propose migration strategy" +@agent-refactoring-expert "identify modernization opportunities" +@agent-system-architect "propose migration strategy" /sc:workflow "create migration plan" ``` @@ -238,7 +238,7 @@ /sc:analyze legacy-module/ --comprehensive # Phase 2: Design new architecture -@agents-system-architect "design modern replacement" +@agent-system-architect "design modern replacement" # Phase 3: Implementation /sc:implement "modern module with compatibility layer" @@ -254,8 +254,8 @@ ```bash # Comprehensive security review /sc:analyze . --focus security --think-hard -@agents-security "review authentication and authorization" -@agents-security "check for OWASP vulnerabilities" +@agent-security "review authentication and authorization" +@agent-security "check for OWASP vulnerabilities" /sc:document --type security-audit ``` @@ -264,8 +264,8 @@ ```bash # Multi-aspect quality review /sc:analyze src/ --focus quality -@agents-quality-engineer "review test coverage" -@agents-refactoring-expert "identify code smells" +@agent-quality-engineer "review test coverage" +@agent-refactoring-expert "identify code smells" /sc:improve --fix --preview ``` @@ -273,9 +273,9 @@ ```bash # System architecture assessment -@agents-system-architect "review current architecture" +@agent-system-architect "review current architecture" /sc:analyze . --focus architecture --think-hard -@agents-performance-engineer "identify bottlenecks" +@agent-performance-engineer "identify bottlenecks" /sc:design "optimization recommendations" ``` diff --git a/Docs/Reference/advanced-workflows.md b/Docs/Reference/advanced-workflows.md index b06e898..cd333ca 100644 --- a/Docs/Reference/advanced-workflows.md +++ b/Docs/Reference/advanced-workflows.md @@ -23,17 +23,17 @@ ```bash # E-commerce platform using multiple contexts # Step 1: Architecture context -@agents-system-architect "design e-commerce architecture" +@agent-system-architect "design e-commerce architecture" # Step 2: Security requirements -@agents-security "define security requirements for payments" +@agent-security "define security requirements for payments" # Step 3: Backend implementation /sc:implement "API with authentication and payment processing" # Claude uses accumulated context from previous steps # Step 4: Frontend implementation -@agents-frontend-architect "design responsive UI" +@agent-frontend-architect "design responsive UI" /sc:implement "React frontend with TypeScript" # Step 5: Review @@ -51,8 +51,8 @@ /sc:troubleshoot "application performance issues" # Step 2: Expert analysis -@agents-performance-engineer "analyze potential bottlenecks" -@agents-backend-architect "review architecture for issues" +@agent-performance-engineer "analyze potential bottlenecks" +@agent-backend-architect "review architecture for issues" # Step 3: Solution design /sc:design "performance improvement plan" @@ -75,7 +75,7 @@ # Planning phase /sc:design "system architecture" -@agents-system-architect "review and refine" +@agent-system-architect "review and refine" # Documentation /sc:document --type architecture @@ -98,7 +98,7 @@ # Feature 3: Admin Dashboard (uses previous context) /sc:implement "admin dashboard" -@agents-frontend-architect "ensure consistency" +@agent-frontend-architect "ensure consistency" # Each feature builds on conversation context ``` @@ -113,7 +113,7 @@ # Claude builds understanding # Phase 2: Planning -@agents-system-architect "design migration strategy" +@agent-system-architect "design migration strategy" /sc:workflow "create migration plan" # Phase 3: Implementation @@ -143,7 +143,7 @@ /sc:analyze frontend/ --focus performance # Synthesis -@agents-system-architect "synthesize findings" +@agent-system-architect "synthesize findings" /sc:workflow "improvement recommendations" # Note: Sequential analysis, not parallel @@ -154,18 +154,18 @@ ```bash # Projects with diverse tech stacks # Backend (Python) -@agents-python-expert "implement FastAPI backend" +@agent-python-expert "implement FastAPI backend" /sc:implement "Python API with async support" # Frontend (React) -@agents-frontend-architect "implement React frontend" +@agent-frontend-architect "implement React frontend" /sc:implement "TypeScript React application" # Mobile (React Native) /sc:implement "React Native mobile app" # Infrastructure -@agents-devops-architect "design deployment" +@agent-devops-architect "design deployment" /sc:implement "Docker configuration" # Each technology addressed sequentially @@ -179,17 +179,17 @@ # Multi-aspect code review # Quality review /sc:analyze . --focus quality -@agents-quality-engineer "identify improvements" +@agent-quality-engineer "identify improvements" # Security review /sc:analyze . --focus security -@agents-security "check for vulnerabilities" +@agent-security "check for vulnerabilities" # Architecture review -@agents-system-architect "evaluate design" +@agent-system-architect "evaluate design" # Performance review -@agents-performance-engineer "suggest optimizations" +@agent-performance-engineer "suggest optimizations" # Consolidated improvements /sc:improve . --fix @@ -301,7 +301,7 @@ 1. **Strategic Activation**: Use agents for specific expertise 2. **Avoid Overload**: Too many agents can dilute focus -3. **Manual Control**: Use `@agents-` for precise control +3. **Manual Control**: Use `@agent-` for precise control 4. **Context Layering**: Add agents in logical order ## Summary diff --git a/Docs/Reference/basic-examples.md b/Docs/Reference/basic-examples.md index 6964524..65fa218 100644 --- a/Docs/Reference/basic-examples.md +++ b/Docs/Reference/basic-examples.md @@ -4,7 +4,7 @@ **Quick Reference Guide**: Copy-paste ready examples for beginners, focused on essential SuperClaude usage patterns and fundamental development workflows. -> **📝 Context Note**: These examples show `/sc:` commands and `@agents-` invocations that trigger Claude Code to read specific context files and adopt the behaviors defined there. The sophistication comes from the behavioral instructions, not from executable software. +> **📝 Context Note**: These examples show `/sc:` commands and `@agent-` invocations that trigger Claude Code to read specific context files and adopt the behaviors defined there. The sophistication comes from the behavioral instructions, not from executable software. ## Overview and Usage Guide @@ -116,31 +116,31 @@ ### Direct Specialist Activation -#### Pattern: @agents-[specialist] +#### Pattern: @agent-[specialist] **Purpose**: Manually invoke specific domain experts instead of auto-activation -**Syntax**: `@agents-[specialist] "task or question"` +**Syntax**: `@agent-[specialist] "task or question"` #### Python Expert ```bash -@agents-python-expert "optimize this data processing pipeline for performance" +@agent-python-expert "optimize this data processing pipeline for performance" # Expected: Python-specific optimizations, async patterns, memory management ``` #### Security Engineer ```bash -@agents-security "review this authentication system for vulnerabilities" +@agent-security "review this authentication system for vulnerabilities" # Expected: OWASP compliance check, vulnerability assessment, secure coding recommendations ``` #### Frontend Architect ```bash -@agents-frontend-architect "design a responsive component architecture" +@agent-frontend-architect "design a responsive component architecture" # Expected: Component patterns, state management, accessibility considerations ``` #### Quality Engineer ```bash -@agents-quality-engineer "create comprehensive test coverage for payment module" +@agent-quality-engineer "create comprehensive test coverage for payment module" # Expected: Test strategy, unit/integration/e2e tests, edge cases ``` @@ -153,27 +153,27 @@ # Auto-activates: backend-architect, possibly frontend # Step 2: Add specific expert review -@agents-security "review the profile system for data privacy compliance" +@agent-security "review the profile system for data privacy compliance" # Manual activation for targeted review # Step 3: Performance optimization -@agents-performance-engineer "optimize database queries for profile fetching" +@agent-performance-engineer "optimize database queries for profile fetching" # Manual activation for specific optimization ``` #### Pattern: Sequential Specialist Chain ```bash # Design phase -@agents-system-architect "design microservices architecture for e-commerce" +@agent-system-architect "design microservices architecture for e-commerce" # Security review -@agents-security "review architecture for security boundaries" +@agent-security "review architecture for security boundaries" # Implementation guidance -@agents-backend-architect "implement service communication patterns" +@agent-backend-architect "implement service communication patterns" # DevOps setup -@agents-devops-architect "configure CI/CD for microservices" +@agent-devops-architect "configure CI/CD for microservices" ``` ## Basic Usage Patterns @@ -397,38 +397,38 @@ ```bash # New React project with TypeScript /sc:implement "React TypeScript project with routing, state management, and testing setup" -@agents-frontend-architect "review and optimize the project structure" +@agent-frontend-architect "review and optimize the project structure" # New Node.js API server /sc:implement "Express.js REST API with JWT authentication and PostgreSQL integration" -@agents-backend-architect "ensure scalability and best practices" +@agent-backend-architect "ensure scalability and best practices" # Python web API /sc:implement "FastAPI application with async PostgreSQL and authentication middleware" -@agents-python-expert "optimize async patterns and dependency injection" +@agent-python-expert "optimize async patterns and dependency injection" # Next.js full-stack app /sc:implement "Next.js 14 application with App Router, TypeScript, and Tailwind CSS" -@agents-system-architect "design optimal data fetching strategy" +@agent-system-architect "design optimal data fetching strategy" ``` ### Quick Quality Improvements ```bash # Code quality enhancement /sc:analyze . --focus quality && /sc:implement "code quality improvements" -@agents-quality-engineer "create quality metrics dashboard" +@agent-quality-engineer "create quality metrics dashboard" # Security hardening /sc:analyze . --focus security && /sc:implement "security improvements" -@agents-security "perform OWASP Top 10 compliance check" +@agent-security "perform OWASP Top 10 compliance check" # Performance optimization /sc:analyze . --focus performance && /sc:implement "performance optimizations" -@agents-performance-engineer "profile and optimize critical paths" +@agent-performance-engineer "profile and optimize critical paths" # Test coverage improvement /sc:test --focus quality && /sc:implement "additional test coverage" -@agents-quality-engineer "identify untested edge cases" +@agent-quality-engineer "identify untested edge cases" ``` ### Common Feature Implementations diff --git a/Docs/Reference/integration-patterns.md b/Docs/Reference/integration-patterns.md index 5d55000..32fe89e 100644 --- a/Docs/Reference/integration-patterns.md +++ b/Docs/Reference/integration-patterns.md @@ -29,7 +29,7 @@ # 3. Claude generates React code based on these contexts # Component development pattern -@agents-frontend-architect "design component architecture" +@agent-frontend-architect "design component architecture" /sc:implement "reusable component library" # Testing pattern for React @@ -51,7 +51,7 @@ # Database integration pattern /sc:implement "database models with Prisma" -@agents-backend-architect "review database schema" +@agent-backend-architect "review database schema" # API testing pattern /sc:test --focus api @@ -63,7 +63,7 @@ ```bash # Python web development /sc:implement "FastAPI application" --c7 -@agents-python-expert "review implementation" +@agent-python-expert "review implementation" # What Happens: # - Claude uses Python-specific context @@ -72,7 +72,7 @@ # Data science context /sc:implement "data analysis pipeline" -@agents-python-expert "optimize pandas operations" +@agent-python-expert "optimize pandas operations" # Claude provides optimization suggestions (not actual optimization) # Testing patterns @@ -85,15 +85,15 @@ ```bash # Full-stack application pattern /sc:brainstorm "full-stack application architecture" -@agents-system-architect "design system components" +@agent-system-architect "design system components" # Frontend implementation /sc:implement "React frontend with TypeScript" -@agents-frontend-architect "review component structure" +@agent-frontend-architect "review component structure" # Backend implementation /sc:implement "Node.js API with authentication" -@agents-backend-architect "review API design" +@agent-backend-architect "review API design" # Integration /sc:implement "connect frontend to backend API" @@ -125,17 +125,17 @@ ```bash # Security-focused development -@agents-security "review authentication requirements" +@agent-security "review authentication requirements" /sc:implement "secure authentication system" /sc:analyze --focus security # Quality-focused workflow /sc:implement "new feature" -@agents-quality-engineer "review code quality" +@agent-quality-engineer "review code quality" /sc:test --focus quality # Architecture-focused approach -@agents-system-architect "design microservices" +@agent-system-architect "design microservices" /sc:design "service boundaries" /sc:implement "service communication" ``` @@ -162,7 +162,7 @@ ```bash # Schema design -@agents-backend-architect "design database schema" +@agent-backend-architect "design database schema" # Model implementation /sc:implement "database models" @@ -171,7 +171,7 @@ /sc:implement "database migrations" # Query optimization suggestions -@agents-backend-architect "suggest query optimizations" +@agent-backend-architect "suggest query optimizations" # Note: Claude suggests optimizations, doesn't actually optimize ``` @@ -204,7 +204,7 @@ /sc:implement "TypeScript React components with props validation" # State management -@agents-frontend-architect "recommend state management approach" +@agent-frontend-architect "recommend state management approach" /sc:implement "state management with Zustand/Redux" # Testing @@ -218,7 +218,7 @@ /sc:implement "FastAPI project structure" # Endpoint development -@agents-python-expert "implement async endpoints" +@agent-python-expert "implement async endpoints" # Database integration /sc:implement "SQLAlchemy models with Alembic" @@ -231,7 +231,7 @@ ```bash # Architecture design -@agents-system-architect "design microservices architecture" +@agent-system-architect "design microservices architecture" # Service implementation /sc:implement "user service with Express" @@ -253,7 +253,7 @@ /sc:troubleshoot "describe the issue" # Root cause investigation -@agents-root-cause-analyst "analyze symptoms" +@agent-root-cause-analyst "analyze symptoms" # Solution implementation /sc:implement "fix based on analysis" @@ -269,10 +269,10 @@ /sc:analyze code/ --focus quality # Security review -@agents-security "review for vulnerabilities" +@agent-security "review for vulnerabilities" # Performance review -@agents-performance-engineer "suggest improvements" +@agent-performance-engineer "suggest improvements" # Note: Suggestions only, no actual performance measurement # Implementation of improvements @@ -310,7 +310,7 @@ - **Simple tasks**: Use basic commands without MCP - **Complex tasks**: Add appropriate agents and MCP servers -- **Security-critical**: Always include `@agents-security` +- **Security-critical**: Always include `@agent-security` - **UI development**: Consider `--magic` flag if configured - **Documentation needs**: Use `--c7` for framework docs diff --git a/Docs/Reference/troubleshooting.md b/Docs/Reference/troubleshooting.md index b1a0485..157fbd3 100644 --- a/Docs/Reference/troubleshooting.md +++ b/Docs/Reference/troubleshooting.md @@ -54,7 +54,7 @@ python3 -m SuperClaude install --components core commands agents modes --force **Agents Not Activating:** - Use specific keywords: `/sc:implement "secure JWT authentication"` -- Manual activation: `@agents-security "review auth code"` +- Manual activation: `@agent-security "review auth code"` **Slow Performance:** ```bash diff --git a/Docs/User-Guide/agents.md b/Docs/User-Guide/agents.md index 55f0258..b71d01f 100644 --- a/Docs/User-Guide/agents.md +++ b/Docs/User-Guide/agents.md @@ -12,7 +12,7 @@ Before using this guide, verify agent selection works: ```bash # Test manual agent invocation -@agents-python-expert "explain decorators" +@agent-python-expert "explain decorators" # Example behavior: Python expert responds with detailed explanation # Test security agent auto-activation @@ -29,7 +29,7 @@ Before using this guide, verify agent selection works: # Test combining manual and auto /sc:analyze src/ -@agents-refactoring-expert "suggest improvements" +@agent-refactoring-expert "suggest improvements" # Example behavior: Analysis followed by refactoring suggestions ``` @@ -44,12 +44,12 @@ Before using this guide, verify agent selection works: ### Two Ways to Use Agents -#### 1. Manual Invocation with @agents- Prefix +#### 1. Manual Invocation with @agent- Prefix ```bash # Directly invoke a specific agent -@agents-security "review authentication implementation" -@agents-frontend "design responsive navigation" -@agents-architect "plan microservices migration" +@agent-security "review authentication implementation" +@agent-frontend "design responsive navigation" +@agent-architect "plan microservices migration" ``` #### 2. Auto-Activation (Behavioral Routing) @@ -75,7 +75,7 @@ Before using this guide, verify agent selection works: ### Agent Selection Rules **Priority Hierarchy:** -1. **Manual Override** - @agents-[name] takes precedence over auto-activation +1. **Manual Override** - @agent-[name] takes precedence over auto-activation 2. **Keywords** - Direct domain terminology triggers primary agents 3. **File Types** - Extensions activate language/framework specialists 4. **Complexity** - Multi-step tasks engage coordination agents @@ -91,7 +91,7 @@ Before using this guide, verify agent selection works: **Selection Decision Tree:** ``` Task Analysis → -├─ Manual @agents-? → Use specified agent +├─ Manual @agent-? → Use specified agent ├─ Single Domain? → Activate primary agent ├─ Multi-Domain? → Coordinate specialist agents ├─ Complex System? → Add system-architect oversight @@ -103,11 +103,11 @@ Task Analysis → ### Manual Agent Invocation ```bash -# Explicitly call specific agents with @agents- prefix -@agents-python-expert "optimize this data processing pipeline" -@agents-quality-engineer "create comprehensive test suite" -@agents-technical-writer "document this API with examples" -@agents-socratic-mentor "explain this design pattern" +# Explicitly call specific agents with @agent- prefix +@agent-python-expert "optimize this data processing pipeline" +@agent-quality-engineer "create comprehensive test suite" +@agent-technical-writer "document this API with examples" +@agent-socratic-mentor "explain this design pattern" ``` ### Automatic Agent Coordination @@ -132,8 +132,8 @@ Task Analysis → /sc:implement "user profile system" # Then explicitly add specialist review -@agents-security "review the profile system for OWASP compliance" -@agents-performance-engineer "optimize database queries" +@agent-security "review the profile system for OWASP compliance" +@agent-performance-engineer "optimize database queries" ``` --- diff --git a/Docs/User-Guide/commands.md b/Docs/User-Guide/commands.md index 64351fe..ea01f29 100644 --- a/Docs/User-Guide/commands.md +++ b/Docs/User-Guide/commands.md @@ -1,13 +1,13 @@ # SuperClaude Commands Guide -SuperClaude provides 21 commands for Claude Code: `/sc:*` commands for workflows and `@agents-*` for specialists. +SuperClaude provides 21 commands for Claude Code: `/sc:*` commands for workflows and `@agent-*` for specialists. ## Command Types | Type | Where Used | Format | Example | |------|------------|--------|---------| | **Slash Commands** | Claude Code | `/sc:[command]` | `/sc:implement "feature"` | -| **Agents** | Claude Code | `@agents-[name]` | `@agents-security "review"` | +| **Agents** | Claude Code | `@agent-[name]` | `@agent-security "review"` | | **Installation** | Terminal | `SuperClaude [command]` | `SuperClaude install` | ## Quick Test @@ -33,7 +33,7 @@ SuperClaude provides behavioral context files that Claude Code reads to adopt sp ### Command Types: - **Slash Commands** (`/sc:*`): Trigger workflow patterns and behavioral modes -- **Agent Invocations** (`@agents-*`): Manually activate specific domain specialists +- **Agent Invocations** (`@agent-*`): Manually activate specific domain specialists - **Flags** (`--think`, `--safe-mode`): Modify command behavior and depth ### The Context Mechanism: @@ -55,7 +55,7 @@ SuperClaude provides behavioral context files that Claude Code reads to adopt sp **💬 Claude Code Commands** (Context triggers): - `/sc:brainstorm` - Activates requirements discovery context - `/sc:implement` - Activates feature development context -- `@agents-security` - Activates security specialist context +- `@agent-security` - Activates security specialist context - All commands work inside Claude Code chat interface only ## ✅ Verification Status @@ -103,10 +103,10 @@ SuperClaude install --list-components | grep mcp | **🖥️ Installation** | Terminal/CMD | `SuperClaude [command]` | Setup and maintenance | `SuperClaude install` | | **🔧 Configuration** | Terminal/CMD | `python3 -m SuperClaude [command]` | Advanced configuration | `python3 -m SuperClaude --version` | | **💬 Slash Commands** | Claude Code | `/sc:[command]` | Workflow automation | `/sc:implement "feature"` | -| **🤖 Agent Invocation** | Claude Code | `@agents-[name]` | Manual specialist activation | `@agents-security "review"` | +| **🤖 Agent Invocation** | Claude Code | `@agent-[name]` | Manual specialist activation | `@agent-security "review"` | | **⚡ Enhanced Flags** | Claude Code | `/sc:[command] --flags` | Behavior modification | `/sc:analyze --think-hard` | -> **Remember**: All `/sc:` commands and `@agents-` invocations work inside Claude Code chat, not your terminal. They trigger Claude Code to read specific context files from the SuperClaude framework. +> **Remember**: All `/sc:` commands and `@agent-` invocations work inside Claude Code chat, not your terminal. They trigger Claude Code to read specific context files from the SuperClaude framework. ## Table of Contents diff --git a/SuperClaude/Agents/security-engineer.md b/SuperClaude/Agents/security-engineer.md index 2f13b8d..468f290 100644 --- a/SuperClaude/Agents/security-engineer.md +++ b/SuperClaude/Agents/security-engineer.md @@ -7,7 +7,7 @@ tools: Read, Grep, Glob, Bash, Write # Security Engineer -> **Context Framework Note**: This agent persona is activated when Claude Code users type `@agents-security` patterns or when security contexts are detected. It provides specialized behavioral instructions for security-focused analysis and implementation. +> **Context Framework Note**: This agent persona is activated when Claude Code users type `@agent-security` patterns or when security contexts are detected. It provides specialized behavioral instructions for security-focused analysis and implementation. ## Triggers - Security vulnerability assessment and code audit requests