Christoph Wagner 5ad0700b41 refactor: Consolidate repository structure - flatten from workspace pattern

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>

2025-11-23 10:05:26 +01:00

3.5 KiB

Raw Permalink Blame History

bottleneck detect

Analyze performance bottlenecks in swarm operations and suggest optimizations.

Usage

npx claude-flow bottleneck detect [options]

Options

--swarm-id, -s <id> - Analyze specific swarm (default: current)
--time-range, -t <range> - Analysis period: 1h, 24h, 7d, all (default: 1h)
--threshold <percent> - Bottleneck threshold percentage (default: 20)
--export, -e <file> - Export analysis to file
--fix - Apply automatic optimizations

Examples

Basic bottleneck detection

npx claude-flow bottleneck detect

Analyze specific swarm

npx claude-flow bottleneck detect --swarm-id swarm-123

Last 24 hours with export

npx claude-flow bottleneck detect -t 24h -e bottlenecks.json

Auto-fix detected issues

npx claude-flow bottleneck detect --fix --threshold 15

Metrics Analyzed

Communication Bottlenecks

Message queue delays
Agent response times
Coordination overhead
Memory access patterns

Processing Bottlenecks

Task completion times
Agent utilization rates
Parallel execution efficiency
Resource contention

Memory Bottlenecks

Cache hit rates
Memory access patterns
Storage I/O performance
Neural pattern loading

Network Bottlenecks

API call latency
MCP communication delays
External service timeouts
Concurrent request limits

Output Format

🔍 Bottleneck Analysis Report
━━━━━━━━━━━━━━━━━━━━━━━━━━━

📊 Summary
├── Time Range: Last 1 hour
├── Agents Analyzed: 6
├── Tasks Processed: 42
└── Critical Issues: 2

🚨 Critical Bottlenecks
1. Agent Communication (35% impact)
   └── coordinator → coder-1 messages delayed by 2.3s avg

2. Memory Access (28% impact)
   └── Neural pattern loading taking 1.8s per access

⚠️ Warning Bottlenecks
1. Task Queue (18% impact)
   └── 5 tasks waiting > 10s for assignment

💡 Recommendations
1. Switch to hierarchical topology (est. 40% improvement)
2. Enable memory caching (est. 25% improvement)
3. Increase agent concurrency to 8 (est. 20% improvement)

✅ Quick Fixes Available
Run with --fix to apply:
- Enable smart caching
- Optimize message routing
- Adjust agent priorities

Automatic Fixes

When using --fix, the following optimizations may be applied:

Topology Optimization
- Switch to more efficient topology
- Adjust communication patterns
- Reduce coordination overhead
Caching Enhancement
- Enable memory caching
- Optimize cache strategies
- Preload common patterns
Concurrency Tuning
- Adjust agent counts
- Optimize parallel execution
- Balance workload distribution
Priority Adjustment
- Reorder task queues
- Prioritize critical paths
- Reduce wait times

Performance Impact

Typical improvements after bottleneck resolution:

Communication: 30-50% faster message delivery
Processing: 20-40% reduced task completion time
Memory: 40-60% fewer cache misses
Overall: 25-45% performance improvement

Integration with Claude Code

// Check for bottlenecks in Claude Code
mcp__claude-flow__bottleneck_detect {
  timeRange: "1h",
  threshold: 20,
  autoFix: false
}

3.5 KiB Raw Permalink Blame History