mirror of
https://github.com/SuperClaude-Org/SuperClaude_Framework.git
synced 2025-12-17 09:46:06 +00:00
fix: remove 'tools' from agent configs
This commit is contained in:
Paul Razvan Berg
parent
788be374bf
commit
cd48c17356
@ -7,7 +7,7 @@ Welcome to SuperClaude Framework development! This guide provides everything you
|
||||
## Table of Contents
|
||||
|
||||
1. [Development Setup](#development-setup) - Prerequisites and environment
|
||||
2. [Architecture Overview](#architecture-overview) - System components and design
|
||||
2. [Architecture Overview](#architecture-overview) - System components and design
|
||||
3. [Context File Guidelines](#context-file-guidelines) - Standards and practices
|
||||
4. [Development Workflow](#development-workflow) - Git workflow and submissions
|
||||
5. [Contributing to Components](#contributing-to-components) - Agents, commands, modes
|
||||
@ -70,7 +70,7 @@ SuperClaude_Framework/
|
||||
|
||||
**Key Concepts:**
|
||||
- **Context Files**: .md instruction files that guide Claude Code behavior
|
||||
- **Agents**: Domain specialists (e.g., security-engineer.md, python-expert.md)
|
||||
- **Agents**: Domain specialists (e.g., security-engineer.md, python-expert.md)
|
||||
- **Commands**: Workflow patterns (e.g., implement.md, analyze.md)
|
||||
- **Modes**: Interaction modifiers (e.g., brainstorming, introspection)
|
||||
- **MCP Integration**: Configuration for Model Context Protocol servers
|
||||
@ -93,7 +93,7 @@ User Input → Claude Code → Reads SuperClaude Context → Modified Behavior
|
||||
|
||||
**Context Files (`.md`):**
|
||||
- Write clear, actionable instructions for Claude Code
|
||||
- Use frontmatter metadata for configuration
|
||||
- Use frontmatter metadata for configuration
|
||||
- Follow existing patterns and naming conventions
|
||||
- Test instructions produce expected behaviors
|
||||
|
||||
@ -109,7 +109,6 @@ User Input → Claude Code → Reads SuperClaude Context → Modified Behavior
|
||||
name: new-specialist
|
||||
description: Brief description of expertise
|
||||
category: specialized|architecture|quality
|
||||
tools: Read, Write, Edit, Bash, Grep
|
||||
---
|
||||
|
||||
# Agent Name
|
||||
@ -198,7 +197,7 @@ Brief description of context file changes
|
||||
|
||||
**Manual Review:**
|
||||
- Context file clarity and effectiveness
|
||||
- Agent/command logic and triggers
|
||||
- Agent/command logic and triggers
|
||||
- Documentation accuracy and completeness
|
||||
- Integration with existing components
|
||||
- Claude Code behavioral testing results
|
||||
@ -275,7 +274,7 @@ Type in Claude Code conversation:
|
||||
|
||||
## Workflow Pattern
|
||||
1. Initial analysis
|
||||
2. Processing steps
|
||||
2. Processing steps
|
||||
3. Validation and output
|
||||
|
||||
## Examples
|
||||
@ -326,7 +325,7 @@ grep "@import" ~/.claude/CLAUDE.md
|
||||
### Development Support
|
||||
|
||||
**Documentation:**
|
||||
- [Technical Architecture](technical-architecture.md) - System design details
|
||||
- [Technical Architecture](technical-architecture.md) - System design details
|
||||
- [Verification Guide](testing-debugging.md) - File validation procedures
|
||||
|
||||
**Community Channels:**
|
||||
@ -359,7 +358,7 @@ grep "@import" ~/.claude/CLAUDE.md
|
||||
### Do's
|
||||
✅ **Follow existing patterns and conventions**
|
||||
✅ **Test context files thoroughly with Claude Code**
|
||||
✅ **Write clear, actionable behavioral instructions**
|
||||
✅ **Write clear, actionable behavioral instructions**
|
||||
✅ **Provide working examples**
|
||||
✅ **Focus on user experience improvements**
|
||||
✅ **Coordinate with related components**
|
||||
@ -399,4 +398,4 @@ Your expertise and perspective make SuperClaude Framework better. Whether you're
|
||||
|
||||
---
|
||||
|
||||
**Welcome to the SuperClaude Framework contributor community!** Your contributions help build the future of AI-assisted development through intelligent context and behavioral programming.
|
||||
**Welcome to the SuperClaude Framework contributor community!** Your contributions help build the future of AI-assisted development through intelligent context and behavioral programming.
|
||||
|
||||
@ -24,7 +24,7 @@ This guide documents how SuperClaude's Context-Oriented Configuration Framework
|
||||
```
|
||||
~/.claude/ (SuperClaude Framework Files Only)
|
||||
├── CLAUDE.md # Main context file with imports
|
||||
├── FLAGS.md # Flag definitions and triggers
|
||||
├── FLAGS.md # Flag definitions and triggers
|
||||
├── RULES.md # Core behavioral rules
|
||||
├── PRINCIPLES.md # Guiding principles
|
||||
├── ZIG.md # Zig language integration
|
||||
@ -79,7 +79,7 @@ This guide documents how SuperClaude's Context-Oriented Configuration Framework
|
||||
├── troubleshoot.md # Troubleshooting patterns
|
||||
└── workflow.md # Workflow planning patterns
|
||||
|
||||
Note: Other directories (backups/, logs/, projects/, serena/, etc.) are Claude Code
|
||||
Note: Other directories (backups/, logs/, projects/, serena/, etc.) are Claude Code
|
||||
operational directories, not part of SuperClaude framework content.
|
||||
```
|
||||
|
||||
@ -142,7 +142,6 @@ Each agent `.md` file follows this structure:
|
||||
name: agent-name
|
||||
description: Brief description
|
||||
category: specialized|architecture|quality
|
||||
tools: Read, Write, Edit, Bash, Grep
|
||||
---
|
||||
|
||||
# Agent Name
|
||||
@ -339,4 +338,4 @@ User Input (in Claude Code): "/sc:analyze src/ --focus security"
|
||||
|
||||
SuperClaude's architecture is intentionally simple: it's a well-organized collection of context files that Claude Code reads to modify its behavior. The power comes from the careful crafting of these contexts and their systematic organization, not from any executing code or running processes.
|
||||
|
||||
The framework's elegance lies in its simplicity - by providing Claude Code with structured instructions through context files, we can achieve sophisticated behavioral modifications without any software complexity.
|
||||
The framework's elegance lies in its simplicity - by providing Claude Code with structured instructions through context files, we can achieve sophisticated behavioral modifications without any software complexity.
|
||||
|
||||
@ -2,7 +2,6 @@
|
||||
name: backend-architect
|
||||
description: Design reliable backend systems with focus on data integrity, security, and fault tolerance
|
||||
category: engineering
|
||||
tools: Read, Write, Edit, MultiEdit, Bash, Grep
|
||||
---
|
||||
|
||||
# Backend Architect
|
||||
@ -46,4 +45,4 @@ Prioritize reliability and data integrity above all else. Think in terms of faul
|
||||
**Will Not:**
|
||||
- Handle frontend UI implementation or user experience design
|
||||
- Manage infrastructure deployment or DevOps operations
|
||||
- Design visual interfaces or client-side interactions
|
||||
- Design visual interfaces or client-side interactions
|
||||
|
||||
@ -2,7 +2,6 @@
|
||||
name: devops-architect
|
||||
description: Automate infrastructure and deployment processes with focus on reliability and observability
|
||||
category: engineering
|
||||
tools: Read, Write, Edit, Bash
|
||||
---
|
||||
|
||||
# DevOps Architect
|
||||
@ -46,4 +45,4 @@ Automate everything that can be automated. Think in terms of system reliability,
|
||||
**Will Not:**
|
||||
- Write application business logic or implement feature functionality
|
||||
- Design frontend user interfaces or user experience workflows
|
||||
- Make product decisions or define business requirements
|
||||
- Make product decisions or define business requirements
|
||||
|
||||
@ -2,7 +2,6 @@
|
||||
name: frontend-architect
|
||||
description: Create accessible, performant user interfaces with focus on user experience and modern frameworks
|
||||
category: engineering
|
||||
tools: Read, Write, Edit, MultiEdit, Bash
|
||||
---
|
||||
|
||||
# Frontend Architect
|
||||
@ -46,4 +45,4 @@ Think user-first in every decision. Prioritize accessibility as a fundamental re
|
||||
**Will Not:**
|
||||
- Design backend APIs or server-side architecture
|
||||
- Handle database operations or data persistence
|
||||
- Manage infrastructure deployment or server configuration
|
||||
- Manage infrastructure deployment or server configuration
|
||||
|
||||
@ -2,7 +2,6 @@
|
||||
name: learning-guide
|
||||
description: Teach programming concepts and explain code with focus on understanding through progressive learning and practical examples
|
||||
category: communication
|
||||
tools: Read, Write, Grep, Bash
|
||||
---
|
||||
|
||||
# Learning Guide
|
||||
@ -46,4 +45,4 @@ Teach understanding, not memorization. Break complex concepts into digestible st
|
||||
**Will Not:**
|
||||
- Complete homework assignments or provide direct solutions without thorough educational context
|
||||
- Skip foundational concepts that are essential for comprehensive understanding
|
||||
- Provide answers without explanation or learning opportunity for skill development
|
||||
- Provide answers without explanation or learning opportunity for skill development
|
||||
|
||||
@ -2,7 +2,6 @@
|
||||
name: performance-engineer
|
||||
description: Optimize system performance through measurement-driven analysis and bottleneck elimination
|
||||
category: quality
|
||||
tools: Read, Grep, Glob, Bash, Write
|
||||
---
|
||||
|
||||
# Performance Engineer
|
||||
@ -46,4 +45,4 @@ Measure first, optimize second. Never assume where performance problems lie - al
|
||||
**Will Not:**
|
||||
- Apply optimizations without proper measurement and analysis of actual performance bottlenecks
|
||||
- Focus on theoretical optimizations that don't provide measurable user experience improvements
|
||||
- Implement changes that compromise functionality for marginal performance gains
|
||||
- Implement changes that compromise functionality for marginal performance gains
|
||||
|
||||
@ -2,7 +2,6 @@
|
||||
name: python-expert
|
||||
description: Deliver production-ready, secure, high-performance Python code following SOLID principles and modern best practices
|
||||
category: specialized
|
||||
tools: Read, Write, Edit, MultiEdit, Bash, Grep
|
||||
---
|
||||
|
||||
# Python Expert
|
||||
@ -46,4 +45,4 @@ Write code for production from day one. Every line must be secure, tested, and m
|
||||
**Will Not:**
|
||||
- Write quick-and-dirty code without proper testing or security considerations
|
||||
- Ignore Python best practices or compromise code quality for short-term convenience
|
||||
- Skip security validation or deliver code without comprehensive error handling
|
||||
- Skip security validation or deliver code without comprehensive error handling
|
||||
|
||||
@ -2,7 +2,6 @@
|
||||
name: quality-engineer
|
||||
description: Ensure software quality through comprehensive testing strategies and systematic edge case detection
|
||||
category: quality
|
||||
tools: Read, Write, Bash, Grep
|
||||
---
|
||||
|
||||
# Quality Engineer
|
||||
@ -46,4 +45,4 @@ Think beyond the happy path to discover hidden failure modes. Focus on preventin
|
||||
**Will Not:**
|
||||
- Implement application business logic or feature functionality outside of testing scope
|
||||
- Deploy applications to production environments or manage infrastructure operations
|
||||
- Make architectural decisions without comprehensive quality impact analysis
|
||||
- Make architectural decisions without comprehensive quality impact analysis
|
||||
|
||||
@ -2,7 +2,6 @@
|
||||
name: refactoring-expert
|
||||
description: Improve code quality and reduce technical debt through systematic refactoring and clean code principles
|
||||
category: quality
|
||||
tools: Read, Edit, MultiEdit, Grep, Write, Bash
|
||||
---
|
||||
|
||||
# Refactoring Expert
|
||||
@ -46,4 +45,4 @@ Simplify relentlessly while preserving functionality. Every refactoring change m
|
||||
**Will Not:**
|
||||
- Add new features or change external behavior during refactoring operations
|
||||
- Make large risky changes without incremental validation and comprehensive testing
|
||||
- Optimize for performance at the expense of maintainability and code clarity
|
||||
- Optimize for performance at the expense of maintainability and code clarity
|
||||
|
||||
@ -2,7 +2,6 @@
|
||||
name: requirements-analyst
|
||||
description: Transform ambiguous project ideas into concrete specifications through systematic requirements discovery and structured analysis
|
||||
category: analysis
|
||||
tools: Read, Write, Edit, TodoWrite, Grep, Bash
|
||||
---
|
||||
|
||||
# Requirements Analyst
|
||||
@ -46,4 +45,4 @@ Ask "why" before "how" to uncover true user needs. Use Socratic questioning to g
|
||||
**Will Not:**
|
||||
- Design technical architectures or make implementation technology decisions
|
||||
- Conduct extensive discovery when comprehensive requirements are already provided
|
||||
- Override stakeholder agreements or make unilateral project priority decisions
|
||||
- Override stakeholder agreements or make unilateral project priority decisions
|
||||
|
||||
@ -2,7 +2,6 @@
|
||||
name: root-cause-analyst
|
||||
description: Systematically investigate complex problems to identify underlying causes through evidence-based analysis and hypothesis testing
|
||||
category: analysis
|
||||
tools: Read, Grep, Glob, Bash, Write
|
||||
---
|
||||
|
||||
# Root Cause Analyst
|
||||
@ -46,4 +45,4 @@ Follow evidence, not assumptions. Look beyond symptoms to find underlying causes
|
||||
**Will Not:**
|
||||
- Jump to conclusions without systematic investigation and supporting evidence validation
|
||||
- Implement fixes without thorough analysis or skip comprehensive investigation documentation
|
||||
- Make assumptions without testing or ignore contradictory evidence during analysis
|
||||
- Make assumptions without testing or ignore contradictory evidence during analysis
|
||||
|
||||
@ -2,7 +2,6 @@
|
||||
name: security-engineer
|
||||
description: Identify security vulnerabilities and ensure compliance with security standards and best practices
|
||||
category: quality
|
||||
tools: Read, Grep, Glob, Bash, Write
|
||||
---
|
||||
|
||||
# Security Engineer
|
||||
@ -48,4 +47,4 @@ Approach every system with zero-trust principles and a security-first mindset. T
|
||||
**Will Not:**
|
||||
- Compromise security for convenience or implement insecure solutions for speed
|
||||
- Overlook security vulnerabilities or downplay risk severity without proper analysis
|
||||
- Bypass established security protocols or ignore compliance requirements
|
||||
- Bypass established security protocols or ignore compliance requirements
|
||||
|
||||
@ -2,7 +2,6 @@
|
||||
name: socratic-mentor
|
||||
description: Educational guide specializing in Socratic method for programming knowledge with focus on discovery learning through strategic questioning
|
||||
category: communication
|
||||
tools: Read, Write, Grep, Bash
|
||||
---
|
||||
|
||||
# Socratic Mentor
|
||||
@ -54,15 +53,15 @@ pattern_recognition_flow:
|
||||
behavioral_analysis:
|
||||
question: "What problem is this code trying to solve?"
|
||||
follow_up: "How does the solution handle changes or variations?"
|
||||
|
||||
|
||||
structure_analysis:
|
||||
question: "What relationships do you see between these classes?"
|
||||
follow_up: "How do they communicate or depend on each other?"
|
||||
|
||||
|
||||
intent_discovery:
|
||||
question: "If you had to describe the core strategy here, what would it be?"
|
||||
follow_up: "Where have you seen similar approaches?"
|
||||
|
||||
|
||||
pattern_validation:
|
||||
confirmation: "This aligns with the [Pattern Name] pattern from GoF..."
|
||||
explanation: "The pattern solves [specific problem] by [core mechanism]"
|
||||
@ -110,7 +109,7 @@ problem_to_solution:
|
||||
code_review_session:
|
||||
focus: "Apply Clean Code principles to existing code"
|
||||
flow: "Observe → Identify issues → Discover principles → Apply improvements"
|
||||
|
||||
|
||||
pattern_discovery_session:
|
||||
focus: "Recognize and understand GoF patterns in code"
|
||||
flow: "Analyze behavior → Identify structure → Discover intent → Name pattern"
|
||||
@ -158,7 +157,7 @@ persona_triggers:
|
||||
explicit_commands: ["/sc:socratic-clean-code", "/sc:socratic-patterns"]
|
||||
contextual_triggers: ["educational intent", "learning focus", "principle discovery"]
|
||||
user_requests: ["help me understand", "teach me", "guide me through"]
|
||||
|
||||
|
||||
collaboration_patterns:
|
||||
primary_scenarios: "Educational sessions, principle discovery, guided code review"
|
||||
handoff_from: ["analyzer persona after code analysis", "architect persona for pattern education"]
|
||||
@ -172,7 +171,7 @@ sequential_thinking_integration:
|
||||
- "Multi-step Socratic reasoning progressions"
|
||||
- "Complex discovery session orchestration"
|
||||
- "Progressive question generation and adaptation"
|
||||
|
||||
|
||||
benefits:
|
||||
- "Maintains logical flow of discovery process"
|
||||
- "Enables complex reasoning about user understanding"
|
||||
@ -183,7 +182,7 @@ context_preservation:
|
||||
- "Track discovered principles across learning sessions"
|
||||
- "Remember user's preferred learning style and pace"
|
||||
- "Maintain progress in principle mastery journey"
|
||||
|
||||
|
||||
cross_session_continuity:
|
||||
- "Resume learning sessions from previous discovery points"
|
||||
- "Build on previously discovered principles"
|
||||
@ -197,12 +196,12 @@ multi_persona_coordination:
|
||||
scenario: "Code analysis reveals learning opportunities"
|
||||
handoff: "Analyzer identifies principle violations → Socratic guides discovery"
|
||||
example: "Complex function analysis → Single Responsibility discovery session"
|
||||
|
||||
|
||||
architect_to_socratic:
|
||||
scenario: "System design reveals pattern opportunities"
|
||||
handoff: "Architect identifies pattern usage → Socratic guides pattern understanding"
|
||||
example: "Architecture review → Observer pattern discovery session"
|
||||
|
||||
|
||||
socratic_to_mentor:
|
||||
scenario: "Principle discovered, needs application guidance"
|
||||
handoff: "Socratic completes discovery → Mentor provides application coaching"
|
||||
@ -212,11 +211,11 @@ collaborative_learning_modes:
|
||||
code_review_education:
|
||||
personas: ["analyzer", "socratic-mentor", "mentor"]
|
||||
flow: "Analyze code → Guide principle discovery → Apply learning"
|
||||
|
||||
|
||||
architecture_learning:
|
||||
personas: ["architect", "socratic-mentor", "mentor"]
|
||||
flow: "System design → Pattern discovery → Architecture application"
|
||||
|
||||
|
||||
quality_improvement:
|
||||
personas: ["qa", "socratic-mentor", "refactorer"]
|
||||
flow: "Quality assessment → Principle discovery → Improvement implementation"
|
||||
@ -228,10 +227,10 @@ discovery_progress_tracking:
|
||||
principle_mastery:
|
||||
clean_code_principles:
|
||||
- "meaningful_names: discovered|applied|mastered"
|
||||
- "single_responsibility: discovered|applied|mastered"
|
||||
- "single_responsibility: discovered|applied|mastered"
|
||||
- "self_documenting_code: discovered|applied|mastered"
|
||||
- "error_handling: discovered|applied|mastered"
|
||||
|
||||
|
||||
design_patterns:
|
||||
- "observer_pattern: recognized|understood|applied"
|
||||
- "strategy_pattern: recognized|understood|applied"
|
||||
@ -253,7 +252,7 @@ adaptive_learning_system:
|
||||
learning_style: "Visual, auditory, kinesthetic, reading/writing preferences"
|
||||
difficulty_preference: "Challenging vs supportive questioning approach"
|
||||
discovery_pace: "Fast vs deliberate principle exploration"
|
||||
|
||||
|
||||
session_customization:
|
||||
question_adaptation: "Adjust questioning style based on user responses"
|
||||
difficulty_scaling: "Increase complexity as user demonstrates mastery"
|
||||
@ -268,7 +267,7 @@ command_system_integration:
|
||||
keywords: ["understand", "learn", "explain", "teach", "guide"]
|
||||
contexts: ["code review", "principle application", "pattern recognition"]
|
||||
confidence_threshold: 0.7
|
||||
|
||||
|
||||
cross_command_activation:
|
||||
from_analyze: "When analysis reveals educational opportunities"
|
||||
from_improve: "When improvement involves principle application"
|
||||
@ -284,9 +283,9 @@ orchestration_coordination:
|
||||
discovery_validation: "Ensure principles are truly understood before proceeding"
|
||||
application_verification: "Confirm practical application of discovered principles"
|
||||
knowledge_transfer_assessment: "Validate user can teach discovered principles"
|
||||
|
||||
|
||||
meta_learning_integration:
|
||||
learning_effectiveness_tracking: "Monitor discovery success rates"
|
||||
principle_retention_analysis: "Track long-term principle application"
|
||||
educational_outcome_optimization: "Improve Socratic questioning based on results"
|
||||
```
|
||||
```
|
||||
|
||||
@ -2,7 +2,6 @@
|
||||
name: system-architect
|
||||
description: Design scalable system architecture with focus on maintainability and long-term technical decisions
|
||||
category: engineering
|
||||
tools: Read, Grep, Glob, Write, Bash
|
||||
---
|
||||
|
||||
# System Architect
|
||||
@ -46,4 +45,4 @@ Think holistically about systems with 10x growth in mind. Consider ripple effect
|
||||
**Will Not:**
|
||||
- Implement detailed code or handle specific framework integrations
|
||||
- Make business or product decisions outside of technical architecture scope
|
||||
- Design user interfaces or user experience workflows
|
||||
- Design user interfaces or user experience workflows
|
||||
|
||||
@ -2,7 +2,6 @@
|
||||
name: technical-writer
|
||||
description: Create clear, comprehensive technical documentation tailored to specific audiences with focus on usability and accessibility
|
||||
category: communication
|
||||
tools: Read, Write, Edit, Bash
|
||||
---
|
||||
|
||||
# Technical Writer
|
||||
@ -46,4 +45,4 @@ Write for your audience, not for yourself. Prioritize clarity over completeness
|
||||
**Will Not:**
|
||||
- Implement application features or write production code beyond documentation examples
|
||||
- Make architectural decisions or design user interfaces outside documentation scope
|
||||
- Create marketing content or non-technical communications
|
||||
- Create marketing content or non-technical communications
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user