I think this comment exposes an important point to make: people have different opinions of what "vibe coding" even means. If I were to ask an LLM to vibe code a text editor, I guarantee you I wouldn't get a React app using Supabase -- because I'd give it pages of requirements documentation and tell it not only what I want, but the important decisions on how to make it.

Obviously no model is going to one-shot something like a full text editor, but there's an ocean of difference between defining vibe coding as prompting "Make me a text editor" versus spending days/weeks going back and forth on architecture and implementation with a model while it's implementing things bottom-up.

Both seem like common definitions of the term, but only one of them will _actually_ work here.