audio-plugin-coder README

The project's README from github.com/Noizefield/audio-plugin-coder. As one markdown file: README.md.

Audio Plugin Coder (APC)

Audio Plugin Coder Logo

AI-powered open-source framework for vibe-coding audio plugins from concept to shipped product

License: MIT Version JUCE Platform HOL Guard Scanner Sponsor

What's new in v1.5.0

APC 1.5 is a big step forward - especially if you are a musician or hobbyist who just wants to build your own plugin without fighting tooling. Here is what changed, in plain words.

The APC Hub - a window into your whole project. Instead of digging through folders and config files, you now get a live dashboard in your browser. Type /apc-hub (or run node hub/server.js) and you can see every plugin at a glance - which phase it is in, what still needs to be done, your design library, scripts, templates, tools and settings. Documentation is searchable and readable right there. You can even adjust your settings from a simple form instead of hand-editing JSON. It is read-only by default, so nothing breaks by accident.

Works with more AI coding tools than ever. APC used to be picky about which assistant you used. In 1.5 that changed:

A single command-line tool. All the important tasks - version, paths, build, validate, backup, rollback, status - are now in one cross-platform tool (apc), tested by an automated suite. No more hunting for the right script.

Improve and extend your plugins after release. Shipped a plugin? /apc-patch opens a focused bugfix round, /apc-evolve starts a feature upgrade. Your version number and state stay consistent automatically.

Everything else got tidier too. Docs were rewritten to match reality, the framework version has one single source of truth, and releases now land in a clean release/ folder that honors your configured paths.

Start: clone -> /apc-setup (Claude Code / Kilo / Cursor / OpenCode) or $audio-plugin-coder:audio-plugin-coder setup (Codex) -> /apc-dream MyPlugin.

APC Hub

The APC Hub gives you a complete, live overview of the framework and your plugins - no build required, read-only by default:

node hub/server.js --port 4872   # or: /apc-hub in your agent

APC Hub dashboard

Video Tutorial Series

APC tutorial series - click to watch on YouTube

APC Tutorial Series (YouTube Playlist) - 7 episodes and more to come, explaining the framework in detail.

About

Audio Plugin Coder (APC) is an AI-first framework that guides LLM agents through the whole plugin lifecycle - ideation, architecture, UI, DSP implementation, testing, and packaging - without the agent re-learning JUCE or your conventions every session. It is agent-agnostic (Codex, Claude Code, Kilo, Cursor, Antigravity) and has been hardened over 18 months of real plugin development.

The core workflow - setup -> dream -> plan -> design -> impl -> ship - is ready for production on Windows, macOS, and Linux.

Which AI Coding Tools Work with APC?

APC is agent-agnostic: pick the assistant you already use. In v1.5.0 all major ones are first-class:

Assistant Status How APC talks to it
Codex ✅ Fully supported in 1.5.0 Codex does not use slash commands - it gets a dedicated audio-plugin-coder skill and plugin with cost-aware model routing
Cursor ✅ Ready out of the box Custom rules + /apc-* commands, project guidance via AGENTS.md
OpenCode ✅ Fully wired up /apc-* commands with dedicated host shims
Claude Code ✅ Fully supported /apc-* commands
Kilo ✅ Fully supported /apc-* commands
Antigravity / Gemini ✅ Supported Natural language + AGENTS.md guidance

Previously Cursor, OpenCode and Codex had only partial support. In 1.5.0 they now work the same way as Claude Code and Kilo - no workarounds needed.

Key Features

Quick Start

One-command setup

npx github:Noizefield/audio-plugin-coder

Clones, checks your tools, and prints next steps for your platform. Requires Node.js 18+ and Git.

Manual setup

# Windows
git clone --recurse-submodules https://github.com/Noizefield/audio-plugin-coder.git
cd audio-plugin-coder
.\scripts\system-check.ps1 -Human
# macOS / Linux
git clone --recurse-submodules https://github.com/Noizefield/audio-plugin-coder.git
cd audio-plugin-coder
bash scripts/system-check.sh --human

Then open the repo in your agent and run /apc-setup, then /apc-dream <PluginName>.

Prerequisites

