AGENT SKILL

game-audio

Game audio principles. Sound design, music integration, adaptive audio systems.

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

name
game-audio
risk
unknown
source
community
date_added
2026-02-27
description
Game audio principles. Sound design, music integration, adaptive audio systems.

03 SKILL.md 正文

Game Audio Principles

Sound design and music integration for immersive game experiences.


1. Audio Category System

Category Definitions

Category Behavior Examples
Music Looping, crossfade, ducking BGM, combat music
SFX One-shot, 3D positioned Footsteps, impacts
Ambient Looping, background layer Wind, crowd, forest
UI Immediate, non-3D Button clicks, notifications
Voice Priority, ducking trigger Dialogue, announcer

Priority Hierarchy

When sounds compete for channels:

1. Voice (highest - always audible)
2. Player SFX (feedback critical)
3. Enemy SFX (gameplay important)
4. Music (mood, but duckable)
5. Ambient (lowest - can drop)

2. Sound Design Decisions

SFX Creation Approach

Approach When to Use Trade-offs
Recording Realistic needs High quality, time intensive
Synthesis Sci-fi, retro, UI Unique, requires skill
Library samples Fast production Common sounds, licensing
Layering Complex sounds Best results, more work

Layering Structure

Layer Purpose Example: Gunshot
Attack Initial transient Click, snap
Body Main character Boom, blast
Tail Decay, room Reverb, echo
Sweetener Special sauce Shell casing, mechanical

3. Music Integration

Music State System

Game State → Music Response
│
├── Menu → Calm, loopable theme
├── Exploration → Ambient, atmospheric
├── Combat detected → Transition to tension
├── Combat engaged → Full battle music
├── Victory → Stinger + calm transition
├── Defeat → Somber stinger
└── Boss → Unique, multi-phase track

Transition Techniques

Technique Use When Feel
Crossfade Smooth mood shift Gradual
Stinger Immediate event Dramatic
Stem mixing Dynamic intensity Seamless
Beat-synced Rhythmic gameplay Musical
Queue point Next natural break Clean

4. Adaptive Audio Decisions

Intensity Parameters

Parameter Affects Example
Threat level Music intensity Enemy count
Health Filter, reverb Low health = muffled
Speed Tempo, energy Racing speed
Environment Reverb, EQ Cave vs outdoor
Time of day Mood, volume Night = quieter

Vertical vs Horizontal

System What Changes Best For
Vertical (layers) Add/remove instrument layers Intensity scaling
Horizontal (segments) Different music sections State changes
Combined Both AAA adaptive scores

5. 3D Audio Decisions

Spatialization

Element 3D Positioned? Reason
Player footsteps No (or subtle) Always audible
Enemy footsteps Yes Directional awareness
Gunfire Yes Combat awareness
Music No Mood, non-diegetic
Ambient zone Yes (area) Environmental
UI sounds No Interface feedback

Distance Behavior

Distance Sound Behavior
Near Full volume, full frequency
Medium Volume falloff, high-freq rolloff
Far Low volume, low-pass filter
Max Silent or ambient hint

6. Platform Considerations

Format Selection

Platform Recommended Format Reason
PC OGG Vorbis, WAV Quality, no licensing
Console Platform-specific Certification
Mobile MP3, AAC Size, compatibility
Web WebM/Opus, MP3 fallback Browser support

Memory Budget

Game Type Audio Budget Strategy
Mobile casual 10-50 MB Compressed, fewer variants
PC indie 100-500 MB Quality focus
AAA 1+ GB Full quality, many variants

7. Mix Hierarchy

Volume Balance Reference

Category Relative Level Notes
Voice 0 dB (reference) Always clear
Player SFX -3 to -6 dB Prominent but not harsh
Music -6 to -12 dB Foundation, ducks for voice
Enemy SFX -6 to -9 dB Important but not dominant
Ambient -12 to -18 dB Subtle background

Ducking Rules

When Duck What Amount
Voice plays Music, Ambient -6 to -9 dB
Explosion All except explosion Brief duck
Menu open Gameplay audio -3 to -6 dB

8. Anti-Patterns

Don't Do
Play same sound repeatedly Use variations (3-5 per sound)
Max volume everything Use proper mix hierarchy
Ignore silence Silence creates contrast
One music track loops forever Provide variety, transitions
Skip audio in prototype Placeholder audio matters

Remember: 50% of the game experience is audio. A muted game loses half its soul.

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

04 同仓库更多 Skills

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

vercel-sandbox

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

slack

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

dogfood

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

★ 1