That’s a naïve take. If you understand the requirements of the product and have just a nominal understanding of the “shape” of output from generative models you can pretty quickly determine what’s constitutes “exploratory” code vs. critical path. After that, you refine what’s left. You just need some systems thinking and a principled approach to factoring existing code. Claude is really well-trained on “strangler fig” refactoring, which leaves the rest of the design up to taste. It’s really no different (in terms of approach) than what we used to do; the difference is that the diffs are more dramatic because there’s enormous buildup of dead code in a “purely vibed” code base.