debug-voice
Adds logging so a Grok voice session can be read after the fact, then fixes the app from that evidence.
- Kind
- Skill
- Works with
- Cursor
- Source
- cursor/plugins @ 9580c23696ac
- Path
- grok-voice/skills/debug-voice/SKILL.md
- License
- MIT
- Jobs
- Debugging
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# Debug Voice Make a voice session readable after the fact, then fix from evidence. The agent cannot hear the app; the log is its ears, the user is its judge. No audio, no tokens, never in prod. Works for any stack. The pipeline is a small contract (below); implement it in whatever the app already uses. ## Workflow 1. **Map** the app (read only). 2. **Plan**: write the change list, show it, **stop**. Nothing is edited until the user aligns. 3. **Install** the agreed pieces in the app's language, framework, and conventions. 4. **Verify** the sink, hand the app to the user. 5. **Fix loop** from the log. ## 1. Map Find, and note the paths: - Voice client: where realtime events are received and sent, mic capture, audio playback, token fetch. - Server: framework, how routes are declared, where shared server code lives, how env is read, what "production" means here. - Conventions: language(s), module system, formatter, where scripts or tasks live (`package.json`, `Makefile`, `pyproject`, `justfile`), `.gitignore`. - Client kind: browser, mobile, desktop, CLI. A non-browser client still POSTs the same JSON; a single-process app can skip HTTP and append to the file directly. …