Spec → Scaffold for audio plugins
Build the audio plugin you keep imagining.
Describe your idea in plain English. You get a scoped plugin spec, a playable prototype built around it, and the prompts to vibe-code it further in Cursor — with a clear JUCE path to VST/AU when you're ready.
One-time purchase · ~48h delivery · No coding background needed
From idea to first sound, then onward
- 01
Describe it
A pad machine, a swing click, a three-pad sampler. Sound words, not code words. How to write your idea.
- 02
Get your scaffold
We scope the idea and wire a working prototype on one of four engines: pad/drone, drums, click, or sampler.
- 03
Vibe-code the rest
Open the folder in Cursor, run the prompt chain, add one feature at a time — and follow the JUCE path when you want a real plugin.
Start learning
Free guides for musicians who want to build their own audio plugins with AI — read at your own pace.
Learn hub
All guides in one place: scoping, prototyping, and the path to VST/AU.
Scope your first plugin
Shrink a big idea into one musical job you can hear in minutes.
Vibe coding plugins
What steering an AI assistant looks like for audio tools — and its limits.
Blog
Plugin ideas, prompt chains, common mistakes, and Web Audio basics.
Inspiration
Plugins like these start as an idea and a prototype
Example plugin UIs you can aim for: delays, synths, reverbs. They're not included products. Your pack builds the playable browser version first, then the prompts and JUCE path help you grow toward a look like this.
UI inspiration only. Your pack builds the playable browser prototype first, not a compiled VST/AU.
What's in the $49
Everything you need to start building — and an honest line on what isn't included.
Not included: a compiled VST/AU plugin. You get the prototype and the path; the native build is yours to take on.
- Plugin spec — Will / Won't / Build-next, scoped to your idea
- Playable browser prototype — open it, press Start, hear it
- Cursor prompt chain — understand → extend → polish, in order
- Project rules — keep your AI assistant on-scope
- Guides — mini ebook, success checklist, prompt cheat sheet
- JUCE path — curated resources for taking it native (VST/AU)
Why prototype first
Hear it in minutes
No SDK, no host setup, no signing. Prove the idea sounds right before you invest in a native toolchain.
AI works better on rails
Assistants extend a working project far more reliably than they invent one from a blank folder.
The design carries over
Controls, signal flow and scope you settle in the prototype become the blueprint for a JUCE build.
Questions
What do I get for $49?
A written Spec for your plugin idea (what it will do, what it won't, what to build next), a playable browser prototype zip built around it, an ordered Cursor prompt chain, project rules, short guides, and a JUCE learning path for going native (VST/AU) later.
Is this a finished VST or AU plugin?
No. You get a working browser prototype you can hear and extend, plus a clear path toward JUCE. A compiled VST/AU plugin is not part of the $49 delivery.
Do I need to know how to code?
No. The prototype already makes sound. You open it in an AI coding tool such as Cursor and follow the prompts one feature at a time. Curiosity helps; a CS degree doesn't.
What kinds of ideas fit?
Small, focused instruments and utilities: pad and drone machines, drum machines, click and practice tools, and sample-trigger pads. One clear job per plugin works best.
How fast is delivery?
The target is about 48 hours after your intake answers arrive.
Can I try it first?
Yes. Download the free sample pad prototype to hear what a scaffold looks and sounds like before you buy.
Start with a spec that already makes sound
$49 one-time · delivered in ~48h after intake · browser prototype, prompts, guides and JUCE path