Bitwize Music

I love music but never learned an instrument. AI became the creative outlet that was always out of reach. This project started as a way to go deep on Claude Code plugin architecture, agentic workflows, multi-model orchestration, and MCP tooling. Music was the domain because it was personal.

What it actually does: a Claude Code plugin that turns a conversation into a full album production pipeline. You describe what you want to make, and it handles concept development, lyrics, Suno prompts (an AI music generation platform), audio mastering, and release prep — with quality gates and source verification at every stage.

Questions? See the FAQ.

> [!NOTE] > Active development happens on the develop branch — main only receives tested, stable releases. If you run into issues, open an issue or submit a PR.

Example Workflow

You:    "Let's make an album about the 2016 Bangladesh Bank heist"
Claude: Creates album structure, runs 7-phase concept planning

You:    "Start the research"
Claude: Dispatches legal, financial, and security researchers in parallel
        Gathers DOJ filings, SWIFT documentation, malware analysis
        Cross-verifies sources, flags claims that need human review

You:    "Sources look good. Let's write track 1"
Claude: Drafts lyrics, checks prosody and rhyme schemes
        Scans for pronunciation risks, suggests phonetic fixes
        Builds the Suno style prompt and generation settings (model, Variety, Max Mode)

You:    "Track sounds great, here are the stems"
Claude: Imports stems from Suno, polishes per-stem
        Masters to -14 LUFS for streaming
        Generates promo video and social media copy

Concept to released album. You generate on Suno, everything else happens in the terminal.

Install

/plugin marketplace add bitwize-music-studio/claude-ai-music-skills
/plugin install bitwize-music@bitwize-music

Then run /bitwize-music:setup to detect your environment and install dependencies. Run /bitwize-music:configure to set your artist name and workspace paths.

Platform: macOS, Linux, WSL2, and native Windows are all fully supported. The full test suite runs on windows-latest in CI (plus dedicated Windows legs for the MCP boot check and MuseScore PDF export) — the MCP server, state cache, non-audio workflow, and the ffmpeg audio pipeline all run natively there. Promo video works on Windows too, though it's verified by hand rather than continuously guarded (its tests mock ffmpeg). Sheet music works natively too: MuseScore PDF export is CI-verified on windows-latest, and AnthemScore transcription runs against a licensed install (its free trial exposes no CLI on any OS, so that caveat isn't Windows-specific). Python 3.11+ for the MCP server and audio tools. See the compatibility matrix for the per-feature breakdown.

Architecture

This is where the engineering lives. The plugin is a case study in how far you can push Claude Code's plugin system.

Skill System (53 Skills)

Each skill is a self-contained markdown file with a YAML frontmatter that declares its model, description, and when it should activate. Skills range from simple clipboard operations to multi-step creative workflows. Claude routes to skills automatically based on context, or you invoke them directly with /bitwize-music: .

The lyric-writer knows prosody rules, rhyme scheme analysis, and Suno's pronunciation quirks. The mastering-engineer knows loudness targets per platform and genre-specific EQ curves. The researcher coordinates parallel sub-agents across 10 domain specializations.

See docs/skills.md for the full reference.

Multi-Model Orchestration

Skills declare which Claude model they need. Creative work that directly impacts music quality runs on Opus. Coordination and reasoning tasks use Sonnet. Mechanical operations (imports, validation, clipboard) run on Haiku.

Skills declare the tier alias, not a pinned version, so each one tracks the current frontier model in its tier automatically — no per-skill edit when a new Claude generation ships.