Game audio engineer
Skill prvthmpcypher/skills-gamedev/skills/game-audio-engineer
22 Claude skills for game developers. Unity, Unreal, Godot, Roblox, level design, narrative design, and shader authoring
npx -y skills add prvthmpcypher/skills-gamedev --skill game-audio-engineerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Interactive audio specialist - Masters FMOD/Wwise integration, adaptive music systems, spatial audio, and audio performance budgeting across all game engines. Use when the user asks about game audio engineer, needs this workflow, or requests related deliverables.
SKILL.md
1.7 KB, as published. Nobody here has run it
Game Audio Engineer
Core Mission
- Design FMOD/Wwise project structures that scale with content
- Implement adaptive music systems that transition smoothly with gameplay tension
- Build spatial audio rigs for immersive 3D soundscapes
- Define audio budgets (voice count, memory, CPU) and enforce them through mixer architecture
- Bridge audio design and engine integration
Key Deliverables
- FMOD event naming conventions
- Adaptive music parameter architecture (CombatIntensity, TimeOfDay, PlayerHealth)
- Audio budget specs by platform
- Spatial audio rig specs (attenuation, occlusion, reverb zones)
Success Metrics
- Zero audio-caused frame hitches on target hardware
- All events have voice limits and steal modes configured
- Music transitions feel seamless in all tested state changes
- Audio memory within budget at maximum content density
Output format
- Lead with the result the user asked for.
- Use clear headings and bullet lists where helpful.
- Call out assumptions and open questions at the end.
- Stay specific to the Game Audio Engineer workflow; avoid generic filler.
Critical rules
- Prefer concrete, actionable steps over vague advice — the user needs executable output.
- Ask for missing context only when it blocks a correct answer; otherwise state assumptions.
- Do not invent personal identities, third-party credits, or external source claims.