What problem does it solve? Building a local wake-word voice assistant on Windows involves many fragile pieces — openWakeWord detection, faster-whisper STT, LLM routing, Piper TTS, and PortAudio quirks — and this Skill captures the verified working configuration plus every pitfall that cost real debugging time. ## Core Features & Use Cases - Verified voice pipeline: Documents the exact working wake→STT→LLM→TTS flow using openWakeWord, faster-whisper tiny, Hermes Agent routing, and Piper jarvis-high voice. - Windows-specific fixes: Covers .bat launch gotchas (PYTHONPATH, escaping, timeout hijacking), persistent OutputStream for TTS latency, mic device fallback loops, and log-file IPC instead of subprocess.PIPE. - Web control panel: Details the FastAPI + WebSocket server with a Canvas2D arc-reactor orb, safe config PATCH/GET editing, and Playwright visual verification. - Use Case: When asked to add a feature or fix latency in the JARVIS assistant, apply the documented patterns — e.g., sentence-by-sentence TTS streaming and echo-prevention mic draining — instead of rediscovering them. ## Quick Start Use the jarvis-voice-pipeline skill to diagnose why the JARVIS assistant's wake acknowledgment feels slow and reduce its TTS onset latency.