Blog
Guides for building audio plugins with AI
Practical notes on vibe coding music tools: prototyping first, keeping Cursor on scope, and the road to VST/AU.
Best first audio plugin ideas that work with AI
Small first-plugin ideas that fit vibe coding with AI: pads, clicks, sample toys, and utility tools you can prove in a browser before JUCE or VST.
Prompt chain for audio plugins
A practical AI prompt chain for audio plugin features — understand, extend, listen, polish. Keep Cursor on scope while you vibe-code Web Audio prototypes toward VST.
Common mistakes when vibe coding audio plugins
The mistakes that stall musicians vibe coding audio plugins with AI — oversized scope, blank-repo starts, skipping hear-it-first — and the practical fix for each.
Web Audio API for musicians (friendly intro)
A musician-friendly intro to the Web Audio API: AudioContext, nodes, Start buttons, and why browser prototypes help you vibe-code plugins before JUCE or VST.
How to make a VST plugin with AI (honest roadmap)
Idea → spec → browser prototype → JUCE/native → DAW testing. What vibe coding a VST really means—and what AI cannot skip.
Want to build an audio plugin? Start with a browser prototype
Why a playable browser prototype — not a blank repo or a native SDK — is the fastest first step to building your own audio plugin with AI.
What is vibe coding for audio plugins?
Vibe coding means steering an AI assistant in plain language. Here's how it applies to audio plugins, and why you should start from something that already plays.
How to start building your first audio plugin with AI
A practical path for musicians: define a tiny plugin idea, prove it as a browser prototype, then extend it with AI prompts toward JUCE and VST/AU.
Cursor rules for vibe coding audio plugins
How to write Cursor rules that keep an AI assistant on track while you prototype an audio plugin: tone, constraints, and one-feature-at-a-time habits.
Browser prototype vs VST/AU: the path to building your first plugin
Web Audio prototype or native VST/AU first? The tradeoffs for beginners, and why most first plugins should prove their sound in a browser before JUCE.
Start with a spec that already makes sound
$49 one-time · delivered in ~48h after you send your idea · browser prototype, prompts, guides and JUCE path