6ed69a3d48
Major changes: - Organized Python v1 implementation into v1/ subdirectory - Created Rust workspace with 9 modular crates: - wifi-densepose-core: Core types, traits, errors - wifi-densepose-signal: CSI processing, phase sanitization, FFT - wifi-densepose-nn: Neural network inference (ONNX/Candle/tch) - wifi-densepose-api: Axum-based REST/WebSocket API - wifi-densepose-db: SQLx database layer - wifi-densepose-config: Configuration management - wifi-densepose-hardware: Hardware abstraction - wifi-densepose-wasm: WebAssembly bindings - wifi-densepose-cli: Command-line interface Documentation: - ADR-001: Workspace structure - ADR-002: Signal processing library selection - ADR-003: Neural network inference strategy - DDD domain model with bounded contexts Testing: - 69 tests passing across all crates - Signal processing: 45 tests - Neural networks: 21 tests - Core: 3 doc tests Performance targets: - 10x faster CSI processing (~0.5ms vs ~5ms) - 5x lower memory usage (~100MB vs ~500MB) - WASM support for browser deployment
55 lines
1.2 KiB
Markdown
55 lines
1.2 KiB
Markdown
# SPARC Debugger Mode
|
|
|
|
## Purpose
|
|
Systematic debugging with TodoWrite and Memory integration.
|
|
|
|
## Activation
|
|
|
|
### Option 1: Using MCP Tools (Preferred in Claude Code)
|
|
```javascript
|
|
mcp__claude-flow__sparc_mode {
|
|
mode: "debugger",
|
|
task_description: "fix authentication issues",
|
|
options: {
|
|
verbose: true,
|
|
trace: true
|
|
}
|
|
}
|
|
```
|
|
|
|
### Option 2: Using NPX CLI (Fallback when MCP not available)
|
|
```bash
|
|
# Use when running from terminal or MCP tools unavailable
|
|
npx claude-flow sparc run debugger "fix authentication issues"
|
|
|
|
# For alpha features
|
|
npx claude-flow@alpha sparc run debugger "fix authentication issues"
|
|
```
|
|
|
|
### Option 3: Local Installation
|
|
```bash
|
|
# If claude-flow is installed locally
|
|
./claude-flow sparc run debugger "fix authentication issues"
|
|
```
|
|
|
|
## Core Capabilities
|
|
- Issue reproduction
|
|
- Root cause analysis
|
|
- Stack trace analysis
|
|
- Memory leak detection
|
|
- Performance bottleneck identification
|
|
|
|
## Debugging Workflow
|
|
1. Create debugging plan with TodoWrite
|
|
2. Systematic issue investigation
|
|
3. Store findings in Memory
|
|
4. Track fix progress
|
|
5. Verify resolution
|
|
|
|
## Tools Integration
|
|
- Error log analysis
|
|
- Breakpoint simulation
|
|
- Variable inspection
|
|
- Call stack tracing
|
|
- Memory profiling
|