Can AI write a finished VST plugin for me in one prompt?

No. AI coding assistants are strong at HTML/JS prototypes and can help with JUCE/C++ once you have a toolchain and a clear spec. A compiled, signed VST/AU that loads in every DAW is a multi-step project, not a single chat reply.

What is the fastest first step toward a VST with AI?

Prove the sound and controls as a playable browser prototype (Web Audio). You hear progress in minutes, learn the describe → edit → listen loop, then take a clearer idea into JUCE for native VST/AU.

Do I need to know C++ to vibe code a VST?

Not on day one. Start with a browser prototype and plain-language prompts. When you move to JUCE, expect to learn toolchain basics (IDE, build, plugin formats). AI helps, but native plugins still need a build environment and DAW testing.

Does Vibepatch Spec → Scaffold include a compiled VST?

No. For $49 you get a personalized spec, a playable browser prototype, Cursor prompts, guides, and a JUCE learning path. A compiled VST/AU is not included.

How to Make a VST Plugin with AI — Honest Roadmap

Search “how to make a VST plugin with AI” or “vibe code a VST plugin” and you will see two extremes: tutorials that dump you into a native SDK on day one, and hype that implies a chat bot can ship a finished DAW plugin overnight. Neither path matches how most musicians actually succeed. Here is an honest roadmap: idea → scoped spec → browser prototype → JUCE / native → testing in a DAW.

What “vibe coding a VST” really means

Vibe coding means you steer an AI coding assistant in plain language—describe the sound or control you want, accept small diffs, listen, and correct. It does not mean the model invents a signed VST3 for every host in one shot. Treat AI as a fast pair-programmer for each stage of the roadmap, not as a plugin factory.

Stage 1 — Shrink the idea

Write one sticky-note job. Examples that fit a first plugin:

Ambient pad: pick key + mood, hold a slowly evolving tone I can record.
Practice click: BPM, accent on beat 1, optional mute bars.
Four sample pads: load a WAV, trigger, simple pitch.

Avoid “make me Serum.” Huge scopes stall both humans and AI. If you need help phrasing the idea, use our writing your idea guide.

Stage 2 — Write a scoped spec (will / next / won’t)

Before more code, lock three lists: Will (what the first version already does), Build next (ordered features), Won’t (yet) (native export, full preset library, multi-out, etc.). A short spec keeps Cursor (or any assistant) from inventing a second product mid-chat. See also: Cursor rules for vibe coding audio plugins.

Stage 3 — Prove it as a browser prototype

Use the Web Audio API in a tiny HTML/JS project so you can double-click, click Start, and hear sound. This is the fastest feedback loop for vibe coding: change one knob or DSP habit, refresh, listen. A playable prototype is step one toward a VST—not a detour. More on the tradeoffs: browser prototype vs VST/AU and why start with a browser prototype.

Try the free sample pad scaffold if you want to hear this shape before buying anything: download the free sample.

Stage 4 — Move toward JUCE / native VST-AU

When the idea sounds right and the control set is stable, open a native path (commonly JUCE) with a clearer brief: which parameters exist, what the audio graph does, what “done” means in a DAW. Expect toolchain work: IDE, SDKs, plugin formats (VST3 / AU), and host quirks. AI can help generate glue code and explain errors; it cannot skip compilers, signing, or host validation for you. A learning path (JUCE docs, structured courses such as The Audio Programmer’s material) belongs in your pack—not a promise of a binary on day one.

Stage 5 — Test in a DAW like a plugin author

Load in more than one host if you can (behavior differs).
Check silence, bypass, parameter automation, and CPU on a long session.
Compare against your sticky-note job: does it still do one clear thing well?
Only then expand scope (presets, fancy UI, extra modes).

What AI is good at (and what it is not)

Good: scaffolding UI wiring, explaining unfamiliar APIs, suggesting one-feature prompts, rewriting a filter section after you describe the sound.
Weak alone: taste, musical intent, shipping/signing, and “make it a commercial VST” without a spec and a build setup.

For the mindset behind this loop, read what vibe coding means for audio plugins and how to start your first audio plugin with AI.

Where Vibepatch Spec → Scaffold fits

Spec → Scaffold is for people who want to build audio plugins by vibe coding. For $49 (one-time) you get a personalized will/next/won’t spec, a playable browser prototype matched to your idea (pad, drums, click, or sampler engine), an ordered Cursor prompt chain, project rules, mini ebook, checklist, cheat sheet, and a resources sheet toward JUCE. Delivery target is about 48 hours after intake. A compiled VST/AU is not included—you get the honest first miles plus the map to native, not a finished DAW binary.