Skip to main content

tts-integration

Add or modify text-to-speech providers in assistant-api with transport-aware behavior (WS/SSE/SDK/HTTP), packet lifecycle correctness, and UI/provider wiring.

설치로 이동

소스 정보

저장소
rapidaai/voice-ai
최근 소스 활동
2026년 8월 23일 07:23
감지된 SKILL.md 언어
영어
스타
733
포크
120

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
6 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
tts-integration
description
Add or modify text-to-speech providers in assistant-api with transport-aware behavior (WS/SSE/SDK/HTTP), packet lifecycle correctness, and UI/provider wiring.
# TTS Integration Skill ## Mission Integrate TTS providers with correct stream/flush/interruption lifecycle and stable `tts_latency_ms` metrics. ## Inputs expected from user 1. Output transport: WS, SSE/chunked HTTP, SDK callback, or HTTP flush. 2. Voice/model requirements. 3. Provider output format constraints. If missing: - Choose closest transport baseline and preserve existing packet behavior. ## Hard boundaries In scope: - `api/assistant-api/internal/transformer/<provider>/tts.go` (+ option/normalizer helpers) - `api/assistant-api/internal/transformer/transformer.go` - optional shared contracts: `tts_transformer.go`, `packet.go` - provider TTS metadata and UI components Out of scope: - STT-only internals - telephony internals - EOS/VAD internals ## Packet contract Input packets: - `LLMResponseDeltaPacket` - `LLMResponseDonePacket` - `InterruptionPacket` Required outputs: - `TextToSpeechAudioPacket` - `TextToSpeechEndPacket` - `ConversationEventPacket{Name:"tts", ...}` - `MessageMetricPacket{Name:"tts_latency_ms"}` once per utterance ## Implementation workflow 1. Pick transport baseline (`deepgram`/`rime`/`sarvam`, `minimax`, `azure`/`google`, `aws`). 2. Implement provider package. 3. Register in TTS factory switch. 4. Wire UI provider voice/model config. 5. Verify interruption clears pending state correctly. 6. Add provider + integration tests. ## Governed lifecycle - Classify work as Fast, Standard, or Governed using `DEVELOPMENT_PROCESS.md`; use the full gated lifecycle only for Governed work. - This skill operates only in its assigned phase and path ownership; it may not approve its own plan or code review. - Governed implementation starts only from a coordinator-attested approved plan; Fast and Standard work follows its lighter documented lifecycle. - Return changed-file and verification evidence to the coordinator, then route the complete verified diff to the read-only `code-reviewer`. ## Validation commands - `go test ./api/assistant-api/internal/transformer/... -run TestTTS` - `go test ./api/assistant-api/internal/transformer/<provider>/...` - `cd ui && yarn test providers` - `./skills/tts-integration/scripts/validate.sh --check-diff --provider <provider>` ## References - `references/checklist.md` - `references/tts-checklist.md` - `examples/sample.md`
GitHub에서 보기