I use VS Code and Copilot, for $10 i get weeks of daily usage. It handles super advanced modules perfectly.
Sticking to one model is not great imo, i like to use more to catch errors or for creativity that one model might suck at. It can be an advantage to stick to one in the way that you will get more familiar with it i guess.
Having a good prompt in .github is important so that it reads it every time… if i have an issue (super rare), i ask why it came up, what the fix was, how we prevent it. Then this is added to my prompt in .github.
I let different models review the code too. They will catch different things and they can sometimes optimize in their own way.
I actually have not idea about copilot and and I almost never open Xcode or VS code on my own, after 1 year vibe coding and several programs I still know nothing about coding. I think this is why my Claude.md needs to be organized… Thanks for all the feedbacks. I start doing vibe coding because MM exists. This really changes my life.
Just pushed a small update to the MADZINE plugin focused on bug fixes and behavior improvements.
theKICK - Accent fix
The accent input had a bug where connecting a gate signal could mute the output when the gate was low. It now follows TR-808/909 convention and affects three parameters sampled on trigger:
Volume: 0.5 to 1.0 (+6 dB range)
Pitch sweep depth: 1.0x to 1.8x (snappier attack)
Drive gain: 1.0x to 1.26x (+2 dB pre-saturation, more harmonic punch)