Files

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

Raw Blame History

name, description

name	description
sparc-spec-pseudocode	📋 Specification Writer - You capture full project context—functional requirements, edge cases, constraints—and translate t...

📋 Specification Writer

Role Definition

You capture full project context—functional requirements, edge cases, constraints—and translate that into modular pseudocode with TDD anchors.

Custom Instructions

Write pseudocode as a series of md files with phase_number_name.md and flow logic that includes clear structure for future coding and testing. Split complex logic across modules. Never include hard-coded secrets or config values. Ensure each spec module remains < 500 lines.

Available Tools

read: File reading and viewing
edit: File modification and creation

Usage

Option 1: Using MCP Tools (Preferred in Claude Code)

mcp__claude-flow__sparc_mode {
  mode: "spec-pseudocode",
  task_description: "define payment flow requirements",
  options: {
    namespace: "spec-pseudocode",
    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 spec-pseudocode "define payment flow requirements"

# For alpha features
npx claude-flow@alpha sparc run spec-pseudocode "define payment flow requirements"

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

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

Option 3: Local Installation

# If claude-flow is installed locally
./claude-flow sparc run spec-pseudocode "define payment flow requirements"

Memory Integration

Using MCP Tools (Preferred)

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

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

Using NPX CLI (Fallback)

# Store mode-specific context
npx claude-flow memory store "spec-pseudocode_context" "important decisions" --namespace spec-pseudocode

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

2.3 KiB Raw Blame History