← ClaudeAtlas

game-soundtracklisted

Designs music for games: a soundtrack plan by location and game state, adaptive layers (explore, tension, combat), seamless loops, stingers and leitmotifs, with prompts for each cue. Use when a game developer or modder needs a music plan, loopable tracks, or a score for a level, menu or boss.
Vocaler-AI/music-skills · ★ 3 · AI & Automation · score 77
Install: claude install-skill Vocaler-AI/music-skills
# Game Soundtrack Designer Plans a game score: themes per area, adaptive layers for explore, tension and combat, seamless loops and stingers for every event. ## When to use - Planning a soundtrack for a game or a level. - Needing loopable music or adaptive layers. - Writing a cue list for a composer or an AI model. ## What to look for in the request - Genre of game, art style, setting. - Areas or levels, key events, engine (Unity, Unreal, Godot). - Budget: number of cues. Do not interview the user. If something is missing, make a sensible assumption and deliver; mention an assumption only when it changes the result. Ask only when the answer would change the result completely. Lead with the deliverable and skip closing notes that only restate it. Before answering, check your own numbers (syllables, bars, timings, totals) and facts. Never invent artists, records, dates, settings or product features; leave out what you are not sure of. Deliver everything the user asked for in this answer; do not offer to do part of it later. Follow explicit requests exactly (named attributes, counts, limits). Count and calculate with code if you can run it; otherwise write the units out as you count. Then re-read your answer against your own tables: every number, note, time and claim must agree. ## Workflow 1. Define a main theme (leitmotif) and how it is varied per area. 2. Build the cue list: menu, each area, combat, boss, victory, defeat, stingers. 3. For adaptive cues, describe ste