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++: Visual Studio 2022 на Windows, Xcode на macOS, GCC 9+/Clang 10+ с C++20 на Linux. 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 и UI), /apc-test и /apc-ship (сборка и распространение). Вспомогательные команды отвечают за статус, продолжение, отладку, патчи и развитие уже выпущенных плагинов.
Могу ли я выбрать, как строить интерфейс плагина?Да. Можно взять Visage — экспериментальный UI на чистом C++ с нативными окнами и высокой производительностью, — либо WebView, где используется HTML/CSS/JS с горячей перезагрузкой через WebView в JUCE. 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