Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Creates interactive game music with layered stems and seamless loops for middleware integration.
/plugin marketplace add pluginagentmarketplace/custom-plugin-game-developer/plugin install custom-plugin-game-developer@pluginagentmarketplace-game-developerThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/daw_config.yamlreferences/DAW_GUIDE.mdscripts/music_helper.py┌─────────────────────────────────────────────────────────────┐
│ DAW COMPARISON │
├─────────────────────────────────────────────────────────────┤
│ REAPER: │
│ Price: $60 │ Best for: Game audio, flexibility │
│ Pros: Lightweight, customizable, great for stems │
├─────────────────────────────────────────────────────────────┤
│ ABLETON LIVE: │
│ Price: $99-749 │ Best for: Electronic, live performance │
│ Pros: Session view, great for layered music │
├─────────────────────────────────────────────────────────────┤
│ FL STUDIO: │
│ Price: $99-499 │ Best for: Electronic, hip-hop │
│ Pros: Pattern-based, lifetime updates │
├─────────────────────────────────────────────────────────────┤
│ LOGIC PRO: │
│ Price: $199 │ Best for: Film, orchestral (Mac only) │
│ Pros: Great instruments, Apple ecosystem │
└─────────────────────────────────────────────────────────────┘
INTERACTIVE MUSIC LAYERS:
┌─────────────────────────────────────────────────────────────┐
│ Layer 1 (Base): Percussion/rhythm - always playing │
│ Layer 2 (Harmony): Pads/strings - calm moments │
│ Layer 3 (Melody): Main theme - exploration │
│ Layer 4 (Tension): Dissonance - approaching danger │
│ Layer 5 (Combat): Intense - full orchestra/drums │
└─────────────────────────────────────────────────────────────┘
MUSIC STATE TRANSITIONS:
┌─────────────────────────────────────────────────────────────┐
│ [EXPLORATION] → detect enemy → [TENSION] │
│ ↑ ↓ │
│ └── no enemy ←───────── [COMBAT] ←── engage │
│ ↓ │
│ enemy defeated │
│ ↓ │
│ [VICTORY] │
│ ↓ │
│ → [EXPLORATION] │
└─────────────────────────────────────────────────────────────┘
GAME MUSIC PRODUCTION PIPELINE:
┌─────────────────────────────────────────────────────────────┐
│ 1. CONCEPT: │
│ • Reference tracks │
│ • Mood boards │
│ • Discuss with team │
├─────────────────────────────────────────────────────────────┤
│ 2. SKETCH: │
│ • Quick mockup (piano/synth) │
│ • Establish tempo, key, theme │
│ • 30-second demo for approval │
├─────────────────────────────────────────────────────────────┤
│ 3. PRODUCTION: │
│ • Full instrumentation │
│ • Create stems for interactivity │
│ • Multiple intensity versions │
├─────────────────────────────────────────────────────────────┤
│ 4. MIXING: │
│ • Balance levels │
│ • EQ and compression │
│ • Leave headroom for SFX │
├─────────────────────────────────────────────────────────────┤
│ 5. EXPORT: │
│ • Loop points (seamless) │
│ • Stems for middleware │
│ • Multiple quality versions │
└─────────────────────────────────────────────────────────────┘
LOOP TECHNIQUES:
┌─────────────────────────────────────────────────────────────┐
│ 1. MEASURE-ALIGNED: │
│ • Start/end on exact bar boundaries │
│ • Ensure reverb tails don't extend past end │
│ • Crossfade at loop point if needed │
├─────────────────────────────────────────────────────────────┤
│ 2. INTRO + LOOP: │
│ • Separate intro section │
│ • Main loop starts after intro │
│ • Mark loop start/end points in metadata │
├─────────────────────────────────────────────────────────────┤
│ 3. STINGER TRANSITIONS: │
│ • Short musical phrases for state changes │
│ • Victory fanfares │
│ • Death/failure sounds │
└─────────────────────────────────────────────────────────────┘
| Format | Use Case | Settings |
|---|---|---|
| WAV | Master/Stems | 48kHz, 24-bit |
| OGG | Game runtime | 128-192 kbps |
| MP3 | Backup/Preview | 320 kbps |
| MIDI | Interactive | Standard MIDI |
┌─────────────────────────────────────────────────────────────┐
│ PROBLEM: Loop has audible click/pop │
├─────────────────────────────────────────────────────────────┤
│ SOLUTIONS: │
│ → Ensure loop points are at zero-crossing │
│ → Add small crossfade (5-10ms) │
│ → Check reverb/delay tails │
│ → Verify exact sample alignment │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ PROBLEM: Music doesn't fit game mood │
├─────────────────────────────────────────────────────────────┤
│ SOLUTIONS: │
│ → Create reference playlist with team │
│ → Start with temp music to establish mood │
│ → Get feedback on sketches before full production │
│ → Consider genre conventions │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ PROBLEM: Transitions between music states jarring │
├─────────────────────────────────────────────────────────────┤
│ SOLUTIONS: │
│ → Use same key/tempo across states │
│ → Add transition stingers │
│ → Crossfade on musical boundaries (bars) │
│ → Use stems to gradually add/remove layers │
└─────────────────────────────────────────────────────────────┘
MIDDLEWARE INTEGRATION:
┌─────────────────────────────────────────────────────────────┐
│ DAW → Export Stems → Wwise/FMOD → Game Engine │
│ │
│ Stems typically: │
│ • Percussion │
│ • Bass │
│ • Harmony │
│ • Melody │
│ • FX/Stingers │
└─────────────────────────────────────────────────────────────┘
Use this skill: When composing game music, implementing audio systems, or creating interactive soundtracks.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.