[jFriedensreich]

Its an interesting direction if you see it under the umbrella of diminishing costs: You build a product once with vibe coding and a design/ product hat. Once you know what works you rebuild it 100% in a framework like this. You do this every time from scratch when the tech debt or the mismatch between architecture and needs are too big.

[gck1]

You could also use the same framework always - that's what I'm doing anyway. But you gotta remember that no matter how well you spec it, first iteration of the specs is going to suck anyway.

But you vibe-code it anyway and see what happens. You'll start noticing obvious issues that you can track back to something in spec.

Then you throw away the entire thing (the entire project!) and start from scratch. Repeat until you have something you like.

Incremental specing doesn't work though. You need a clean room approach with only important learnings from previous iterations. Otherwise agent will never pick a hard but correct path.

[rsrsrs86]

I do exactly this. The database schema won’t change as often.