pi-voice

Pi package development best practices and patterns for pi-voice. Use when planning, editing, implementing, or reviewing pi-voice extension code — adding tools, commands, event handlers, TUI components, or modifying the server. Also use when the user asks about extension architecture, pi SDK APIs, or "how should I implement" a pi-voice feature. Do not use for running tests (use pi-test skill) or server-only changes.

Test pi-voice TUI, tts tool, and auto-TTS using pilotty for PTY-based terminal automation. Use when the user wants to test, verify, or validate the /voice command UI, the tts tool, auto-TTS event handling, or any pi-voice extension behavior. Also use when the user says "test the TUI", "run e2e tests", "test voice", "run pilotty", or asks about testing pi-voice. Do not use for server integration tests (npm test), linting, type checking, or server-only testing.

Verify pi-voice development environment setup. Use when the user says "init", "setup", "check environment", or asks to verify their development environment. This project is already initialized — the skill performs a quick health check rather than a full template setup. Do not use for general development tasks or running tests.