agency-game-audio-engineer

Design interactive audio systems integrating FMOD/Wwise across Unity, Unreal, and Godot.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/augustoheiss/LogicDefense --skill agency-game-audio-engineer-augustoheiss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-game-audio-engineer
Source: https://github.com/augustoheiss/LogicDefense/tree/main/.gemini/skills/agency-game-audio-engineer
Command: npx skills add https://github.com/augustoheiss/LogicDefense --skill agency-game-audio-engineer-augustoheiss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridges game design and audio implementation by providing a structured approach to building interactive audio systems, adaptive music, and spatial sound within engines like Unity, Unreal, and Godot.

Core Features & Use Cases

  • Adaptive music systems that respond to gameplay tension and state changes.
  • Spatial audio rigs and dynamic 3D soundscapes across Unity, Unreal, or Godot.
  • Middleware-driven integration standards, budgets, and clear event naming for scalable collaboration.
  • Documentation and guidance for project setup, testing, and performance budgets.

Quick Start

Configure your project's audio identity, set performance budgets, and implement a middleware-driven FMOD/Wwise workflow to drive adaptive and spatial audio.

Frequently Asked Questions about agency-game-audio-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement adaptive music systems that respond to gameplay tension using FMOD or Wwise?

Adaptive music systems use parameter-driven middleware events to shift musical intensity based on gameplay state. This approach structures interactive audio architectures that respond dynamically to tension changes while enforcing CPU and voice budgets across platforms.

What's the best way to integrate spatial audio rigs across Unity, Unreal, and Godot?

Spatial audio integration uses middleware-driven workflows to build dynamic 3D soundscapes across major game engines. It provides structured event naming conventions and validation workflows to ensure consistent audio behavior across Unity, Unreal, and Godot.

How do you enforce voice and CPU performance budgets for game audio middleware?

Performance budgets are enforced by configuring middleware-driven audio architectures that limit voice counts and CPU usage. This approach documents specific budget thresholds and validation workflows to maintain scalable audio behavior across different platforms.

Does this approach support Wwise and FMOD integration for scalable game audio architectures?

Wwise and FMOD integration is fully supported to drive scalable, middleware-driven audio architectures. The system applies integration standards, parameter-driven music, and clear event naming conventions to ensure consistent collaboration and cross-platform audio behavior.

How do I set up event naming conventions and documentation for game audio projects?

Event naming conventions and documentation are established by defining integration standards and validation workflows for the project. This structure ensures scalable collaboration and provides thorough guidance for project setup, testing, and performance budgets.

When do I need middleware-driven audio architectures instead of native engine audio?

Middleware-driven audio architectures are needed when projects require adaptive music, spatial audio, and strict performance budgets that respond to gameplay state. They provide scalable collaboration tools and consistent cross-platform behavior that native engine audio often lacks.