mirror of
https://github.com/SuperClaude-Org/SuperClaude_Framework.git
synced 2025-12-29 16:16:08 +00:00
🔧 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>
This commit is contained in:
NomenAK
@@ -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"
|
||||
```
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user