Comment by gbalduzzi

I think that fast prototyping followed by a rewrite (in case the prototype confirmed the idea works) is the best use case for vibe coding.

A product person can quickly validate an idea and, once the project is a bit more concrete you can bring in the engineering team and start caring about security, maintenability, scaling and so. A rewrite is almost always the best thing, you can start with a solid foundation instead of spaghetti vibe coded stuff