Audio Design

Audio Design for Games

Psychological principles and practical patterns for designing game audio that enhances player experience without causing fatigue or cognitive overload. This skill covers sound design philosophy, AI prompt engineering for audio generation, and technical specifications.

Related Skills

• web-audio: Technical implementation patterns (AudioContext, preloading, cloneNode)
• ux-feedback-patterns: Visual + audio feedback coordination
• ux-animation-motion: Timing audio with visual animations
• ux-accessibility: Reduced motion/audio preferences

Core Philosophy: Audio as Skill Atom Feedback

From Daniel Cook's Skill Atom framework, audio serves as immediate feedback that creates insight:

Action → Simulation → Feedback (AUDIO) → Insight

Key Principles:

1. Proportional Feedback: Sound intensity matches action significance
2. Melodic Hierarchy: Sounds build from simple to complex as achievements grow
3. Error as Invitation: Failure sounds should redirect, not punish
4. Fantasy Cohesion: All sounds share a unified palette creating consistent world
5. No Cognitive Overload: Sounds inform, never overwhelm

Rule 1: Volume Hierarchy by Sound Type

Different sounds serve different psychological purposes and need balanced volumes.

Why: Balanced audio creates professional feel. Loud frequent sounds cause fatigue; quiet celebrations feel anticlimactic.

Rule 2: Frequency Band Management (Anti-Masking)

Sounds must occupy distinct frequency bands to remain readable when played together.

Frequency Allocation

HPF (High-Pass Filter) Guidelines

HPF 100–150 Hz  → Heavy impacts, bass elements
HPF 150–200 Hz  → Standard UI, most game sounds
HPF 200–250 Hz  → Light, airy sounds (sparkles, chimes)
HPF 250+ Hz     → Ethereal, floating sounds

Why: Low frequencies mask each other and cause "mud." HPF keeps sounds clean and distinct.

Rule 3: Duration by Function

Sound length must match its psychological purpose.

Tail Management

Critical: Keep tails tight to prevent audio pile-up.

Decay 100–250 ms  → Snappy, rapid-fire safe
Decay 250–400 ms  → Standard feedback
Decay 400–600 ms  → Celebrations, important moments
Decay 600+ ms     → Only for rare, significant events

Rule 4: Kind Games Audio Philosophy

From Daniel Cook's Kind Games framework, audio should support prosocial design:

Audio for Psychological Safety

Error Sound Design

✅ Good: "Gentle descending three-note woodwind phrase, curious not sad"
✅ Good: "Soft 'hmm' with upward questioning inflection at end"

❌ Bad: "Harsh buzzer sound"
❌ Bad: "Sad trombone descending"
❌ Bad: "Game show failure sound"

Success Sound Hierarchy

Build a melodic progression that players learn to anticipate:

Micro:     Single tone (sparkle, chime)
Small:     Two-note ascending (success)
Medium:    Three-note phrase (phase complete)
Major:     Full flourish with resolution (achievement)
Epic:      Orchestral swell with choir (milestone)

Rule 5: AI Audio Prompt Engineering (ElevenLabs)

When generating sounds via AI, use these prompt patterns for high clarity, low masking, non-musical UI readability.

Prompt Structure

[Sound description] + [Technical specs] + [Anti-patterns]

Technical Spec Template

"{description}, {frequency info} ({X}–{Y} kHz), HPF {Z} Hz,
{duration} ms, {decay/tail info}, no {anti-patterns}"

Frequency Descriptors

Essential Anti-Patterns to Include

Always specify what to avoid in prompts:

"no melody"         → Prevents musical interference with game music
"no pad/drone"      → Prevents sustained tones that cause masking
"no reverb wash"    → Keeps sound tight and readable
"no low-end buildup" → Prevents mud in mix
"no harsh highs"    → Prevents ear fatigue
"no musical tone"   → Keeps UI sounds non-distracting
"non-musical"       → Reinforces UI intent

Rule 6: Sound Category Templates

UI Micro-Feedback

"Soft {material} {action}, {duration} ms, bright transient (2–4 kHz),
HPF {180–220} Hz, short decay {80–150} ms, no musical tone, no reverb."

Examples:
- "Soft wooden tok with subtle shimmer tail, 120 ms, bright 2–4 kHz, HPF 200 Hz"
- "Gentle paper rustle with airy top, 100 ms, HPF 180 Hz, no reverb"

