grtninja Shockwave Voice Command Governance
Use this skill for Project Shockwave's voice-command matrix and surface-parity lane.
Workflow
- Start from the current command matrix, not from ad hoc parser guesses.
- Compare parser order, direct fast paths, and JSON fallback behavior to the visible UI controls.
- Keep source-aware command filtering explicit for music, radio, maps, camera, telemetry, and memory.
- Track missing command families as deliberate gaps rather than hidden regressions.
- Re-run a bounded voice-command parity proof after updates.
Required Evidence
- command family touched
- parser or UI surface touched
- source-aware filtering rule checked
- parity or missing-gap note after the change
Guardrails
- Do not expose voice commands that the active source cannot honor.
- Do not leave touch-only controls undocumented if they should have voice analogs.
- Keep radio and music handoff explicit.
- Fail closed if parser order creates ambiguous or unsafe command capture.
Best-Fit Companion Skills
$shockwave-dashboard-ops$distributed-voice-plane-governance$catalog-snapshot-consistency$docs-alignment-lock
Scope Boundary
Use this skill only for Shockwave voice command parity and command-surface governance.
For startup or dashboard shell behavior alone, route through $shockwave-dashboard-ops.