voice integration skill — canonical UI + transcription pattern (one drop-in) #219
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_skills#219
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Overview
Wherever an app needs voice (transcription input, TTS output, wake word), today every app reinvents the integration. Define one canonical skill that any app drops in to get: voice input button → hero_lib voice client → aibroker → STT/TTS provider. UI, plumbing, and error handling identical across apps.
Why
Meeting 2026-05-06: "wherever in app we need voice, use the skill to put UI part / skill can do it properly / talk to ai broker, talk to new component from scott".
The
hero_voiceskill exists. This issue is to make it the canonical drop-in and apply it to every app that needs voice.Acceptance
hero_voiceskill documents the canonical drop-in pattern (UI markup, hero_lib call, settings persistence)Related
hero_voiceSource: meeting notes 2026-05-06.