Did you end up finding a reference you liked better? I'm default suspicious of anything called "vibe coding" but there are probably some good lessons in that territory.
To answer your question, no. I'm growing deeply suspicious of outright vibe coding as a practice. We still need to figure out the tools and process, so experimentation is pretty much where we're still at.
Edit: One concrete thing that the robo coding changes is it's totally reasonable to have the tools synthesize requirements based on a Slack thread, write a design doc, polish that, do a draft implementation, and then finally open a ticket to do the work with the benefit of having tested many of the assumptions.