the path of the vibe coder: phase 1: this is incredible, I can build anything! phase 2: claude code can't even debug a simple CSS class, so f**ing useless phase 3: oh it refactored the whole battle visualizer in one prompt, we're so back! phase 4: every new feature breaks old features.. maybe this won't work phase 5: just realized most of the tests are stubbed or ignored, let's clean this up and do this properly phase 6: alright we're back, new features don't break old code and we're doing incremental improvements I'm basically at phase 6 right now where I'm diving into the code and actually need to understand what's going on. Learning: Vibecoding gets you to ~90% completion while the last 10% take patience and a more "traditional way of working". You need to shift from "let's build things quickly with multiple claude code instances" to "pair programming with claude code where you are the navigator and claude code the driver", and you actually read this code this time.