game-audio
Game audio principles. Sound design, music integration, adaptive audio systems.
What this skill does
# 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.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.