Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By fadelabs
AI audio engineering skills for mixing, mastering, effects, diagnostics, and session setup. Pairs with the Phantom MCP server for audio analysis.
npx claudepluginhub fadelabs/phantom --plugin phantomPre-mix audio analysis and problem detection for audio engineering. Runs Phantom MCP diagnostic tools on stems, catalogs issues by severity (dealbreaker/significant/moderate/minor), identifies frequency masking between stems, and produces a structured mix brief. Use this skill whenever the user wants to analyze audio stems or files before mixing, diagnose audio problems (phase issues, clipping, noise, hum, mud, harshness), assess recording quality, prepare a mix session overview, check if a mix is ready for mastering, or investigate why something "sounds wrong." Also use when the user provides WAV file paths and asks for analysis, quality checks, or problem identification -- even if they don't explicitly mention "diagnostics."
Deep expertise in audio effects for sound design and mixing. Covers distortion/saturation taxonomy, modulation effects, time-based processing, creative effect chains, and effects automation. Use this skill whenever the user wants to choose effects, design sounds, build effect chains, make creative processing decisions, add warmth or grit (saturation/distortion), set up reverb or delay, create specific sonic textures (ethereal, lo-fi, massive, underwater), understand the science behind effects (harmonics, comb filtering, all-pass filters), or automate effects for dynamic transitions. Also use when the user asks about making something "bigger," "wider," "warmer," or "more interesting" -- those are effects engineering questions even if they don't mention specific plugins.
Professional mastering methodology for audio engineering. Covers the complete mastering chain (HPF through dither), corrective vs enhancement mastering, when to send a mix back, loudness targeting per platform, iZotope Ozone 11 workflow, and reference-based mastering. Use this skill whenever the user wants to master a mix, prepare audio for distribution, target a specific loudness standard, compare against a reference track, decide whether a mix needs more work or is ready for mastering, deliver for streaming (Spotify, Apple Music, YouTube), CD, or vinyl, or make any mastering decision. Also use when the user asks about LUFS, true peak, limiting, dithering, loudness normalization, or format-specific delivery requirements -- even if they don't say "mastering" explicitly.
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.
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.
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
AI music generation workflow for Suno - album concepts, lyrics, prompts, mastering, release
Comprehensive Suno AI music prompt creation with automated artist research, structured prompts, genre-specific techniques, AI-slop avoidance, quality review, and Chrome automation for direct upload to suno.com
Memory compression system for Claude Code - persist context across sessions
Standalone image generation plugin using Nano Banana MCP server. Generates and edits images, icons, diagrams, patterns, and visual assets via Gemini image models. No Gemini CLI dependency required.
AI image generation Creative Director powered by Google Gemini Nano Banana models. Claude interprets intent, selects domain expertise, constructs optimized prompts, and orchestrates Gemini for best results.
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Makes Claude a professional audio engineer.
Phantom gives Claude ears. It's an audio engineering system that combines measurement tools, professional mixing and mastering methodology, genre reference profiles, and Reaper DAW integration. Everything works through Claude Code.
Drop in your stems. Claude analyzes every file: spectral balance, loudness, dynamics, stereo width, phase coherence, frequency masking between instruments, and problems like clipping, hum, and noise. Then it makes the same decisions an experienced engineer would. Where to cut, what to compress, how to route, when to send it back for more work.
Without Claude, Phantom is a capable CLI analysis tool. With Claude, it becomes a full mixing and mastering workflow.
Diagnose before you mix. Load 15 stems, run one command. Phantom catches phase cancellation between kick mics, sample rate mismatches across files, 60 Hz hum on the bass DI, and frequency masking where guitar and vocals fight at 3 kHz. All before you touch a fader.
Mix against a reference. A/B your mix against any reference track or genre profile. Get per-dimension deviation: "Your vocal is 2 dB quieter at 2-4 kHz, low end is 3 dB heavy below 100 Hz, stereo width is narrower than the reference." Claude closes the gap with targeted EQ and level adjustments.
Master for every platform in one pass. Claude builds the full chain: HPF, corrective EQ, glue compression, tonal shaping, stereo imaging, limiting. Then it renders three masters. Spotify at -14 LUFS, Apple Music at -16 LUFS, and vinyl with mono bass, de-essing, and HF rolloff at 16 kHz. Different loudness targets, different format constraints, same session.
Solve problems by measurement, not guesswork. "The mix sounds muddy" becomes "4 dB buildup at 300 Hz across bass, guitar, and keys. Cut bass at 300 Hz by 3 dB, cut guitar at 250-350 Hz by 2 dB." Every recommendation is backed by a number.
Set up sessions from a template. Tell Claude the genre and stem count. It builds the folder hierarchy, bus routing, aux sends (reverb, delay, parallel compression), sidechain routing, color coding, and gain staging. Ready to mix.
Design creative effects. "I want Tool-style vocal distortion" or "Make the guitars sound like shoegaze." Claude builds the chain: saturation type, drive amount, chain order, parallel blend level. All calibrated by measurement.
Four layers that work together:
Measurement. 17 MCP tools that quantify your audio: spectrum, loudness (EBU R128), dynamics, stereo field, phase coherence, frequency masking between stems, and problems like clipping, hum, DC offset, sibilance, and room resonances.
Methodology. Five domain expert skills that encode how professional engineers actually think. Structured decision-making workflows: when to use FET vs VCA compression, how to read crest factor to choose a handling strategy, when a mix needs more work vs when it's ready for mastering.
Reference. Nine genre profiles with target loudness, spectral balance, dynamics conventions, and stereo width standards. Your mix gets compared against professional benchmarks for your genre.
Execution. Reaper DAW integration via MCP. Claude inserts EQ, sets compression ratios, builds sidechain routing, writes automation, and renders deliverables.
No install needed. Run this on any audio file:
uvx phantom-audio analyze your-track.wav
Or install it:
uv tool install phantom-audio --python 3.13
phantom analyze your-track.wav
Point it at any WAV file. You'll get a full spectral, loudness, dynamics, stereo, phase, and problem analysis in about a second.
To use with Claude, add to your MCP config (.mcp.json):
{
"mcpServers": {
"phantom": {
"command": "phantom-mcp",
"args": []
}
}
}
Install the Claude Code plugin for domain expert skills:
claude plugin install phantom/plugin
Then talk to Claude:
"Analyze my stems and tell me what needs fixing before I start mixing."
"Compare my master against this reference track and show me what's off."
"Set up a mixing session for a 5-stem rock track with parallel drum compression."
"Is this mix ready for mastering, or does it need more work?"