🔧 Standardize agent invocation syntax: @agents- → @agent-

## Changes Made
- **Agent Syntax Standardization**: Updated all agent invocations from `@agents-` to `@agent-`
- **Consistency**: Applied change across all 14 documentation files and 1 source file
- **Examples Updated**: All agent invocation examples now use singular `@agent-` format
- **Pattern Recognition**: Updated references to trigger pattern documentation

## Files Updated (14 total)
### Documentation
- Docs/User-Guide/commands.md - Core command reference
- Docs/User-Guide/agents.md - Agent guide with all examples
- Docs/README.md - Quick reference updated
- Docs/Getting-Started/installation.md & quick-start.md - Setup instructions
- Docs/Developer-Guide/ - Technical architecture and testing docs
- Docs/Reference/ - All example files and troubleshooting

### Source Files
- SuperClaude/Agents/security-engineer.md - Agent context file

## Impact
✅ **Consistent Syntax**: All agent invocations now use `@agent-[name]` format
✅ **User Clarity**: Clear distinction from previous `@agents-` plural form
✅ **Documentation Alignment**: All examples and references updated consistently
✅ **Framework Standards**: Aligns with SuperClaude naming conventions

Examples now correctly show:
- `@agent-security "review authentication"`
- `@agent-python-expert "optimize code"`
- `@agent-frontend-architect "design components"`

Total replacements: 80+ instances across entire documentation

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

Co-Authored-By: Claude <noreply@anthropic.com>

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"
 ```
 
 ---

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