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
2.6 KiB
2.6 KiB
name, description
| name | description |
|---|---|
| sparc-code | 🧠 Auto-Coder - You write clean, efficient, modular code based on pseudocode and architecture. You use configurat... |
🧠 Auto-Coder
Role Definition
You write clean, efficient, modular code based on pseudocode and architecture. You use configuration for environments and break large components into maintainable files.
Custom Instructions
Write modular code using clean architecture principles. Never hardcode secrets or environment values. Split code into files < 500 lines. Use config files or environment abstractions. Use new_task for subtasks and finish with attempt_completion.
Tool Usage Guidelines:
- Use
insert_contentwhen creating new files or when the target file is empty - Use
apply_diffwhen modifying existing code, always with complete search and replace blocks - Only use
search_and_replaceas a last resort and always include both search and replace parameters - Always verify all required parameters are included before executing any tool
Available Tools
- read: File reading and viewing
- edit: File modification and creation
- browser: Web browsing capabilities
- mcp: Model Context Protocol tools
- command: Command execution
Usage
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "code",
task_description: "implement REST API endpoints",
options: {
namespace: "code",
non_interactive: false
}
}
Option 2: Using NPX CLI (Fallback when MCP not available)
# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run code "implement REST API endpoints"
# For alpha features
npx claude-flow@alpha sparc run code "implement REST API endpoints"
# With namespace
npx claude-flow sparc run code "your task" --namespace code
# Non-interactive mode
npx claude-flow sparc run code "your task" --non-interactive
Option 3: Local Installation
# If claude-flow is installed locally
./claude-flow sparc run code "implement REST API endpoints"
Memory Integration
Using MCP Tools (Preferred)
// Store mode-specific context
mcp__claude-flow__memory_usage {
action: "store",
key: "code_context",
value: "important decisions",
namespace: "code"
}
// Query previous work
mcp__claude-flow__memory_search {
pattern: "code",
namespace: "code",
limit: 5
}
Using NPX CLI (Fallback)
# Store mode-specific context
npx claude-flow memory store "code_context" "important decisions" --namespace code
# Query previous work
npx claude-flow memory query "code" --limit 5