Help us improve
Share bugs, ideas, or general feedback.
From phantom
Session setup methodology for Reaper DAW. Guides track hierarchy, bus routing, send/receive configuration, sidechain setup, and genre-specific session templates. Use this skill whenever the user wants to set up a new mixing session, organize tracks into folders and buses, create routing for sends and returns, build a session from a genre template, configure sidechain compression routing, set up color coding and naming conventions, or prepare render settings. Also use when the user has a mix brief from /phantom:audio-diagnostician and needs to translate diagnostic findings into session architecture decisions, or when they ask about Reaper-specific track setup, folder structures, or plugin routing -- even if they don't say "session setup" explicitly.
npx claudepluginhub fadelabs/phantom --plugin phantomHow this skill is triggered — by the user, by Claude, or both
Slash command
/phantom:session-architectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Where this fits in the workflow:**
Professional mixing methodology for audio engineering. Guides through pre-mix analysis, phase checking, gain staging, EQ decisions, compression selection, spatial processing, and automation. Encodes the decision-making process of a senior mix engineer backed by Phantom MCP measurement tools. Use this skill whenever the user wants to mix stems or tracks, balance a mix, make EQ or compression decisions, set up signal chains, choose compressor types, solve frequency conflicts between instruments, set up spatial processing (reverb, delay, panning), automate volume or effects, or compare their mix against a reference. Also use when the user mentions muddy mixes, harsh frequencies, buried vocals, kick/bass conflicts, or any mixing problem -- even if they don't say "mix" explicitly.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Polishes raw Suno audio by processing per-stem WAVs (vocals, drums, bass, etc.) with cleanup, EQ, and compression, then remixing into a polished stereo WAV for mastering.
Share bugs, ideas, or general feedback.
Where this fits in the workflow:
/phantom:audio-diagnostician-- analyze stems first- You are here:
/phantom:session-architect-- set up the session/phantom:mix-engineer-- mix with measurement-backed decisions/phantom:effects-engineer-- creative processing/phantom:mastering-engineer-- final output
A well-organized session is half the mix. I've seen engineers waste hours hunting for the right track or untangling routing because they skipped the 15-minute setup. A clean session flows -- you make mixing decisions instead of debugging signal path problems. Color every track, name every bus, route every send before you touch a fader.
If /phantom:audio-diagnostician produced a mix brief, read it first. The stem count, sample rates, problem stems, and masking conflicts all inform how you structure this session. A session built around the diagnostic findings puts the solutions in your signal path from the start.
If audio-diagnostician produced a mix brief, start there. Pull out:
If there's no mix brief, gather this information manually before building the session.
Pick the genre template closest to your project from session-templates.md and adapt it. Don't force unconventional projects into a standard template -- start with the closest match and modify. For unusual instrumentation (no drums, orchestral instruments, synth percussion), start from the rock/metal template (the most comprehensive) and strip out what you don't need, rename what doesn't fit.
Reaper's folder tracks serve double duty: visual grouping AND audio bus. A track set as a folder automatically sums its children -- put your compressor on the folder track and it's a bus compressor. This is Reaper's superpower and the foundation of every session.
Standard bus architecture (adapt per genre):
DRUMS (folder/bus) -- color: red
Kick In
Kick Out
Snare Top
Snare Bottom
Hi-Hat
Toms (1, 2, 3)
Overhead L, Overhead R
Room L, Room R
BASS (folder/bus) -- color: blue
Bass DI
Bass Amp (if present)
GUITARS (folder/bus) -- color: green
Rhythm L, Rhythm R
Lead
Clean / Acoustic
VOCALS (folder/bus) -- color: yellow
Lead Vocal
Harmonies
Backing Vocals
Ad-libs
KEYS / SYNTHS (folder/bus) -- color: orange
Piano, Organ, Synth Pad, Synth Lead
FX RETURNS (folder/bus) -- color: purple
Room Verb
Plate Verb
Slapback Delay
Long Delay
Parallel Compression
MIX BUS (master parent)
Requires a Reaper MCP server. Automated track creation, folder setup, and color assignment need a Reaper MCP server connected. See the setup guide for installation. Without it, use this as a reference for manual session setup in Reaper.
Reverb sends:
Delay sends:
Parallel compression:
All send levels start at -inf (negative infinity). Bring up to taste during mixing. Never set sends at 0 dB as a starting point -- that's the maximum, not the default.
Sidechain bass to kick is the most common sidechain setup. In Reaper, sidechain signals travel on channels 3-4 (the first pair beyond the main stereo out on channels 1-2).
How to set up sidechain in Reaper:
This makes the bass duck briefly when the kick hits -- creating space in the low end without EQ. For frequency-dependent sidechaining, HPF the sidechain input at 80-100 Hz so only the sub frequencies duck (not the kick's attack).
Other common sidechain setups:
Consistency matters more than the specific scheme. Pick colors per instrument group and stick with them across all sessions:
| Group | Color | Why |
|---|---|---|
| Drums | Red | High energy, attention-grabbing -- drums are the foundation |
| Bass | Blue | Cool, low -- visually opposite to drums |
| Guitars | Green | Middle ground, organic |
| Vocals | Yellow | Bright, stands out -- vocals should always be easy to find |
| Keys/Synths | Orange | Warm, between guitars and vocals |
| FX Returns | Purple | Distinct from all instrument groups |
Name tracks descriptively: "Kick In" not "Audio 1", "Lead Vox" not "Track 14". When you come back to a session after a week, the names should tell you exactly what each track is without soloing.
When building sessions through the Reaper MCP:
set_track_name after insert_track — the name parameter on insert is unreliableinsert_audio_file call — check with get_track_itemsget_project_summary after structural changesSet the project sample rate to match the stems (don't let Reaper resample on import). Internal processing: 32-bit float (Reaper's default, leave it).
| Deliverable | Format | Sample Rate | Bit Depth | Notes |
|---|---|---|---|---|
| Stems for mixing | WAV | Match project | 32-bit float | Preserves full dynamic range |
| Mix for mastering | WAV | Match project | 24-bit | Standard delivery to mastering |
| Preview / client approval | MP3 | 44.1 kHz | 320 kbps | Lossy but good enough for review |
| Apple Digital Masters | WAV | 96 kHz (if source supports) | 24-bit | Submit highest quality available |
Before any processing, set all faders to unity (0 dB) and check levels. Aim for -18 dBFS average on each channel -- this gives plugins the headroom they expect (most plugin emulations are calibrated to -18 dBFS = 0 VU). If a stem is significantly hotter or quieter, use the item/clip gain (not the fader) to bring it to the right level.
Envelopes are how you make a mix breathe. Set them up during session creation so they're ready when you need them.
Essential envelope types:
Automation modes:
For detailed Reaper track, bus, plugin, and routing setup, see reaper-setup.md.
This covers:
For genre-specific session templates (track layouts, routing conventions, color schemes), see session-templates.md.
Available templates:
For compound Reaper operations that apply this skill's methodology, see reaper-recipes.md.
Available recipes:
Recipes require a Reaper MCP server (TwelveTake recommended). See setup guide for installation.