Learn · Free guides

Learn to vibe-code audio plugins

Plain-English guides for musicians and producers who want to build their own sound tools with AI coding assistants. No sales pitch, no hype — just a realistic path from idea to something you can hear, and onward to a real plugin if you want it.

What “vibe coding plugins” means

Vibe coding is building software by describing what you want to an AI coding assistant — in tools like Cursor, Claude Code, Copilot or similar — and steering the result by ear and by eye rather than writing every line yourself. For audio, that means saying things like “make the pad slower to fade in and a little darker,” listening, and asking for the next change.

It works surprisingly well for small, focused sound tools. It works badly when the idea is vague or huge. Most of what you need to learn is not syntax — it is scoping, describing sound, and knowing which layer you are building in: a quick browser prototype, or a native plugin your DAW can load.

These guides exist to make that learning curve shorter. Read them in order, or jump to the one that matches where you are stuck.

The learning path

  1. Understand the territory. What AI coding tools can and can’t do for audio, and what a realistic first month looks like. → Vibe coding audio plugins: the honest guide
  2. Pick a tiny first idea. One job, one sound, one screen. Write Will / Won’t lists so the AI doesn’t wander. → Scope your first plugin
  3. Describe it well. The 3-line formula and a copy-paste template. → Writing your plugin idea
  4. Prototype in the browser. Web Audio lets you hear your idea in minutes, with no compiler and no DAW crashes. → From browser prototype to VST/AU
  5. Go native when it’s worth it. JUCE is the common route to VST3, AU and standalone apps. → A JUCE learning path

You can stop at any step. Plenty of people get real value from step 4 alone: a browser instrument you can play and record into your DAW is already a creative tool. Step 5 is where the effort jumps, and it is worth knowing that before you start.

Who this is for

  • Musicians and producers with an idea for a sound tool that doesn’t quite exist
  • Beginners curious about AI coding who want a project more fun than a to-do app
  • Hobbyists who tried asking a chatbot for “a VST” and got a pile of code that didn’t build

You don’t need a computer science background. You do need patience, a willingness to change one thing at a time, and decent headphones.

Three ideas that make everything easier

1. Small beats clever

A slow pad with one “warmth” knob that you finish is worth more than a modular synth you abandon. Small ideas let the AI keep the whole project in its head, and they let you hear whether each change helped.

2. Hear it first, then harden it

A browser prototype is a sketchpad. It tells you whether the idea is fun before you spend weeks on build systems, plugin formats and installers. If it isn’t fun in the browser, it won’t be fun as a VST.

3. Sound words beat code words

“Bright and plucky like a music box” gives an AI more useful direction than half-remembered DSP jargon. Learn the vocabulary gradually, as you need it.

From the blog

Or browse all posts.

Try a working example for free

The fastest way to understand all of this is to open a project that already makes sound. The free sample pad prototype is a small browser instrument you can unzip, open in an AI coding tool, and start changing. Ask it for a slower attack, a different chord, a filter sweep — and listen to what happens. It’s the same kind of starting point the rest of these guides assume.

Common questions

Can AI write a finished VST for me?

Not reliably in one shot. It can help a lot with each step, but native plugins involve build tools, plugin formats, real-time audio rules and testing in hosts. The prototype-to-VST guide explains what that path actually involves.

Which AI coding tool should I use?

Any editor-integrated assistant that can see your whole project works. What matters more is giving it a clear spec and project rules, and asking for one change at a time.

How long until I have something I can use?

A browser prototype that makes a pleasant sound: an evening. A polished browser tool: a few weekends. A native plugin you’d share with friends: usually weeks to months, depending on how much you learn along the way.

Want a head start on your own idea?

Spec → Scaffold turns a plain-English plugin idea into a scoped spec, a playable browser prototype, an ordered prompt chain, and a JUCE path for later. It is not a compiled VST/AU. Questions? [email protected]

Get Spec → Scaffold — $49or try the free sample →