Success/Completion

"Warm {instrument} {motion} with {quality} {overtone}, {duration} ms,
{frequency detail}, HPF {X} Hz, {decay} decay, non-melodic."

Examples:
- "Warm ascending harp glissando with gentle bell overtone, 350 ms"
- "Bright crystalline chime with soft shimmer tail, 300 ms, 8–12 kHz"

Error/Invalid

"Gentle {instrument} {motion}, {quality} not {negative}, {duration} ms,
HPF {X} Hz, reads as '{intention}'."

Examples:
- "Gentle descending three-note woodwind phrase, curious not sad, 400 ms"
- "Soft questioning hum with upward inflection, 300 ms, HPF 200 Hz"

Achievement/Celebration

"{Scale} {instrument} {action} with {detail}, {duration} ms,
{frequency}, {space} {wet%}, non-melodic."

Examples:
- "Full magical fanfare with shimmering strings, 800 ms, short room 0.3s 15% wet"
- "Grand orchestral flourish with bells and rising resolution, 1000 ms"

Impact/Action

"{Weight} {material} {action} + {secondary}, {duration} ms,
HPF {X} Hz, {decay}, no boom, no long tail."

Examples:
- "Heavy stone thud with brief debris ticks, 400 ms, HPF 150 Hz, dry"
- "Shield deflect: tight metallic ting with micro scrape, 150 ms"

Rule 7: Fantasy Theme Palette

For cohesive fantasy audio, maintain consistent instrument families:

Magical/Ethereal

• Chimes (crystalline, bell-like)
• Harps (warm, flowing)
• Wind instruments (airy, breathy)
• Sparkle textures (high shimmer)

Earthen/Natural

• Wood (soft toks, knocks)
• Stone (thuds, scrapes)
• Organic (sprouts, rustles)
• Water (drips, flows)

Metal/Martial

• Sword (slices, clangs)
• Shield (deflects, impacts)
• Armor (clinks, rattles)
• Mechanical (clicks, locks)

Mystical/Divine

• Choir textures (soft "ahh")
• Bells (resonant, pure)
• Shimmer (ascending)
• Glow sounds (warm hum)

Rule 8: Multi-Instance Handling

When sounds may trigger simultaneously (40+ players casting), apply these modifiers:

Layered Event Prompt Modifier

"40 layered one-shots, onset jitter 10–40 ms, pitch variance ±2–4 semitones,
wide stereo distribution, HPF consistent, subtle short room 0.2–0.3 s at 8–12% wet,
avoid masking and low-end buildup, preserve transient clarity."

Key Techniques

Rule 9: Accessibility Considerations

Reduced Audio for Motion Sensitivity

Some users prefer reduced audio stimulation with reduced motion:

// Audio should respect prefers-reduced-motion
const reduceAudio = window.matchMedia('(prefers-reduced-motion: reduce)').matches;

if (reduceAudio) {
  // Use simpler, shorter sounds
  // Reduce celebration intensity
  // Skip non-essential feedback sounds
}

Non-Audio Alternatives

Every sound should have a visual equivalent:

• Micro-feedback → Visual pulse/glow
• Success → Color flash + checkmark
• Error → Shake animation + icon
• Achievement → Badge animation

Rule 10: Testing Checklist

Before finalizing sounds:

• Volume balance: All sounds sit correctly in hierarchy
• Frequency separation: No masking when sounds overlap
• Duration appropriate: Matches function and pacing
• HPF applied: No unwanted low-end
• Tail tight: No lingering that causes pile-up
• Non-musical: Doesn't interfere with game music
• Error inviting: Failure sounds encourage retry
• Celebration proportional: Matches achievement significance
• Accessible: Works with reduced audio preference
• 40-cast safe: Still readable when many play together

Example: Fantasy Phonics Sound Design

Complete Sound Specification

Design Rationale

• Melodic hierarchy: sparkle (single) → success (ascending) → milestone (full flourish)
• Fantasy cohesion: Chimes, harps, bells, woodwinds — storybook palette
• Error as invitation: Questioning woodwind, not punishing buzzer
• Proportional celebration: 100 ms micro vs 1200 ms milestone

Quick Reference: Prompt Building Blocks

Descriptive Words by Feeling

Motion Words

Material Words