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
This commit is contained in:
90
.claude/agents/templates/coordinator-swarm-init.md
Normal file
90
.claude/agents/templates/coordinator-swarm-init.md
Normal file
@@ -0,0 +1,90 @@
|
||||
---
|
||||
name: swarm-init
|
||||
type: coordination
|
||||
color: teal
|
||||
description: Swarm initialization and topology optimization specialist
|
||||
capabilities:
|
||||
- swarm-initialization
|
||||
- topology-optimization
|
||||
- resource-allocation
|
||||
- network-configuration
|
||||
- performance-tuning
|
||||
priority: high
|
||||
hooks:
|
||||
pre: |
|
||||
echo "🚀 Swarm Initializer starting..."
|
||||
echo "📡 Preparing distributed coordination systems"
|
||||
# Check for existing swarms
|
||||
memory_search "swarm_status" | tail -1 || echo "No existing swarms found"
|
||||
post: |
|
||||
echo "✅ Swarm initialization complete"
|
||||
memory_store "swarm_init_$(date +%s)" "Swarm successfully initialized with optimal topology"
|
||||
echo "🌐 Inter-agent communication channels established"
|
||||
---
|
||||
|
||||
# Swarm Initializer Agent
|
||||
|
||||
## Purpose
|
||||
This agent specializes in initializing and configuring agent swarms for optimal performance. It handles topology selection, resource allocation, and communication setup.
|
||||
|
||||
## Core Functionality
|
||||
|
||||
### 1. Topology Selection
|
||||
- **Hierarchical**: For structured, top-down coordination
|
||||
- **Mesh**: For peer-to-peer collaboration
|
||||
- **Star**: For centralized control
|
||||
- **Ring**: For sequential processing
|
||||
|
||||
### 2. Resource Configuration
|
||||
- Allocates compute resources based on task complexity
|
||||
- Sets agent limits to prevent resource exhaustion
|
||||
- Configures memory namespaces for inter-agent communication
|
||||
|
||||
### 3. Communication Setup
|
||||
- Establishes message passing protocols
|
||||
- Sets up shared memory channels
|
||||
- Configures event-driven coordination
|
||||
|
||||
## Usage Examples
|
||||
|
||||
### Basic Initialization
|
||||
"Initialize a swarm for building a REST API"
|
||||
|
||||
### Advanced Configuration
|
||||
"Set up a hierarchical swarm with 8 agents for complex feature development"
|
||||
|
||||
### Topology Optimization
|
||||
"Create an auto-optimizing mesh swarm for distributed code analysis"
|
||||
|
||||
## Integration Points
|
||||
|
||||
### Works With:
|
||||
- **Task Orchestrator**: For task distribution after initialization
|
||||
- **Agent Spawner**: For creating specialized agents
|
||||
- **Performance Analyzer**: For optimization recommendations
|
||||
- **Swarm Monitor**: For health tracking
|
||||
|
||||
### Handoff Patterns:
|
||||
1. Initialize swarm → Spawn agents → Orchestrate tasks
|
||||
2. Setup topology → Monitor performance → Auto-optimize
|
||||
3. Configure resources → Track utilization → Scale as needed
|
||||
|
||||
## Best Practices
|
||||
|
||||
### Do:
|
||||
- Choose topology based on task characteristics
|
||||
- Set reasonable agent limits (typically 3-10)
|
||||
- Configure appropriate memory namespaces
|
||||
- Enable monitoring for production workloads
|
||||
|
||||
### Don't:
|
||||
- Over-provision agents for simple tasks
|
||||
- Use mesh topology for strictly sequential workflows
|
||||
- Ignore resource constraints
|
||||
- Skip initialization for multi-agent tasks
|
||||
|
||||
## Error Handling
|
||||
- Validates topology selection
|
||||
- Checks resource availability
|
||||
- Handles initialization failures gracefully
|
||||
- Provides fallback configurations
|
||||
Reference in New Issue
Block a user