People have been asking me this.
Honestly, the way I vibe-code is not special at all. Going by the true definition, it's not even vibe-coding.
The reason I build good software with AI is because I was already good at it prior to AI.
I don't even use skills, agents.md, MCPs, etc.
I prompt one small feature at a time.
My typical vibe-coding session looks like this:
"Create a table to track usage analytics, the data should be scoped to projects for better granular insights."
> Agent creates table.
"Generate and run the migration files, then create a trackUsage helper function we can resuse".
> Agent: Done.
> "Scan the API directory and track usage for every event that is emitted".
Sometimes, I send all of this or more as one prompt but you get the point. One thing at a time, the same way I would do it without AI.
I'm not doing anything out of the ordinary to get good results out of AI. Existing experience and expertise is what helps me.
Bro..., I don't if you will ever honor this or even take a look at this comment twice.., but if you ever did, if there was a way to have a preview into your client vibecoding session 🙏🏾