Platform Requirements
Windows LLM agent, Git, Node.js 18+, Python 3.8+, Visual Studio 2022 C++, CMake 3.22+, WebView2 Runtime, JUCE 9 (submodule), pluginval (submodule)
macOS LLM agent, macOS 10.13+, Xcode + CLT, CMake 3.22+, Git, Node.js 18+, Python 3.8+, jq, JUCE 9, pluginval (WKWebView, no WebView2)
Linux LLM agent, GCC 9+ / Clang 10+, C++20, CMake 3.22+, Make/Ninja, Node.js 18+, Python 3.8+, WebKitGTK, libegl-dev, ALSA (+JACK), JUCE 9, pluginval

Bridge Templates (FFGL & Max/MSP)

For FFGL visual plugins or Max for Live externals, run the Windows one-click setup:

.\scripts\setup_bridges.bat

How It Works

The Five-Phase Workflow

SETUP  -> First-run toolchain, paths, model preferences
DREAM  -> Creative brief, parameter spec
PLAN   -> Architecture, UI framework, complexity
DESIGN -> GUI mockups and visual design
IMPL   -> DSP engine and UI integration
SHIP   -> Installers, DAW testing, distribution

Agent Commands

Prefer the /apc-* names (unique across frameworks). Short aliases (/dream, ...) still work as deprecated. Codex invokes actions through the audio-plugin-coder skill (bare /plan//status are Codex built-ins).

Primary Codex action Description
/apc-setup $audio-plugin-coder:audio-plugin-coder setup First-run toolchain, paths, models
/apc-dream [Name] ... dream [Name] Start new plugin (ideation)
/apc-plan [Name] ... plan [Name] Architecture + UI framework
/apc-design [Name] ... design [Name] GUI mockups and visual design
/apc-impl [Name] ... impl [Name] Implement DSP and UI
/apc-test [Name] ... test [Name] Run tests / validation
/apc-debug [Name] ... debug [Name] Diagnose and fix issues
/apc-ship [Name] ... ship [Name] Package and distribute
/apc-status [Name] ... status [Name] Progress and state
/apc-resume [Name] ... resume [Name] Continue from last incomplete phase
/apc-new [Name] ... new [Name] Full workflow with confirmations
/apc-patch [Name] $audio-plugin-coder:audio-plugin-coder patch [Name] Bugfix generation on a shipped plugin
/apc-evolve [Name] $audio-plugin-coder:audio-plugin-coder evolve [Name] Feature generation on a shipped plugin
/apc-hub $audio-plugin-coder:audio-plugin-coder hub Open the live local dashboard

See Command Reference, Codex Compatibility, and Model Routing.

Example Session

You: /apc-setup
AI: ✅ Setup complete. Next: /apc-dream <PluginName>

You: /apc-dream TapeDelay / "Warm analog tape delay with wow/flutter"
AI: ✅ Dream phase complete! Files created: .ideas/creative-brief.md, .ideas/parameter-spec.md, status.json

You: /apc-design TapeDelay / "Teal dashboard, skeumorphic knobs"
AI: ✅ Design complete! Next: /apc-impl TapeDelay

Architecture

APC tracks every plugin in a status.json (phase, validation, rollback). That lets you pause, switch agents, or rebuild state at any time.

audio-plugin-coder/
├── AGENTS.md                    # Agent guidance (AGENTS.md standard)
├── .agents/                     # Canonical source: workflows/, skills/, rules/, guides/, troubleshooting/
├── .codex-plugin/               # Codex plugin manifest
├── skills/                      # Packaged Codex skill (points at .agents/)
├── hub/                         # APC Hub - server.js, ui/, _design/
├── templates/                   # Plugin templates (visage, webview, ffgl, max-external)
├── docs/                        # Documentation (16 files)
├── scripts/                     # Build / state / validation automation (ps1 + sh)
├── bin/                         # setup.js, apc.js CLI
├── common/                      # Shared helpers (e.g. VisageJuceHost.h)
├── plugins/                     # Your plugins (config-relocatable)
├── build/                       # Compilation artifacts
├── release/                     # Ship packages (installers, zips)
└── test/                        # apc.js test suite (npm test)

Workflows orchestrate skills: /apc-design reads your UI framework from status.json, then loads the matching design skill. Troubleshooting auto-captures issues so the system improves over time.

UI Framework Options

The AI recommends a framework during planning based on your plugin's complexity.

Supported Plugin Formats

Format Windows macOS Linux
VST3 ✅ ✅ ✅
Standalone ✅ ✅ ✅
AU ❌ ✅ ❌
LV2 ❌ ❌ ✅

CLAP support is planned.

Technology Stack

JUCE 9, CMake, PowerShell/Bash, WebView2 / WKWebView, YAML knowledge base, Node.js (CLI + Hub).

Documentation

Docs live in docs/: Getting Started, Plugin Development Lifecycle, Command Reference, Hub, FAQ, Troubleshooting. The Hub serves them as a searchable reader.

Roadmap

Contributing & Community

Join GitHub Discussions; see CONTRIBUTING.md.

Sponsor

Independent development with significant API costs. If APC saves you time, consider sponsoring - it covers API costs and accelerates new features.

Acknowledgments

License

MIT - see LICENSE.md. Note: APC itself is MIT, but plugins built with it inherit JUCE's dual license (AGPLv3 free, or a JUCE commercial license for closed-source). JUCE terms.


Built with a lot of tokens for the audio development community. Turn your plugin ideas into reality.

audio-plugin-coder (Noizefield/audio-plugin-coder)

Searching Database…

这是什么东西?Audio Plugin Coder(APC)是一个开源的、由 AI 驱动的框架,用来开发专业音频插件:你只需向 LLM 编程助手描述插件,而不用事事亲手去写。它覆盖了整个流程:构思、架构、界面、DSP(数字信号处理)、测试和打包。
那它是我写代码时用的框架,还是一个替我写代码的应用?它是一个框架,不是独立应用:它通过结构化的工作流来驱动你已经在用的 AI 编程助手(Claude Code、Codex、Cursor、Kilo、OpenCode、Antigravity),由它们帮你生成 JUCE 9 插件代码。
除了 AI 编程助手,我还需要安装什么?需要 Git、Node.js 18+、Python 3.8+ 和 CMake 3.22+,外加一套原生 C++ 工具链:Windows 上是 Visual Studio 2022,macOS 上是 Xcode,Linux 上是 GCC 9+/Clang 10+(支持 C++20)。JUCE 9 和 pluginval 会作为子模块自动拉取下来。
我实际能发布哪些插件格式?支持哪些平台?VST3 和 Standalone 版本可以在 Windows、macOS 和 Linux 上使用,但 AU 只支持 macOS,LV2 只支持 Linux。CLAP 已列入计划,目前还不能用。
MIT 许可证就是全部了吗?还是有什么坑?确实有坑:APC 本身采用 MIT 许可证,但你用它开发的插件会继承 JUCE 的双重许可——如果插件是免费/开源的,就适用 AGPLv3;闭源插件则需要购买 JUCE 商业许可证。
五个阶段的工作流实际是怎么走的?先用 /apc-dream 勾勒想法,然后依次经过 /apc-plan(架构)、/apc-design(界面草图)、/apc-impl(DSP 和界面代码)、/apc-test 和 /apc-ship(打包与发布)。还有一些辅助命令,用来查看状态、恢复进度、调试、打补丁以及对已发布的插件进行升级。
插件的界面用什么方式搭建,我可以自己选吗?可以。可以选择 Visage——一个实验性的纯 C++ 界面方案,使用原生窗口,性能很高;也可以选 WebView——用 HTML/CSS/JS 开发,并借助 JUCE 的 WebView 实现热重载。在规划阶段,AI 会根据插件的复杂程度推荐其中一种。
项目可以中途暂停,或者换一个 AI 助手继续吗?可以。每个插件的阶段、校验和回滚状态都保存在 status.json 文件里,所以你随时可以暂停、更换助手或重建状态,进度不会丢失。
APC Hub 是什么?一个本地的只读面板,用 /apc-hub(或 node hub/server.js)打开。它会显示每个插件所处的阶段和剩余工作,还有你的设计库、脚本、模板和设置,并把文档变成一个可搜索的阅读器——不需要任何构建。
Creator
Noizefield
Size
43.2 MB
Stars
334
Updated
CommitOct 10
Age
8mo
Commits · 90 Days