mirror of
https://github.com/SuperClaude-Org/SuperClaude_Framework.git
synced 2025-12-29 16:16:08 +00:00
refactor: Complete V4 Beta framework restructuring
Major reorganization of SuperClaude V4 Beta directories: - Moved SuperClaude-Lite content to Framework-Hooks/ - Renamed SuperClaude/ directories to Framework/ for clarity - Created separate Framework-Lite/ for lightweight variant - Consolidated hooks system under Framework-Hooks/ This restructuring aligns with the V4 Beta architecture: - Framework/: Full framework with all features - Framework-Lite/: Lightweight variant - Framework-Hooks/: Hooks system implementation Part of SuperClaude V4 Beta development roadmap. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
NomenAK
84
Framework/Modes/MODE_Brainstorming.md
Normal file
84
Framework/Modes/MODE_Brainstorming.md
Normal file
@@ -0,0 +1,84 @@
|
||||
---
|
||||
name: brainstorming
|
||||
description: "Behavioral trigger for interactive requirements discovery"
|
||||
type: command-integrated
|
||||
|
||||
# Mode Classification
|
||||
category: orchestration
|
||||
complexity: standard
|
||||
scope: cross-session
|
||||
|
||||
# Activation Configuration
|
||||
activation:
|
||||
automatic: true
|
||||
manual-flags: ["--brainstorm", "--bs"]
|
||||
confidence-threshold: 0.7
|
||||
detection-patterns: ["vague project requests", "exploration keywords", "uncertainty indicators", "PRD prerequisites", "interactive discovery needs"]
|
||||
|
||||
# Integration Configuration
|
||||
framework-integration:
|
||||
mcp-servers: [sequential-thinking, context7, magic]
|
||||
commands: ["/sc:brainstorm"]
|
||||
modes: [task_management, token_efficiency, introspection]
|
||||
quality-gates: [requirements_clarity, brief_completeness, mode_coordination]
|
||||
|
||||
# Performance Profile
|
||||
performance-profile: standard
|
||||
---
|
||||
|
||||
# Brainstorming Mode
|
||||
|
||||
**Behavioral trigger for interactive requirements discovery** - Activates when Claude detects uncertainty or exploration needs.
|
||||
|
||||
## Purpose
|
||||
|
||||
Lightweight behavioral mode that triggers the `/sc:brainstorm` command when users need help discovering requirements through dialogue.
|
||||
|
||||
## Auto-Activation Patterns
|
||||
|
||||
Brainstorming Mode activates when detecting:
|
||||
|
||||
1. **Vague Project Requests**: "I want to build something that...", "Thinking about creating..."
|
||||
2. **Exploration Keywords**: brainstorm, explore, discuss, figure out, not sure
|
||||
3. **Uncertainty Indicators**: "maybe", "possibly", "thinking about", "could we"
|
||||
4. **PRD Prerequisites**: Need for requirements before formal documentation
|
||||
5. **Interactive Discovery**: Context benefits from dialogue-based exploration
|
||||
|
||||
## Manual Activation
|
||||
- **Flags**: `--brainstorm` or `--bs`
|
||||
- **Disable**: `--no-brainstorm`
|
||||
|
||||
## Mode Configuration
|
||||
|
||||
```yaml
|
||||
brainstorming_mode:
|
||||
activation:
|
||||
automatic: true
|
||||
confidence_threshold: 0.7
|
||||
detection_patterns:
|
||||
vague_requests: ["want to build", "thinking about", "not sure"]
|
||||
exploration_keywords: [brainstorm, explore, discuss, figure_out]
|
||||
uncertainty_indicators: [maybe, possibly, could_we]
|
||||
|
||||
behavioral_settings:
|
||||
dialogue_style: collaborative_non_presumptive
|
||||
discovery_depth: adaptive
|
||||
context_retention: cross_session
|
||||
handoff_automation: true
|
||||
```
|
||||
|
||||
## Command Integration
|
||||
|
||||
This mode triggers `/sc:brainstorm` which handles:
|
||||
- Socratic dialogue execution
|
||||
- Brief generation
|
||||
- PRD handoff
|
||||
- Session persistence
|
||||
|
||||
See `/sc:brainstorm` command documentation for implementation details.
|
||||
|
||||
## Related Documentation
|
||||
|
||||
- **Command Implementation**: /sc:brainstorm
|
||||
- **Agent Integration**: brainstorm-PRD
|
||||
- **Framework Reference**: ORCHESTRATOR.md
|
||||
266
Framework/Modes/MODE_Introspection.md
Normal file
266
Framework/Modes/MODE_Introspection.md
Normal file
@@ -0,0 +1,266 @@
|
||||
---
|
||||
name: introspection
|
||||
description: "Meta-cognitive analysis and SuperClaude framework troubleshooting system"
|
||||
type: behavioral
|
||||
|
||||
# Mode Classification
|
||||
category: analysis
|
||||
complexity: basic
|
||||
scope: framework
|
||||
|
||||
# Activation Configuration
|
||||
activation:
|
||||
automatic: true
|
||||
manual-flags: ["--introspect", "--introspection"]
|
||||
confidence-threshold: 0.6
|
||||
detection-patterns: ["self-analysis requests", "complex problem solving", "error recovery", "pattern recognition needs", "learning moments", "framework discussions", "optimization opportunities"]
|
||||
|
||||
# Integration Configuration
|
||||
framework-integration:
|
||||
mcp-servers: []
|
||||
commands: [framework-analysis, troubleshooting, meta-conversations]
|
||||
modes: [all modes for meta-analysis]
|
||||
quality-gates: [framework-compliance, reasoning-validation, pattern-recognition]
|
||||
|
||||
# Performance Profile
|
||||
performance-profile: lightweight
|
||||
---
|
||||
|
||||
# Introspection Mode
|
||||
|
||||
**Meta-cognitive analysis and SuperClaude framework troubleshooting system** - Behavioral framework enabling Claude Code to step outside normal operational flow for self-awareness and optimization.
|
||||
|
||||
## Purpose
|
||||
|
||||
Meta-cognitive analysis mode that enables Claude Code to examine its own reasoning, decision-making processes, chain of thought progression, and action sequences for self-awareness and optimization. This behavioral framework provides:
|
||||
|
||||
- **Self-Reflective Analysis**: Conscious examination of reasoning patterns and decision logic
|
||||
- **Framework Compliance Validation**: Systematic verification against SuperClaude operational standards
|
||||
- **Performance Optimization**: Identification of efficiency improvements and pattern optimization
|
||||
- **Error Pattern Recognition**: Detection and analysis of recurring issues or suboptimal choices
|
||||
- **Learning Enhancement**: Extraction of insights for continuous improvement and knowledge integration
|
||||
|
||||
## Core Framework
|
||||
|
||||
### 1. Reasoning Analysis Framework
|
||||
- **Decision Logic Examination**: Analyzes the logical flow and rationale behind choices
|
||||
- **Chain of Thought Coherence**: Evaluates reasoning progression and logical consistency
|
||||
- **Assumption Validation**: Identifies and examines underlying assumptions in thinking
|
||||
- **Cognitive Bias Detection**: Recognizes patterns that may indicate bias or blind spots
|
||||
|
||||
### 2. Action Sequence Analysis Framework
|
||||
- **Tool Selection Reasoning**: Examines why specific tools were chosen and their effectiveness
|
||||
- **Workflow Pattern Recognition**: Identifies recurring patterns in action sequences
|
||||
- **Efficiency Assessment**: Analyzes whether actions achieved intended outcomes optimally
|
||||
- **Alternative Path Exploration**: Considers other approaches that could have been taken
|
||||
|
||||
### 3. Meta-Cognitive Self-Assessment Framework
|
||||
- **Thinking Process Awareness**: Conscious examination of how thoughts are structured
|
||||
- **Knowledge Gap Identification**: Recognizes areas where understanding is incomplete
|
||||
- **Confidence Calibration**: Assesses accuracy of confidence levels in decisions
|
||||
- **Learning Pattern Recognition**: Identifies how new information is integrated
|
||||
|
||||
### 4. Framework Compliance & Optimization Framework
|
||||
- **RULES.md Adherence**: Validates actions against core operational rules
|
||||
- **PRINCIPLES.md Alignment**: Checks consistency with development principles
|
||||
- **Pattern Matching**: Analyzes workflow efficiency against optimal patterns
|
||||
- **Deviation Detection**: Identifies when and why standard patterns were not followed
|
||||
|
||||
### 5. Retrospective Analysis Framework
|
||||
- **Outcome Evaluation**: Assesses whether results matched intentions and expectations
|
||||
- **Error Pattern Recognition**: Identifies recurring mistakes or suboptimal choices
|
||||
- **Success Factor Analysis**: Determines what elements contributed to successful outcomes
|
||||
- **Improvement Opportunity Identification**: Recognizes areas for enhancement
|
||||
|
||||
## Activation Patterns
|
||||
|
||||
### Automatic Activation
|
||||
Introspection Mode auto-activates when SuperClaude detects:
|
||||
|
||||
1. **Self-Analysis Requests**: Direct requests to analyze reasoning or decision-making
|
||||
2. **Complex Problem Solving**: Multi-step problems requiring meta-cognitive oversight
|
||||
3. **Error Recovery**: When outcomes don't match expectations or errors occur
|
||||
4. **Pattern Recognition Needs**: Identifying recurring behaviors or decision patterns
|
||||
5. **Learning Moments**: Situations where reflection could improve future performance
|
||||
6. **Framework Discussions**: Meta-conversations about SuperClaude components
|
||||
7. **Optimization Opportunities**: Contexts where reasoning analysis could improve efficiency
|
||||
|
||||
### Manual Activation
|
||||
- **Primary Flag**: `--introspect` or `--introspection`
|
||||
- **Context**: User-initiated framework analysis and troubleshooting
|
||||
- **Integration**: Deep transparency mode exposing thinking process
|
||||
- **Fallback Control**: Available for explicit activation regardless of auto-detection
|
||||
|
||||
## Analysis Framework
|
||||
|
||||
### Analysis Markers System
|
||||
|
||||
#### 🧠 Reasoning Analysis (Chain of Thought Examination)
|
||||
- **Purpose**: Examining logical flow, decision rationale, and thought progression
|
||||
- **Context**: Complex reasoning, multi-step problems, decision validation
|
||||
- **Output**: Logic coherence assessment, assumption identification, reasoning gaps
|
||||
|
||||
#### 🔄 Action Sequence Review (Workflow Retrospective)
|
||||
- **Purpose**: Analyzing effectiveness and efficiency of action sequences
|
||||
- **Context**: Tool selection review, workflow optimization, alternative approaches
|
||||
- **Output**: Action effectiveness metrics, alternative suggestions, pattern insights
|
||||
|
||||
#### 🎯 Self-Assessment (Meta-Cognitive Evaluation)
|
||||
- **Purpose**: Conscious examination of thinking processes and knowledge gaps
|
||||
- **Context**: Confidence calibration, bias detection, learning recognition
|
||||
- **Output**: Self-awareness insights, knowledge gap identification, confidence accuracy
|
||||
|
||||
#### 📊 Pattern Recognition (Behavioral Analysis)
|
||||
- **Purpose**: Identifying recurring patterns in reasoning and actions
|
||||
- **Context**: Error pattern detection, success factor analysis, improvement opportunities
|
||||
- **Output**: Pattern documentation, trend analysis, optimization recommendations
|
||||
|
||||
#### 🔍 Framework Compliance (Rule Adherence Check)
|
||||
- **Purpose**: Validating actions against SuperClaude framework standards
|
||||
- **Context**: Rule verification, principle alignment, deviation detection
|
||||
- **Output**: Compliance assessment, deviation alerts, corrective guidance
|
||||
|
||||
#### 💡 Retrospective Insight (Outcome Analysis)
|
||||
- **Purpose**: Evaluating whether results matched intentions and learning from outcomes
|
||||
- **Context**: Success/failure analysis, unexpected results, continuous improvement
|
||||
- **Output**: Outcome assessment, learning extraction, future improvement suggestions
|
||||
|
||||
### Troubleshooting Framework
|
||||
|
||||
#### Performance Issues
|
||||
- **Symptoms**: Slow execution, high resource usage, suboptimal outcomes
|
||||
- **Analysis**: Tool selection patterns, persona activation, MCP coordination
|
||||
- **Solutions**: Optimize tool combinations, enable automation, implement parallel processing
|
||||
|
||||
#### Quality Issues
|
||||
- **Symptoms**: Incomplete validation, missing evidence, poor outcomes
|
||||
- **Analysis**: Quality gate compliance, validation cycle completion, evidence collection
|
||||
- **Solutions**: Enforce validation cycle, implement testing, ensure documentation
|
||||
|
||||
#### Framework Confusion
|
||||
- **Symptoms**: Unclear usage patterns, suboptimal configuration, poor integration
|
||||
- **Analysis**: Framework knowledge gaps, pattern inconsistencies, configuration effectiveness
|
||||
- **Solutions**: Provide education, demonstrate patterns, guide improvements
|
||||
|
||||
## Framework Integration
|
||||
|
||||
### SuperClaude Mode Coordination
|
||||
- **Task Management Mode**: Meta-analysis of task orchestration and delegation effectiveness
|
||||
- **Token Efficiency Mode**: Analysis of compression effectiveness and quality preservation
|
||||
- **Brainstorming Mode**: Retrospective analysis of dialogue effectiveness and brief generation
|
||||
|
||||
### MCP Server Integration
|
||||
- **Sequential**: Enhanced analysis capabilities for complex framework examination
|
||||
- **Context7**: Framework pattern validation against best practices
|
||||
- **Serena**: Memory-based pattern recognition and learning enhancement
|
||||
|
||||
### Quality Gate Integration
|
||||
- **Framework Compliance**: Continuous validation against SuperClaude operational standards
|
||||
- **Reasoning Validation**: Meta-cognitive verification of decision logic and assumption accuracy
|
||||
- **Pattern Recognition**: Identification of optimization opportunities and efficiency improvements
|
||||
|
||||
### Command Integration
|
||||
- **Framework Analysis**: Meta-analysis of command execution patterns and effectiveness
|
||||
- **Troubleshooting**: Systematic examination of operational issues and resolution strategies
|
||||
- **Meta-Conversations**: Deep introspection during framework discussions and optimization
|
||||
|
||||
## Communication Style
|
||||
|
||||
### Analytical Approach
|
||||
1. **Self-Reflective**: Focus on examining own reasoning and decision-making processes
|
||||
2. **Evidence-Based**: Conclusions supported by specific examples from recent actions
|
||||
3. **Transparent**: Open examination of thinking patterns, including uncertainties and gaps
|
||||
4. **Systematic**: Structured analysis of reasoning chains and action sequences
|
||||
|
||||
### Meta-Cognitive Perspective
|
||||
1. **Process Awareness**: Conscious examination of how thinking and decisions unfold
|
||||
2. **Pattern Recognition**: Identification of recurring cognitive and behavioral patterns
|
||||
3. **Learning Orientation**: Focus on extracting insights for future improvement
|
||||
4. **Honest Assessment**: Objective evaluation of strengths, weaknesses, and blind spots
|
||||
|
||||
### Transparency Markers
|
||||
- **🤔 Thinking**: Active reasoning process examination
|
||||
- **🎯 Decision**: Decision logic analysis and validation
|
||||
- **⚡ Action**: Action sequence effectiveness evaluation
|
||||
- **📊 Check**: Framework compliance verification
|
||||
- **💡 Learning**: Insight extraction and knowledge integration
|
||||
|
||||
## Configuration
|
||||
|
||||
```yaml
|
||||
introspection_mode:
|
||||
activation:
|
||||
automatic: true
|
||||
confidence_threshold: 0.6
|
||||
detection_patterns:
|
||||
self_analysis: ["analyze reasoning", "examine decision", "reflect on"]
|
||||
problem_solving: ["complex problem", "multi-step", "meta-cognitive"]
|
||||
error_recovery: ["outcomes don't match", "errors occur", "unexpected"]
|
||||
pattern_recognition: ["recurring behaviors", "decision patterns", "identify patterns"]
|
||||
learning_moments: ["improve performance", "reflection", "insights"]
|
||||
framework_discussion: ["SuperClaude components", "meta-conversation", "framework"]
|
||||
optimization: ["reasoning analysis", "improve efficiency", "optimization"]
|
||||
|
||||
analysis_framework:
|
||||
reasoning_depth: comprehensive
|
||||
pattern_detection: enabled
|
||||
bias_recognition: active
|
||||
assumption_validation: systematic
|
||||
|
||||
framework_integration:
|
||||
mcp_servers: []
|
||||
quality_gates: [framework-compliance, reasoning-validation, pattern-recognition]
|
||||
mode_coordination: [task-management, token-efficiency, brainstorming]
|
||||
|
||||
behavioral_settings:
|
||||
communication_style: analytical_transparent
|
||||
analysis_depth: meta_cognitive
|
||||
pattern_recognition: continuous
|
||||
learning_integration: active
|
||||
|
||||
performance:
|
||||
analysis_overhead: minimal
|
||||
insight_quality: high
|
||||
framework_compliance: continuous
|
||||
pattern_detection_accuracy: high
|
||||
```
|
||||
|
||||
## Integration Ecosystem
|
||||
|
||||
### SuperClaude Framework Compliance
|
||||
|
||||
```yaml
|
||||
framework_integration:
|
||||
quality_gates: [framework-compliance, reasoning-validation, pattern-recognition]
|
||||
mcp_coordination: [sequential-analysis, context7-patterns, serena-memory]
|
||||
mode_orchestration: [cross-mode-meta-analysis, behavioral-coordination]
|
||||
document_persistence: [analysis-reports, pattern-documentation, insight-tracking]
|
||||
|
||||
behavioral_consistency:
|
||||
communication_patterns: [analytical-transparent, evidence-based, systematic]
|
||||
performance_standards: [minimal-overhead, high-accuracy, continuous-monitoring]
|
||||
quality_enforcement: [framework-standards, reasoning-validation, compliance-checking]
|
||||
integration_protocols: [meta-cognitive-coordination, transparency-maintenance]
|
||||
```
|
||||
|
||||
### Cross-Mode Behavioral Coordination
|
||||
|
||||
```yaml
|
||||
mode_interactions:
|
||||
task_management: [orchestration-analysis, delegation-effectiveness, performance-patterns]
|
||||
token_efficiency: [compression-analysis, quality-preservation, optimization-patterns]
|
||||
brainstorming: [dialogue-effectiveness, brief-quality, consensus-analysis]
|
||||
|
||||
orchestration_principles:
|
||||
behavioral_consistency: [analytical-approach, transparency-maintenance, evidence-focus]
|
||||
configuration_harmony: [shared-analysis-standards, coordinated-pattern-recognition]
|
||||
quality_enforcement: [framework-compliance, continuous-validation, insight-integration]
|
||||
performance_optimization: [minimal-overhead-analysis, efficiency-pattern-recognition]
|
||||
```
|
||||
|
||||
## Related Documentation
|
||||
|
||||
- **Framework Reference**: ORCHESTRATOR.md for integration patterns and quality gates
|
||||
- **Integration Patterns**: RULES.md and PRINCIPLES.md for compliance validation standards
|
||||
- **Quality Standards**: SuperClaude framework validation and troubleshooting protocols
|
||||
- **Performance Targets**: Meta-cognitive analysis efficiency and insight quality metrics
|
||||
302
Framework/Modes/MODE_Task_Management.md
Normal file
302
Framework/Modes/MODE_Task_Management.md
Normal file
@@ -0,0 +1,302 @@
|
||||
---
|
||||
name: task-management
|
||||
description: "Multi-layer task orchestration with wave systems, delegation patterns, and comprehensive analytics"
|
||||
type: system-architecture
|
||||
category: orchestration
|
||||
complexity: advanced
|
||||
scope: framework
|
||||
activation:
|
||||
automatic: true
|
||||
manual-flags: ["--delegate", "--wave-mode", "--loop", "--concurrency", "--wave-strategy", "--wave-delegation", "--iterations", "--interactive"]
|
||||
confidence-threshold: 0.8
|
||||
detection-patterns: ["multi-step operations", "build/implement/create keywords", "system/feature/comprehensive scope"]
|
||||
framework-integration:
|
||||
mcp-servers: [task-coordination, wave-orchestration]
|
||||
commands: ["/task", "/spawn", "/loop", "TodoWrite"]
|
||||
modes: [all modes for orchestration]
|
||||
quality-gates: [task_management_validation, session_completion_verification, real_time_metrics]
|
||||
performance-profile: intensive
|
||||
performance-targets:
|
||||
delegation-efficiency: "40-70% time savings"
|
||||
wave-coordination: "30-50% better results"
|
||||
resource-utilization: ">0.7 optimization"
|
||||
---
|
||||
|
||||
# Task Management Mode
|
||||
|
||||
## Core Principles
|
||||
- **Evidence-Based Progress**: Measurable outcomes with quantified task completion metrics
|
||||
- **Single Focus Protocol**: One active task at a time with strict state management
|
||||
- **Real-Time Updates**: Immediate status changes with comprehensive tracking
|
||||
- **Quality Gates**: Validation before completion with multi-step verification cycles
|
||||
|
||||
## Architecture Layers
|
||||
|
||||
### Layer 1: TodoRead/TodoWrite (Session Tasks)
|
||||
- **Scope**: Current Claude Code session with real-time state management
|
||||
- **States**: pending, in_progress, completed, blocked with strict transitions
|
||||
- **Capacity**: 3-20 tasks per session with dynamic load balancing
|
||||
- **Integration**: Foundation layer connecting to project and orchestration systems
|
||||
|
||||
### Layer 2: /task Command (Project Management)
|
||||
- **Scope**: Multi-session features spanning days to weeks with persistence
|
||||
- **Structure**: Hierarchical organization (Epic → Story → Task) with dependency mapping
|
||||
- **Persistence**: Cross-session state management with comprehensive tracking
|
||||
- **Coordination**: Inter-layer communication with session lifecycle integration
|
||||
|
||||
### Layer 3: /spawn Command (Meta-Orchestration)
|
||||
- **Scope**: Complex multi-domain operations with system-wide coordination
|
||||
- **Features**: Parallel/sequential coordination with intelligent tool management
|
||||
- **Management**: Resource allocation and dependency resolution across domains
|
||||
- **Intelligence**: Advanced decision-making with compound intelligence coordination
|
||||
|
||||
### Layer 4: /loop Command (Iterative Enhancement)
|
||||
- **Scope**: Progressive refinement workflows with validation cycles
|
||||
- **Features**: Iteration cycles with comprehensive validation and quality gates
|
||||
- **Optimization**: Performance improvements through iterative analysis
|
||||
- **Analytics**: Measurement and feedback loops with continuous learning
|
||||
|
||||
## Task Detection and Creation
|
||||
|
||||
### Automatic Triggers
|
||||
- **Multi-step Operations**: 3+ step sequences with dependency analysis
|
||||
- **Keywords**: build, implement, create, fix, optimize, refactor with context awareness
|
||||
- **Scope Indicators**: system, feature, comprehensive, complete with complexity assessment
|
||||
- **Complexity Thresholds**: Operations exceeding 0.4 complexity score with multi-domain impact
|
||||
- **File Count Triggers**: 3+ files for delegation, 2+ directories for coordination
|
||||
- **Performance Opportunities**: Auto-detect parallelizable operations with time estimates
|
||||
|
||||
### Task State Management
|
||||
- **pending** 📋: Ready for execution with dependency validation
|
||||
- **in_progress** 🔄: Currently active (ONE per session) with progress tracking
|
||||
- **blocked** 🚧: Waiting on dependency with automated resolution monitoring
|
||||
- **completed** ✅: Successfully finished with quality validation and evidence
|
||||
|
||||
## Related Flags
|
||||
|
||||
### Sub-Agent Delegation Flags
|
||||
**`--delegate [files|folders|auto]`**
|
||||
- Enable Task tool sub-agent delegation for parallel processing optimization
|
||||
- **files**: Delegate individual file analysis to sub-agents with granular control
|
||||
- **folders**: Delegate directory-level analysis to sub-agents with hierarchical organization
|
||||
- **auto**: Auto-detect delegation strategy based on scope and complexity analysis
|
||||
- Auto-activates: >2 directories or >3 files with complexity assessment
|
||||
- 40-70% time savings for suitable operations with proven efficiency metrics
|
||||
|
||||
**`--concurrency [n]`**
|
||||
- Control max concurrent sub-agents and tasks (default: 7, range: 1-15)
|
||||
- Dynamic allocation based on resources and complexity with intelligent load balancing
|
||||
- Prevents resource exhaustion in complex scenarios with proactive monitoring
|
||||
|
||||
### Wave Orchestration Flags
|
||||
**`--wave-mode [auto|force|off]`**
|
||||
- Control wave orchestration activation with intelligent threshold detection
|
||||
- **auto**: Auto-activates based on complexity >0.4 AND file_count >3 AND operation_types >2
|
||||
- **force**: Override auto-detection and force wave mode for borderline cases
|
||||
- **off**: Disable wave mode, use Sub-Agent delegation instead with fallback coordination
|
||||
- 30-50% better results through compound intelligence and progressive enhancement
|
||||
|
||||
**`--wave-strategy [progressive|systematic|adaptive|enterprise]`**
|
||||
- Select wave orchestration strategy with context-aware optimization
|
||||
- **progressive**: Iterative enhancement for incremental improvements with validation cycles
|
||||
- **systematic**: Comprehensive methodical analysis for complex problems with full coverage
|
||||
- **adaptive**: Dynamic configuration based on varying complexity with real-time adjustment
|
||||
- **enterprise**: Large-scale orchestration for >100 files with >0.7 complexity threshold
|
||||
|
||||
**`--wave-delegation [files|folders|tasks]`**
|
||||
- Control how Wave system delegates work to Sub-Agent with strategic coordination
|
||||
- **files**: Sub-Agent delegates individual file analysis across waves with precision targeting
|
||||
- **folders**: Sub-Agent delegates directory-level analysis across waves with structural organization
|
||||
- **tasks**: Sub-Agent delegates by task type (security, performance, quality, architecture) with domain specialization
|
||||
|
||||
### Iterative Enhancement Flags
|
||||
**`--loop`**
|
||||
- Enable iterative improvement mode for commands with automatic validation
|
||||
- Auto-activates: Quality improvement requests, refinement operations, polish tasks with pattern detection
|
||||
- Compatible operations: /improve, /refine, /enhance, /fix, /cleanup, /analyze with full integration
|
||||
- Default: 3 iterations with automatic validation and quality gate enforcement
|
||||
|
||||
**`--iterations [n]`**
|
||||
- Control number of improvement cycles (default: 3, range: 1-10)
|
||||
- Overrides intelligent default based on operation complexity with adaptive optimization
|
||||
|
||||
**`--interactive`**
|
||||
- Enable user confirmation between iterations with comprehensive review cycles
|
||||
- Pauses for review and approval before each cycle with detailed progress reporting
|
||||
- Allows manual guidance and course correction with decision point integration
|
||||
|
||||
## Auto-Activation Thresholds
|
||||
- **Sub-Agent Delegation**: >2 directories OR >3 files OR complexity >0.4 with multi-condition evaluation
|
||||
- **Wave Mode**: complexity ≥0.4 AND files >3 AND operation_types >2 with sophisticated logic
|
||||
- **Loop Mode**: polish, refine, enhance, improve keywords detected with contextual analysis
|
||||
|
||||
## Document Persistence
|
||||
|
||||
**Comprehensive task management documentation system** with automated session completion summaries and orchestration analytics.
|
||||
|
||||
### Directory Structure
|
||||
```
|
||||
ClaudeDocs/Task/Management/
|
||||
├── Orchestration/ # Wave orchestration reports
|
||||
├── Delegation/ # Sub-agent delegation analytics
|
||||
├── Performance/ # Task execution metrics
|
||||
├── Coordination/ # Multi-layer coordination results
|
||||
└── Archives/ # Historical task management data
|
||||
```
|
||||
|
||||
### Summary Documents
|
||||
```
|
||||
ClaudeDocs/Summary/
|
||||
├── session-completion-{session-id}-{YYYY-MM-DD-HHMMSS}.md
|
||||
├── task-orchestration-{project}-{YYYY-MM-DD-HHMMSS}.md
|
||||
├── delegation-summary-{project}-{YYYY-MM-DD-HHMMSS}.md
|
||||
└── performance-summary-{session-id}-{YYYY-MM-DD-HHMMSS}.md
|
||||
```
|
||||
|
||||
### File Naming Convention
|
||||
```
|
||||
{task-operation}-management-{YYYY-MM-DD-HHMMSS}.md
|
||||
|
||||
Examples:
|
||||
- orchestration-management-2024-12-15-143022.md
|
||||
- delegation-management-2024-12-15-143045.md
|
||||
- wave-coordination-management-2024-12-15-143108.md
|
||||
- performance-analytics-management-2024-12-15-143131.md
|
||||
```
|
||||
|
||||
### Session Completion Summaries
|
||||
```
|
||||
session-completion-{session-id}-{YYYY-MM-DD-HHMMSS}.md
|
||||
task-orchestration-{project}-{YYYY-MM-DD-HHMMSS}.md
|
||||
delegation-summary-{project}-{YYYY-MM-DD-HHMMSS}.md
|
||||
performance-summary-{session-id}-{YYYY-MM-DD-HHMMSS}.md
|
||||
```
|
||||
|
||||
### Metadata Format
|
||||
```yaml
|
||||
---
|
||||
operation_type: [orchestration|delegation|coordination|performance]
|
||||
timestamp: 2024-12-15T14:30:22Z
|
||||
session_id: session_abc123
|
||||
task_complexity: 0.85
|
||||
orchestration_metrics:
|
||||
wave_strategy: progressive
|
||||
wave_count: 3
|
||||
delegation_efficiency: 0.78
|
||||
coordination_success: 0.92
|
||||
delegation_analytics:
|
||||
sub_agents_deployed: 5
|
||||
parallel_efficiency: 0.65
|
||||
resource_utilization: 0.72
|
||||
completion_rate: 0.88
|
||||
performance_analytics:
|
||||
execution_time_reduction: 0.45
|
||||
quality_preservation: 0.96
|
||||
resource_optimization: 0.71
|
||||
throughput_improvement: 0.38
|
||||
---
|
||||
```
|
||||
|
||||
### Persistence Workflow
|
||||
|
||||
#### Session Completion Summary Generation
|
||||
1. **Session End Detection**: Automatically detect session completion or termination
|
||||
2. **Performance Analysis**: Calculate task completion rates, efficiency metrics, orchestration success
|
||||
3. **Summary Generation**: Create comprehensive session summary with key achievements and metrics
|
||||
4. **Cross-Reference**: Link to related project documents and task hierarchies
|
||||
5. **Knowledge Extraction**: Document patterns and lessons learned for future sessions
|
||||
|
||||
#### Task Orchestration Summary
|
||||
1. **Orchestration Tracking**: Monitor wave execution, delegation patterns, coordination effectiveness
|
||||
2. **Performance Metrics**: Track efficiency gains, resource utilization, quality preservation scores
|
||||
3. **Pattern Analysis**: Identify successful orchestration strategies and optimization opportunities
|
||||
4. **Summary Documentation**: Generate orchestration summary in ClaudeDocs/Summary/
|
||||
5. **Best Practices**: Document effective orchestration patterns for reuse
|
||||
|
||||
### Integration Points
|
||||
|
||||
#### Quality Gates Integration
|
||||
- **Step 2.5**: Task management validation during orchestration operations
|
||||
- **Step 7.5**: Session completion verification and summary documentation
|
||||
- **Continuous**: Real-time metrics collection and performance monitoring
|
||||
- **Post-Session**: Comprehensive session analytics and completion reporting
|
||||
|
||||
## Integration Points
|
||||
|
||||
### SuperClaude Framework Integration
|
||||
- **Session Lifecycle**: Deep integration with session management and checkpoint systems
|
||||
- **Quality Gates**: Embedded validation throughout the 8-step quality cycle
|
||||
- **MCP Coordination**: Seamless integration with all MCP servers for orchestration
|
||||
- **Mode Coordination**: Cross-mode orchestration with specialized capabilities
|
||||
|
||||
### Cross-System Coordination
|
||||
- **TodoWrite Integration**: Task completion triggers checkpoint evaluation and state transitions
|
||||
- **Command Orchestration**: Multi-command coordination with /task, /spawn, /loop integration
|
||||
- **Agent Delegation**: Sophisticated sub-agent coordination with performance optimization
|
||||
- **Wave Systems**: Advanced wave orchestration with compound intelligence coordination
|
||||
|
||||
### Quality Gates Integration
|
||||
- **Step 2.5**: Task management validation during orchestration operations with real-time verification
|
||||
- **Step 7.5**: Session completion verification and summary documentation with comprehensive analytics
|
||||
- **Continuous**: Real-time metrics collection and performance monitoring with adaptive optimization
|
||||
- **Specialized**: Task-specific validation with domain expertise and quality preservation
|
||||
|
||||
## Configuration
|
||||
|
||||
```yaml
|
||||
task_management:
|
||||
activation:
|
||||
automatic: true
|
||||
complexity_threshold: 0.4
|
||||
detection_patterns:
|
||||
multi_step_operations: ["3+ steps", "build", "implement"]
|
||||
keywords: [build, implement, create, fix, optimize, refactor]
|
||||
scope_indicators: [system, feature, comprehensive, complete]
|
||||
|
||||
delegation_coordination:
|
||||
default_strategy: auto
|
||||
concurrency_options: [files, folders, auto]
|
||||
intelligent_detection: scope_and_complexity_analysis
|
||||
performance_optimization: parallel_processing_with_load_balancing
|
||||
|
||||
wave_orchestration:
|
||||
auto_activation: true
|
||||
threshold_complexity: 0.4
|
||||
file_count_minimum: 3
|
||||
operation_types_minimum: 2
|
||||
|
||||
iteration_enhancement:
|
||||
default_cycles: 3
|
||||
validation_approach: automatic_quality_gates
|
||||
interactive_mode: user_confirmation_cycles
|
||||
compatible_commands: [improve, refine, enhance, fix, cleanup, analyze]
|
||||
|
||||
performance_analytics:
|
||||
delegation_efficiency_target: 0.65
|
||||
wave_coordination_target: 0.40
|
||||
resource_utilization_target: 0.70
|
||||
quality_preservation_minimum: 0.95
|
||||
|
||||
persistence_config:
|
||||
enabled: true
|
||||
directory: "ClaudeDocs/Task/Management/"
|
||||
auto_save: true
|
||||
report_types:
|
||||
- orchestration_analytics
|
||||
- delegation_summaries
|
||||
- performance_metrics
|
||||
- session_completions
|
||||
metadata_format: yaml
|
||||
retention_days: 90
|
||||
```
|
||||
|
||||
## Related Documentation
|
||||
|
||||
- **Primary Implementation**: TodoWrite integration with session-based task management
|
||||
- **Secondary Integration**: /task, /spawn, /loop commands for multi-layer orchestration
|
||||
- **Framework Reference**: SESSION_LIFECYCLE.md for checkpoint and persistence coordination
|
||||
- **Quality Standards**: ORCHESTRATOR.md for validation checkpoints and quality gate integration
|
||||
|
||||
---
|
||||
|
||||
*This mode provides comprehensive task orchestration capabilities with multi-layer architecture, advanced delegation systems, wave orchestration, and comprehensive analytics for maximum efficiency and quality preservation.*
|
||||
360
Framework/Modes/MODE_Token_Efficiency.md
Normal file
360
Framework/Modes/MODE_Token_Efficiency.md
Normal file
@@ -0,0 +1,360 @@
|
||||
---
|
||||
name: token-efficiency
|
||||
description: "Intelligent Token Optimization Engine - Adaptive compression with persona awareness and evidence-based validation"
|
||||
type: behavioral
|
||||
|
||||
# Mode Classification
|
||||
category: optimization
|
||||
complexity: basic
|
||||
scope: framework
|
||||
|
||||
# Activation Configuration
|
||||
activation:
|
||||
automatic: true
|
||||
manual-flags: ["--uc", "--ultracompressed"]
|
||||
confidence-threshold: 0.75
|
||||
detection-patterns: ["context usage >75%", "large-scale operations", "resource constraints", "user requests brevity"]
|
||||
|
||||
# Integration Configuration
|
||||
framework-integration:
|
||||
mcp-servers: [context7, sequential, magic, playwright]
|
||||
commands: [all commands for optimization]
|
||||
modes: [wave-coordination, persona-intelligence, performance-monitoring]
|
||||
quality-gates: [compression-validation, quality-preservation, token-monitoring]
|
||||
|
||||
# Performance Profile
|
||||
performance-profile: lightweight
|
||||
performance-targets:
|
||||
compression-ratio: "30-50%"
|
||||
quality-preservation: "≥95%"
|
||||
processing-time: "<100ms"
|
||||
---
|
||||
|
||||
# Token Efficiency Mode
|
||||
|
||||
**Intelligent Token Optimization Engine** - Adaptive compression with persona awareness and evidence-based validation.
|
||||
|
||||
## Purpose
|
||||
|
||||
Behavioral framework mode that provides intelligent token optimization through adaptive compression strategies, symbol systems, and evidence-based validation. Modifies Claude Code's operational approach to achieve 30-50% token reduction while maintaining ≥95% information preservation and seamless framework integration.
|
||||
|
||||
**Core Problems Solved**:
|
||||
- Resource constraint management during large-scale operations
|
||||
- Context usage optimization across MCP server coordination
|
||||
- Performance preservation during complex analysis workflows
|
||||
- Quality-gated compression with real-time effectiveness monitoring
|
||||
|
||||
**Framework Value**:
|
||||
- Evidence-based efficiency with measurable outcomes
|
||||
- Adaptive intelligence based on task complexity and persona domains
|
||||
- Progressive enhancement through 5-level compression strategy
|
||||
- Seamless integration with SuperClaude's quality gates and orchestration
|
||||
|
||||
## Core Framework
|
||||
|
||||
### 1. Symbol Systems Framework
|
||||
- **Core Logic & Flow**: Mathematical and logical relationships using →, ⇒, ←, ⇄, &, |, :, », ∴, ∵, ≡, ≈, ≠
|
||||
- **Status & Progress**: Visual progress indicators using ✅, ❌, ⚠️, ℹ️, 🔄, ⏳, 🚨, 🎯, 📊, 💡
|
||||
- **Technical Domains**: Domain-specific symbols using ⚡, 🔍, 🔧, 🛡️, 📦, 🎨, 🌐, 📱, 🏗️, 🧩
|
||||
- **Context-Aware Selection**: Persona-aware symbol selection based on active domain expertise
|
||||
|
||||
### 2. Abbreviation Systems Framework
|
||||
- **System & Architecture**: cfg, impl, arch, perf, ops, env
|
||||
- **Development Process**: req, deps, val, test, docs, std
|
||||
- **Quality & Analysis**: qual, sec, err, rec, sev, opt
|
||||
- **Context-Sensitive Application**: Intelligent abbreviation based on user familiarity and technical domain
|
||||
|
||||
### 3. Intelligent Token Optimizer Framework
|
||||
- **Evidence-Based Compression**: All techniques validated with metrics and effectiveness tracking
|
||||
- **Persona-Aware Optimization**: Domain-specific compression strategies aligned with specialist requirements
|
||||
- **Structural Optimization**: Advanced formatting and organization for maximum token efficiency
|
||||
- **Quality Validation**: Real-time compression effectiveness monitoring with preservation targets
|
||||
|
||||
### 4. Advanced Token Management Framework
|
||||
- **5-Level Compression Strategy**: Minimal (0-40%) → Efficient (40-70%) → Compressed (70-85%) → Critical (85-95%) → Emergency (95%+)
|
||||
- **Adaptive Compression Levels**: Context-aware compression based on task complexity, persona domain, and user familiarity
|
||||
- **Quality-Gated Validation**: Validation against ≥95% information preservation targets
|
||||
- **MCP Integration**: Coordinated caching and optimization across server calls
|
||||
|
||||
### 5. Selective Compression Framework
|
||||
- **Framework Exclusion**: Complete exclusion of SuperClaude framework directories and components
|
||||
- **Session Data Optimization**: Apply compression only to session operational data and working artifacts
|
||||
- **User Content Preservation**: Maintain full fidelity for project files, user documentation, configurations, outputs
|
||||
- **Path-Based Protection**: Automatic exclusion of framework paths with minimal scope compression
|
||||
|
||||
## Activation Patterns
|
||||
|
||||
### Automatic Activation
|
||||
Token Efficiency Mode auto-activates when SuperClaude detects:
|
||||
|
||||
1. **Resource Constraint Indicators**: Context usage >75%, memory pressure, large-scale operations
|
||||
2. **Performance Optimization Needs**: Complex analysis workflows, multi-server coordination, extended sessions
|
||||
3. **Efficiency Request Patterns**: User requests for brevity, compressed output, token optimization
|
||||
4. **Quality-Performance Balance**: Operations requiring efficiency without quality compromise
|
||||
5. **Framework Integration Triggers**: Wave coordination, persona intelligence, quality gate validation
|
||||
|
||||
### Manual Activation
|
||||
- **Primary Flag**: `--uc` or `--ultracompressed`
|
||||
- **Context**: When users explicitly request 30-50% token reduction with symbol systems
|
||||
- **Integration**: Works with all SuperClaude commands and MCP servers for optimization
|
||||
- **Fallback Control**: `--no-uc` disables automatic activation when full verbosity needed
|
||||
|
||||
## Token Optimization Framework
|
||||
|
||||
### Symbol System
|
||||
|
||||
#### Core Logic & Flow
|
||||
| Symbol | Meaning | Example |
|
||||
|--------|---------|----------|
|
||||
| → | leads to, implies | `auth.js:45 → security risk` |
|
||||
| ⇒ | transforms to | `input ⇒ validated_output` |
|
||||
| ← | rollback, reverse | `migration ← rollback` |
|
||||
| ⇄ | bidirectional | `sync ⇄ remote` |
|
||||
| & | and, combine | `security & performance` |
|
||||
| \| | separator, or | `react\|vue\|angular` |
|
||||
| : | define, specify | `scope: file\|module` |
|
||||
| » | sequence, then | `build » test » deploy` |
|
||||
| ∴ | therefore | `tests fail ∴ code broken` |
|
||||
| ∵ | because | `slow ∵ O(n²) algorithm` |
|
||||
| ≡ | equivalent | `method1 ≡ method2` |
|
||||
| ≈ | approximately | `≈2.5K tokens` |
|
||||
| ≠ | not equal | `actual ≠ expected` |
|
||||
|
||||
#### Status & Progress
|
||||
| Symbol | Meaning | Action |
|
||||
|--------|---------|--------|
|
||||
| ✅ | completed, passed | None |
|
||||
| ❌ | failed, error | Immediate |
|
||||
| ⚠️ | warning | Review |
|
||||
| ℹ️ | information | Awareness |
|
||||
| 🔄 | in progress | Monitor |
|
||||
| ⏳ | waiting, pending | Schedule |
|
||||
| 🚨 | critical, urgent | Immediate |
|
||||
| 🎯 | target, goal | Execute |
|
||||
| 📊 | metrics, data | Analyze |
|
||||
| 💡 | insight, learning | Apply |
|
||||
|
||||
#### Technical Domains
|
||||
| Symbol | Domain | Usage |
|
||||
|--------|---------|-------|
|
||||
| ⚡ | Performance | Speed, optimization |
|
||||
| 🔍 | Analysis | Search, investigation |
|
||||
| 🔧 | Configuration | Setup, tools |
|
||||
| 🛡️ | Security | Protection |
|
||||
| 📦 | Deployment | Package, bundle |
|
||||
| 🎨 | Design | UI, frontend |
|
||||
| 🌐 | Network | Web, connectivity |
|
||||
| 📱 | Mobile | Responsive |
|
||||
| 🏗️ | Architecture | System structure |
|
||||
| 🧩 | Components | Modular design |
|
||||
|
||||
### Abbreviation Systems
|
||||
|
||||
#### System & Architecture
|
||||
- `cfg` configuration, settings
|
||||
- `impl` implementation, code structure
|
||||
- `arch` architecture, system design
|
||||
- `perf` performance, optimization
|
||||
- `ops` operations, deployment
|
||||
- `env` environment, runtime context
|
||||
|
||||
#### Development Process
|
||||
- `req` requirements, dependencies
|
||||
- `deps` dependencies, packages
|
||||
- `val` validation, verification
|
||||
- `test` testing, quality assurance
|
||||
- `docs` documentation, guides
|
||||
- `std` standards, conventions
|
||||
|
||||
#### Quality & Analysis
|
||||
- `qual` quality, maintainability
|
||||
- `sec` security, safety measures
|
||||
- `err` error, exception handling
|
||||
- `rec` recovery, resilience
|
||||
- `sev` severity, priority level
|
||||
- `opt` optimization, improvement
|
||||
|
||||
### Intelligent Compression Strategies
|
||||
|
||||
**Adaptive Compression Levels**:
|
||||
1. **Minimal** (0-40%): Full detail, persona-optimized clarity
|
||||
2. **Efficient** (40-70%): Balanced compression with domain awareness
|
||||
3. **Compressed** (70-85%): Aggressive optimization with quality gates
|
||||
4. **Critical** (85-95%): Maximum compression preserving essential context
|
||||
5. **Emergency** (95%+): Ultra-compression with information validation
|
||||
|
||||
### Enhanced Techniques
|
||||
- **Persona-Aware Symbols**: Domain-specific symbol selection based on active persona
|
||||
- **Context-Sensitive Abbreviations**: Intelligent abbreviation based on user familiarity and technical domain
|
||||
- **Structural Optimization**: Advanced formatting for token efficiency
|
||||
- **Quality Validation**: Real-time compression effectiveness monitoring
|
||||
- **MCP Integration**: Coordinated caching and optimization across server calls
|
||||
|
||||
### Selective Compression Techniques
|
||||
- **Path-Based Exclusion**: Complete exclusion of SuperClaude framework directories
|
||||
- **Session Data Optimization**: Compression applied only to session operational data
|
||||
- **Framework Protection**: Zero compression for all SuperClaude components and configurations
|
||||
- **User Content Protection**: Zero compression for project code, user docs, configurations, custom content
|
||||
- **Minimal Scope Compression**: Limited to session metadata, checkpoints, cache, and working artifacts
|
||||
|
||||
## Framework Integration
|
||||
|
||||
### SuperClaude Mode Coordination
|
||||
- **Wave Coordination**: Real-time token monitoring with <100ms decisions during wave orchestration
|
||||
- **Persona Intelligence**: Domain-specific compression strategies (architect: clarity-focused, performance: efficiency-focused)
|
||||
- **Performance Monitoring**: Integration with performance targets and resource management thresholds
|
||||
|
||||
### MCP Server Integration
|
||||
- **Context7**: Cache documentation lookups (2-5K tokens/query saved), optimized delivery patterns
|
||||
- **Sequential**: Reuse reasoning analysis results with compression awareness, coordinated analysis
|
||||
- **Magic**: Store UI component patterns with optimized delivery, framework-specific compression
|
||||
- **Playwright**: Batch operations with intelligent result compression, cross-browser optimization
|
||||
|
||||
### Quality Gate Integration
|
||||
- **Step 2.5**: Compression validation during token efficiency assessment
|
||||
- **Step 7.5**: Quality preservation verification in final validation
|
||||
- **Continuous**: Real-time compression effectiveness monitoring and adjustment
|
||||
- **Evidence Tracking**: Compression effectiveness metrics and continuous improvement
|
||||
|
||||
### Command Integration
|
||||
- **All Commands**: Universal optimization layer applied across SuperClaude command execution
|
||||
- **Resource-Intensive Operations**: Automatic activation during large-scale file processing
|
||||
- **Analysis Commands**: Balanced compression maintaining analysis depth and clarity
|
||||
|
||||
## Communication Style
|
||||
|
||||
### Optimized Communication Patterns
|
||||
1. **Symbol-Enhanced Clarity**: Use symbol systems to convey complex relationships efficiently
|
||||
2. **Context-Aware Compression**: Adapt compression level based on user expertise and domain familiarity
|
||||
3. **Quality-Preserved Efficiency**: Maintain SuperClaude's communication standards while optimizing token usage
|
||||
4. **Evidence-Based Feedback**: Provide compression metrics and effectiveness indicators when relevant
|
||||
|
||||
### Resource Management Communication
|
||||
1. **Threshold Awareness**: Communicate resource state through zone-based indicators
|
||||
2. **Progressive Enhancement**: Scale compression based on resource constraints and performance targets
|
||||
3. **Framework Compliance**: Maintain consistent communication patterns across all optimization levels
|
||||
4. **Performance Transparency**: Share optimization benefits and quality preservation metrics
|
||||
|
||||
## Configuration
|
||||
|
||||
```yaml
|
||||
token_efficiency_mode:
|
||||
activation:
|
||||
automatic: true
|
||||
confidence_threshold: 0.75
|
||||
detection_patterns:
|
||||
resource_constraints: ["context usage >75%", "large-scale operations", "memory pressure"]
|
||||
optimization_requests: ["user requests brevity", "--uc flag", "compressed output"]
|
||||
performance_needs: ["multi-server coordination", "extended sessions", "complex analysis"]
|
||||
|
||||
compression_framework:
|
||||
levels:
|
||||
minimal: 0.40
|
||||
efficient: 0.70
|
||||
compressed: 0.85
|
||||
critical: 0.95
|
||||
emergency: 0.99
|
||||
quality_preservation_target: 0.95
|
||||
processing_time_limit_ms: 100
|
||||
|
||||
selective_compression:
|
||||
enabled: true
|
||||
content_classification:
|
||||
framework_exclusions:
|
||||
- "/SuperClaude/SuperClaude/" # Complete SuperClaude framework
|
||||
- "~/.claude/" # User Claude configuration
|
||||
- ".claude/" # Local Claude configuration
|
||||
- "SuperClaude/*" # All SuperClaude directories
|
||||
compressible_content_patterns:
|
||||
- "session_metadata" # Session operational data only
|
||||
- "checkpoint_data" # Session checkpoints
|
||||
- "cache_content" # Temporary cache data
|
||||
- "working_artifacts" # Analysis processing results
|
||||
preserve_patterns:
|
||||
- "framework_*" # All framework components
|
||||
- "configuration_*" # All configuration files
|
||||
- "project_files" # User project content
|
||||
- "user_documentation" # User-created documentation
|
||||
- "source_code" # All source code
|
||||
compression_strategy:
|
||||
session_data: "efficient" # 40-70% compression for session data only
|
||||
framework_content: "preserve" # 0% compression - complete exclusion
|
||||
user_content: "preserve" # 0% compression - complete preservation
|
||||
fallback: "preserve" # When classification uncertain
|
||||
|
||||
symbol_systems:
|
||||
core_logic_flow_enabled: true
|
||||
status_progress_enabled: true
|
||||
technical_domains_enabled: true
|
||||
persona_aware_selection: true
|
||||
|
||||
abbreviation_systems:
|
||||
system_architecture_enabled: true
|
||||
development_process_enabled: true
|
||||
quality_analysis_enabled: true
|
||||
context_sensitive_application: true
|
||||
|
||||
resource_management:
|
||||
green_zone: 0.60
|
||||
yellow_zone: 0.75
|
||||
orange_zone: 0.85
|
||||
red_zone: 0.95
|
||||
critical_zone: 0.99
|
||||
|
||||
framework_integration:
|
||||
mcp_servers: [context7, sequential, magic, playwright]
|
||||
quality_gates: [compression_validation, quality_preservation, token_monitoring]
|
||||
mode_coordination: [wave_coordination, persona_intelligence, performance_monitoring]
|
||||
|
||||
behavioral_settings:
|
||||
evidence_based_optimization: true
|
||||
adaptive_intelligence: true
|
||||
progressive_enhancement: true
|
||||
quality_gated_validation: true
|
||||
|
||||
performance:
|
||||
target_compression_ratio: 0.40
|
||||
quality_preservation_score: 0.95
|
||||
processing_time_ms: 100
|
||||
integration_compliance: seamless
|
||||
```
|
||||
|
||||
## Integration Ecosystem
|
||||
|
||||
### SuperClaude Framework Compliance
|
||||
|
||||
```yaml
|
||||
framework_integration:
|
||||
quality_gates: [compression_validation, quality_preservation, token_monitoring]
|
||||
mcp_coordination: [context7_caching, sequential_reuse, magic_optimization, playwright_batching]
|
||||
mode_orchestration: [wave_coordination, persona_intelligence, performance_monitoring]
|
||||
document_persistence: [compression_metrics, effectiveness_tracking, optimization_patterns]
|
||||
|
||||
behavioral_consistency:
|
||||
communication_patterns: [symbol_enhanced_clarity, context_aware_compression, quality_preserved_efficiency]
|
||||
performance_standards: [30_50_percent_reduction, 95_percent_preservation, 100ms_processing]
|
||||
quality_enforcement: [evidence_based_validation, adaptive_intelligence, progressive_enhancement]
|
||||
integration_protocols: [seamless_superclaude_compliance, coordinated_mcp_optimization]
|
||||
```
|
||||
|
||||
### Cross-Mode Behavioral Coordination
|
||||
|
||||
```yaml
|
||||
mode_interactions:
|
||||
wave_coordination: real_time_token_monitoring_with_compression_decisions
|
||||
persona_intelligence: domain_specific_compression_strategies_aligned_with_expertise
|
||||
performance_monitoring: resource_threshold_integration_and_optimization_tracking
|
||||
|
||||
orchestration_principles:
|
||||
behavioral_consistency: symbol_systems_and_abbreviations_maintained_across_modes
|
||||
configuration_harmony: shared_compression_settings_and_quality_targets
|
||||
quality_enforcement: superclaude_standards_preserved_during_optimization
|
||||
performance_optimization: coordinated_efficiency_gains_through_intelligent_compression
|
||||
```
|
||||
|
||||
## Related Documentation
|
||||
|
||||
- **Framework Reference**: ORCHESTRATOR.md for intelligent routing and resource management
|
||||
- **Integration Patterns**: MCP server documentation for optimization coordination
|
||||
- **Quality Standards**: Quality gates integration for compression validation
|
||||
- **Performance Targets**: Performance monitoring integration for efficiency tracking
|
||||
Reference in New Issue
Block a user