game-audio
Game audio principles. Sound design, music integration, adaptive audio systems.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 3.3w
- Forks
- 3.9k
01 前言 Front Matter
- name
- game-audio
- description
- Game audio principles. Sound design, music integration, adaptive audio systems.
- allowed-tools
- Read, Glob, Grep
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.
04 同仓库更多 Skills
wealthville-pool-scoring
Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter/Hold/Exit/Reduce/Avoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.
technical-debt-auditor
Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO/FIXME/HACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like "where should I focus refactoring", "find code smells", "audit my codebase", "what technical debt do we have", "prioritize cleanup work", or asks about code quality metrics. Also trigger when the user mentions "code rot", "legacy cleanup", "refactoring priorities", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say "technical debt" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.
readonly-sql-guard
Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production/ERP/analytics database (a "query" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write/DDL/side-effect/transaction-escape risks. Checks what a statement CALLS, not just its shape.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
discernment-nudge
After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.