Uploaded March 2026 | Updated September 2026, 2 weeks ago

---

Last time I vibe coded an audio plugin. It worked, but the code was messy and I had zero control over the output. So I went and studied the best practices, and I built a tool to solve the planning problem. In this video, I show you what changes when you actually prepare before prompting.

⏰ Timestamps:
00:00 - Introduction
01:14 - Why planning matters
01:52 - The Project Planner skill
02:48 - How to upload a Claude skill
04:14 - Running the project planner
06:19 - Defining plugin parameters
08:18 - Adding unique features
11:26 - Defining what's out of scope
12:15 - Code architecture setup
14:26 - Generating the PRD and CLAUDE.md
17:09 - Setting up the project folder
19:03 - Opening Claude Code in plan mode
20:32 - Reviewing Claude's implementation plan
24:41 - Building the plugin
25:07 - Testing in the DAW
27:37 - Reviewing the code
37:28 - Fixing the ping-pong bug
40:52 - Final test
41:41 - Reflections and takeaways

🔗 Resources mentioned:
Project Planner Skill (free download) - github.com/TheAudioProgrammer/claude-audio-plugin-project-planner-skill

Claude Code — docs.anthropic.com/en/docs/claude-code


====

📚 Learn Audio Programming
theaudioprogrammer.com/books

🎤 Join our Community
theaudioprogrammer.com/community

💼 Hire Audio Programmers & Music Tech Professionals
theaudioprogrammer.com/recruitment

🏭 Create Your Own Audio Plug-in with Our Experienced Team
theaudioprogrammer.com/development

Stay connected with us
Instagram: instagram.com/theaudioprogrammer
Facebook: facebook.com/theaudioprogrammer
Twitter: twitter.com/audioprogrammer