HTML/JS/CSS is basically entirely vibe coded. I won't even try to reorg the 4000 line ui.js file. I can just redo the whole thing from a new prompt in a few minutes.
For things like the SQL schema I am still doing things entirely by hand. The consequences of getting this part wrong tend to be far more catastrophic than something in the UI layer.
The UI is the layer the customer is most likely to interact with and request changes over. This is why using the AI as the intermediary is so compelling. Most UI code is not long for this world if we are actually putting it in front of live customers. The less emotionally & economically attached to it we are, the better it is for everyone involved.
When my customer gives me crap about the UI, I barely even process it as a cortisol event because I spent very little time inventing the thing they are concerned with. It makes iterating faster and easier when you don't have much pride on the line.
Probably that's one of reasons why modern web experience is terrible.
A total overhaul is always but a single prompt and 5 minutes away, should the need arise...
That's how you get bloated apps that run poorly on lower/mid end consumer hardware and environments, with poor accessibility, and whatnot :p
Not that LLMs are the cause, this happened a lot before too, but they can exacerbate the issue. They can also be effectively used to minimize it, though they more often than not don't do that without explicit instructions.
There are easy ways to prevent the bloat and wasteful performance though, sth I do deeply care about.
You can get a long way staying on vanilla or picking (for your llm) one of those superfast frameworks like svelte in ny experience :)