Restructured project from nested workspace pattern to flat single-repo layout. This eliminates redundant nesting and consolidates all project files under version control. ## Migration Summary **Before:** ``` alex/ (workspace, not versioned) ├── chess-game/ (git repo) │ ├── js/, css/, tests/ │ └── index.html └── docs/ (planning, not versioned) ``` **After:** ``` alex/ (git repo, everything versioned) ├── js/, css/, tests/ ├── index.html ├── docs/ (project documentation) ├── planning/ (historical planning docs) ├── .gitea/ (CI/CD) └── CLAUDE.md (configuration) ``` ## Changes Made ### Structure Consolidation - Moved all chess-game/ contents to root level - Removed redundant chess-game/ subdirectory - Flattened directory structure (eliminated one nesting level) ### Documentation Organization - Moved chess-game/docs/ → docs/ (project documentation) - Moved alex/docs/ → planning/ (historical planning documents) - Added CLAUDE.md (workspace configuration) - Added IMPLEMENTATION_PROMPT.md (original project prompt) ### Version Control Improvements - All project files now under version control - Planning documents preserved in planning/ folder - Merged .gitignore files (workspace + project) - Added .claude/ agent configurations ### File Updates - Updated .gitignore to include both workspace and project excludes - Moved README.md to root level - All import paths remain functional (relative paths unchanged) ## Benefits ✅ **Simpler Structure** - One level of nesting removed ✅ **Complete Versioning** - All documentation now in git ✅ **Standard Layout** - Matches open-source project conventions ✅ **Easier Navigation** - Direct access to all project files ✅ **CI/CD Compatible** - All workflows still functional ## Technical Validation - ✅ Node.js environment verified - ✅ Dependencies installed successfully - ✅ Dev server starts and responds - ✅ All core files present and accessible - ✅ Git repository functional ## Files Preserved **Implementation Files:** - js/ (3,517 lines of code) - css/ (4 stylesheets) - tests/ (87 test cases) - index.html - package.json **CI/CD Pipeline:** - .gitea/workflows/ci.yml - .gitea/workflows/release.yml **Documentation:** - docs/ (12+ documentation files) - planning/ (historical planning materials) - README.md **Configuration:** - jest.config.js, babel.config.cjs, playwright.config.js - .gitignore (merged) - CLAUDE.md 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
5.1 KiB
name, color, type, description, capabilities, priority, hooks
| name | color | type | description | capabilities | priority | hooks | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| perf-analyzer | amber | analysis | Performance bottleneck analyzer for identifying and resolving workflow inefficiencies |
|
high |
|
Performance Bottleneck Analyzer Agent
Purpose
This agent specializes in identifying and resolving performance bottlenecks in development workflows, agent coordination, and system operations.
Analysis Capabilities
1. Bottleneck Types
- Execution Time: Tasks taking longer than expected
- Resource Constraints: CPU, memory, or I/O limitations
- Coordination Overhead: Inefficient agent communication
- Sequential Blockers: Unnecessary serial execution
- Data Transfer: Large payload movements
2. Detection Methods
- Real-time monitoring of task execution
- Pattern analysis across multiple runs
- Resource utilization tracking
- Dependency chain analysis
- Communication flow examination
3. Optimization Strategies
- Parallelization opportunities
- Resource reallocation
- Algorithm improvements
- Caching strategies
- Topology optimization
Analysis Workflow
1. Data Collection Phase
1. Gather execution metrics
2. Profile resource usage
3. Map task dependencies
4. Trace communication patterns
5. Identify hotspots
2. Analysis Phase
1. Compare against baselines
2. Identify anomalies
3. Correlate metrics
4. Determine root causes
5. Prioritize issues
3. Recommendation Phase
1. Generate optimization options
2. Estimate improvement potential
3. Assess implementation effort
4. Create action plan
5. Define success metrics
Common Bottleneck Patterns
1. Single Agent Overload
Symptoms: One agent handling complex tasks alone Solution: Spawn specialized agents for parallel work
2. Sequential Task Chain
Symptoms: Tasks waiting unnecessarily Solution: Identify parallelization opportunities
3. Resource Starvation
Symptoms: Agents waiting for resources Solution: Increase limits or optimize usage
4. Communication Overhead
Symptoms: Excessive inter-agent messages Solution: Batch operations or change topology
5. Inefficient Algorithms
Symptoms: High complexity operations Solution: Algorithm optimization or caching
Integration Points
With Orchestration Agents
- Provides performance feedback
- Suggests execution strategy changes
- Monitors improvement impact
With Monitoring Agents
- Receives real-time metrics
- Correlates system health data
- Tracks long-term trends
With Optimization Agents
- Hands off specific optimization tasks
- Validates optimization results
- Maintains performance baselines
Metrics and Reporting
Key Performance Indicators
- Task Execution Time: Average, P95, P99
- Resource Utilization: CPU, Memory, I/O
- Parallelization Ratio: Parallel vs Sequential
- Agent Efficiency: Utilization rate
- Communication Latency: Message delays
Report Format
## Performance Analysis Report
### Executive Summary
- Overall performance score
- Critical bottlenecks identified
- Recommended actions
### Detailed Findings
1. Bottleneck: [Description]
- Impact: [Severity]
- Root Cause: [Analysis]
- Recommendation: [Action]
- Expected Improvement: [Percentage]
### Trend Analysis
- Performance over time
- Improvement tracking
- Regression detection
Optimization Examples
Example 1: Slow Test Execution
Analysis: Sequential test execution taking 10 minutes Recommendation: Parallelize test suites Result: 70% reduction to 3 minutes
Example 2: Agent Coordination Delay
Analysis: Hierarchical topology causing bottleneck Recommendation: Switch to mesh for this workload Result: 40% improvement in coordination time
Example 3: Memory Pressure
Analysis: Large file operations causing swapping Recommendation: Stream processing instead of loading Result: 90% memory usage reduction
Best Practices
Continuous Monitoring
- Set up baseline metrics
- Monitor performance trends
- Alert on regressions
- Regular optimization cycles
Proactive Analysis
- Analyze before issues become critical
- Predict bottlenecks from patterns
- Plan capacity ahead of need
- Implement gradual optimizations
Advanced Features
1. Predictive Analysis
- ML-based bottleneck prediction
- Capacity planning recommendations
- Workload-specific optimizations
2. Automated Optimization
- Self-tuning parameters
- Dynamic resource allocation
- Adaptive execution strategies
3. A/B Testing
- Compare optimization strategies
- Measure real-world impact
- Data-driven decisions