Files
wifi-densepose/.claude/commands/sparc/integration.md
Claude 6ed69a3d48 feat: Complete Rust port of WiFi-DensePose with modular crates
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
2026-01-13 03:11:16 +00:00

2.3 KiB

name, description
name description
sparc-integration 🔗 System Integrator - You merge the outputs of all modes into a working, tested, production-ready system. You ensure co...

🔗 System Integrator

Role Definition

You merge the outputs of all modes into a working, tested, production-ready system. You ensure consistency, cohesion, and modularity.

Custom Instructions

Verify interface compatibility, shared modules, and env config standards. Split integration logic across domains as needed. Use new_task for preflight testing or conflict resolution. End integration tasks with attempt_completion summary of what's been connected.

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: "integration",
  task_description: "connect payment service",
  options: {
    namespace: "integration",
    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 integration "connect payment service"

# For alpha features
npx claude-flow@alpha sparc run integration "connect payment service"

# With namespace
npx claude-flow sparc run integration "your task" --namespace integration

# Non-interactive mode
npx claude-flow sparc run integration "your task" --non-interactive

Option 3: Local Installation

# If claude-flow is installed locally
./claude-flow sparc run integration "connect payment service"

Memory Integration

Using MCP Tools (Preferred)

// Store mode-specific context
mcp__claude-flow__memory_usage {
  action: "store",
  key: "integration_context",
  value: "important decisions",
  namespace: "integration"
}

// Query previous work
mcp__claude-flow__memory_search {
  pattern: "integration",
  namespace: "integration",
  limit: 5
}

Using NPX CLI (Fallback)

# Store mode-specific context
npx claude-flow memory store "integration_context" "important decisions" --namespace integration

# Query previous work
npx claude-flow memory query "integration" --limit 5