$git clone https://github.com/bitwize-music-studio/claude-ai-music-skillsHuman + AI music production workflow for Suno - skills, templates, and tools
| 1 | # Claude AI Music Skills |
| 2 | |
| 3 | 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. |
| 4 | |
| 5 | 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](https://suno.com) prompts (an AI music generation platform), audio mastering, and release prep — with quality gates and source verification at every stage. |
| 6 | |
| 7 | Questions? See the [FAQ](FAQ.md). |
| 8 | |
| 9 |  |
| 10 | |
| 11 | > [!NOTE] |
| 12 | > Active development happens on the `develop` branch — `main` only receives tested, stable releases. If you run into issues, [open an issue](https://github.com/bitwize-music-studio/claude-ai-music-skills/issues) or submit a PR. |
| 13 | |
| 14 | --- |
| 15 | |
| 16 | ## Example Workflow |
| 17 | |
| 18 | ``` |
| 19 | You: "Let's make an album about the 2016 Bangladesh Bank heist" |
| 20 | Claude: Creates album structure, runs 7-phase concept planning |
| 21 | |
| 22 | You: "Start the research" |
| 23 | Claude: Dispatches legal, financial, and security researchers in parallel |
| 24 | Gathers DOJ filings, SWIFT documentation, malware analysis |
| 25 | Cross-verifies sources, flags claims that need human review |
| 26 | |
| 27 | You: "Sources look good. Let's write track 1" |
| 28 | Claude: Drafts lyrics, checks prosody and rhyme schemes |
| 29 | Scans for pronunciation risks, suggests phonetic fixes |
| 30 | Builds Suno V5 style prompt with genre tags and vocal direction |
| 31 | |
| 32 | You: "Track sounds great, here are the stems" |
| 33 | Claude: Imports stems from Suno, polishes per-stem |
| 34 | Masters to -14 LUFS for streaming |
| 35 | Generates promo video and social media copy |
| 36 | ``` |
| 37 | |
| 38 | Concept to released album. You generate on Suno, everything else happens in the terminal. |
| 39 | |
| 40 | --- |
| 41 | |
| 42 | ## Install |
| 43 | |
| 44 | ```bash |
| 45 | /plugin marketplace add bitwize-music-studio/claude-ai-music-skills |
| 46 | /plugin install bitwize-music@bitwize-music |
| 47 | ``` |
| 48 | |
| 49 | Then run `/bitwize-music:setup` to detect your environment and install dependencies. Run `/bitwize-music:configure` to set your artist name and workspace paths. |
| 50 | |
| 51 | **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](reference/cross-platform/tool-compatibility-matrix.md) for the per-feature breakdown. |
| 52 | |
| 53 | --- |
| 54 | |
| 55 | ## Architecture |
| 56 | |
| 57 | This is where the engineering lives. The plugin is a case study in how far you can push Claude Code's plugin system. |
| 58 | |
| 59 | ### Skill System (53 Skills) |
| 60 | |
| 61 | 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:<name>`. |
| 62 | |
| 63 | 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. |
| 64 | |
| 65 | See [docs/skills.md](docs/skills.md) for the full reference. |
| 66 | |
| 67 | ### Multi-Model Orchestration |
| 68 | |
| 69 | 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. |
| 70 | |
| 71 | | Tier | Model | Skills | Rationale | |
| 72 | |------|-------|--------|-----------| |
| 73 | | Creative | Opus 4.8 | 7 | Lyrics, Suno prompts, album concepts, legal/verification research — output quality defines the music | |
| 74 | | Reasoning | Sonnet 4.6 | 30 | Research coordination, pronunciation analysis, most workflows | |
| 75 | | Mechanical | Haiku 4.5 | 16 | Imports, validation, clipboard, help — speed over creativity | |
| 76 | |
| 77 | This project pushes Claude Code hard — multi-agent research, real-time audio analysis, sub-agent orchestration across model tiers. It works best on the Max subscription. The standard Pro subscription will hit rate limits during multi-track sessions. |
| 78 | |
| 79 | See [reference/model-strategy.md](reference/model-strategy.md) for per-skill rationale. |
| 80 | |
| 81 | ### MCP Server (80+ Tools) |
| 82 | |
| 83 | A Python MCP serve |