I think frameworks are more important than ever in this AI/vibecoding world if you want to keep any chance for your code to be readable again and not become just a pile of machining that nobody quite gets what it does. The more optioned the framework is the better. The more familiar you are with the framework the better chances you can actually deliver a working thing not just some slop that looks like working.

Source: experience. I decided at some point just to vibecode a fairly complex project with gpt 5.5 sol and Fable.Burned several max subscriptions and it ended up a pile of machinery, impossible to make it work in the end. Rewrote it/vibecoded it with my framework(s), skills, lab conventions etc and it works flawlessly.

Even better I can figure out immediately if Claude or codex goes off the rails just by seeing the snippets. It just shows the AI models are just not ready to build things “unattended” without proper “steering”. Frameworks and other constrains are a way to steer the AI. Of course bloated frameworks would just make things worse.

This made me understand there are very low chances to just vibecode whatever “business” you want to try and succeed. You still need to know your “s**t”.