Blog · Oct 15, 2026

Want to build an audio plugin? Start with a browser prototype

If your goal is to build your own audio plugin and you’re learning to steer AI in plain English, start where you can hear progress in minutes: a playable browser prototype—then grow toward VST/AU.

“Vibe coding” means describing what you want and letting an AI coding assistant write and reshape the project. For plugins, the trap is starting from a blank repository—or jumping straight into a native plugin SDK— before you’ve proved the idea makes the sound you imagined.

Browser prototype first, native plugin next

A Web Audio prototype runs in Chrome (or any modern browser): open an HTML file, click Start, hear oscillators, samples, or clicks. No installer, no DAW host, no bridge toolchain. That feedback loop is what makes vibe coding stick for musicians who want to build plugins.

Native VST/AU plugins are the destination many makers want—and they’re slower to learn on day one. They’re a great next step once the musical idea works. They’re a harsh first mile when you’re still discovering the feature set.

Scaffold beats blank (on the path to a plugin)

AI helpers do better when the project already has a clear layout: audio engine in one file, UI wiring in another, a short scope doc, and prompts that say “extend one feature.” That’s the Spec → Scaffold idea: your plain-English plugin idea becomes a scoped Spec plus a playable prototype zip you can grow— with a JUCE / VST-AU learning path when you’re ready to go native.

Honest scope: Spec → Scaffold ($49) does not include a compiled VST or AU. You get the on-ramp—prototype, prompts, path—not a finished commercial plugin binary.

Try it, then buy a personalized one

Download the free sample pad prototype, unzip, open src/index.html, click Start. When you’re ready for a prototype built around your plugin idea (pad, drums, click, or sampler), Spec → Scaffold is live for $49. Support: [email protected].