Status: early trial, not a finished release. This template exists to walk the whole path a new user would take and find what is missing. What works today is measured, not promised. Run npm run studio:validate to see what works on your machine.
Why This Exists
Making a plugin with Claude Code is powerful, but a single session has no structure. Nobody stops you from shipping a preset that clips, skipping the listening test, or adding a twelfth knob. There is no QA pass, no sound review, no one asking "does this still do the one thing it promised?"
Claude Code Plugin Studio gives your Claude Code session the structure of a real plugin company. Instead of one general-purpose assistant, you get 42 specialized subagents organized into a studio hierarchy: directors who guard the vision, department leads who own their domains, and specialists who do the hands-on work. Each agent has defined responsibilities, escalation paths and quality gates.
The result: you still make every decision, and you are still the only one who can say how it sounds. But now you have a team that asks the right questions, catches mistakes early, and keeps your project organized from first idea to published release.
It is the audio plugin sibling of Claude Code Game Studios, which it is adapted from. Plugins are built on Maru.
Built for Claude Code
This template is deliberately specific to one agent. It uses what Claude Code offers instead of aiming at what every agent has in common:
| Claude Code feature | What the studio does with it |
|---|
| Subagents | 42 agents in .claude/agents/: directors, department leads and specialists, each with its own responsibilities and escalation path |
| Skills | 104 slash commands in .claude/skills/, from /start through release |
| Hooks | Scripts in .claude/hooks/ on eight session events, which load context, check pushes and record agent activity |
| Path-scoped rules | 13 rules in .claude/rules/, applied according to the files being edited |
| Status line and settings | The project stage in .claude/statusline.mjs, and permissions in .claude/settings.json |
Using another agent? The agents, skills and hooks are Claude Code features, and will not run elsewhere. Use the Maru agent skill, which works with any agent. The skill tells an agent what Maru can do. This studio tells Claude Code how we think a plugin should get made.
This is an independent project from Maru. It is not made or endorsed by Anthropic. Claude and Claude Code are Anthropic's products.
Table of Contents
What's Included
| Category | Count | Description |
|---|
| Module | 1 | A working Maru effect in src/, from the official blank starter |
| Agents | 42 | Specialized subagents across product, DSP, face, sound, QA, release and Maru itself |
| Skills | 104 | Slash commands for every phase (/start, /design-module, /dev-story, /gain-staging, /publish) |
| Hooks | 15 | Automated checks on commits, pushes, face and DSP writes, large reads, assets and session lifecycle |
| Rules | 13 | Path-scoped standards for DSP, faces, the contract, presets, assets and more |
| Templates | 30 | Briefs, design documents, ADRs, listening reports, host matrices, release checklists |
| How-to guides | 8 | Effect, instrument, MIDI tool, sample kit, face from an image, web audio port, publishing, native builds |
| Task map | 1 | Every plugin design task, with its skill, agent and status |
| Validator | 1 | Checks every command this studio names against your installed CLI, then tries each capability |
Studio Hierarchy
Tier 1: Directors
creative-director technical-director producer
Tier 2: Department Leads
product-designer lead-dsp-engineer sound-director
art-director qa-lead release-manager
docs-lead localization-lead maru-specialist
Tier 3: Specialists
dsp-engineer voice-engineer midi-engineer
graph-engineer parameter-designer face-engineer
ux-designer preset-designer sample-librarian
demo-producer prototyper performance-analyst
host-compat-engineer native-format-engineer devops-engineer
security-engineer qa-tester accessibility-specialist
community-manager copywriter tools-programmer
modulation-engineer sampler-engineer visualizer-engineer
Maru specialists
restricted-typescript-specialist dsp-library-specialist
ui-kit-specialist generative-audio-specialist publishing-specialist
hardware-specialist
Each agent has its own role, area of ownership, rules and escalation path, and agents without a build job have no shell access. The directors ask for Opus, most specialists name Sonnet, and the rest inherit your session's model. Rules in .claude/rules/ add a second layer: they load by file path, whichever agent is working. The roster lists them all.
Slash Commands
Type / in Claude Code to access all 104 skills:
This is the beginning of the README. Read the rest at the original. Read the full README ↗
