From xonovex-skill-audio
Use when building a low-level, real-time audio/sound system that does its own mixing: the OS audio callback / render thread, summing voices into the output buffer, sample-rate conversion and per-voice pitch, voice pools and stealing, and handing play/stop/parameter changes from the game thread to the audio thread. Triggers on audio underrun/dropout, clicks/pops, the audio callback can't lock or allocate, buffer size vs latency, resampling/interpolation, mixing gain/pan/clipping, fixed voice pools, even when the user doesn't say 'audio'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/xonovex-skill-audio:audio-guideThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Engine-agnostic architecture for a software audio mixer: a real-time render thread feeds the device, voices are summed into the output buffer, and the game thread talks to the audio thread only through a lock-free queue. The lock-free queue itself is owned by **lock-free-guide**; preallocated pools by **memory-management-guide**; struct-of-arrays voice state by **data-oriented-design-guide**.
Engine-agnostic architecture for a software audio mixer: a real-time render thread feeds the device, voices are summed into the output buffer, and the game thread talks to the audio thread only through a lock-free queue. The lock-free queue itself is owned by lock-free-guide; preallocated pools by memory-management-guide; struct-of-arrays voice state by data-oriented-design-guide.
MAX_VOICES; cap concurrency, steal by priority, ramp before reusing a slot, see references/voice-management.mdm[ic][oc] - Volume, pan, and spatialization are all one per-voice input->output matrix, see references/mixing-and-buffers.mdmalloc slow path, or one first-touch page fault inside the callback and you get a click or dropout — far worse than a dropped render frame.float drifts a long sound out of tune; keep the cursor in double or fixed-point.malloc a bigger one; pick a producer-side drop/coalesce policy up front.Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.
npx claudepluginhub xonovex/platform --plugin xonovex-skill-audio