I see so many posts on programming reddits now asking for "brutal feedback" (which I see so often I suspect it must also be a 2nd-tier Claudism that only comes up in this context) with a commit history an hour and a half old, and my "brutal feedback" I want to give is have you actually tried using your code?

I, too, have an AI, and I, too, have manifested a lot of stuff off of a single prompt. That first pass is generally pretty worthless. Amazing in its own way for what comes out from how little input, how quickly the amazing becomes banal, but still, pretty worthless in practice. I don't think there's anything wrong with "vibe coding" but you should definitely expect any product of it that is going to be worth a darn is going to require much more than 30 minutes of QA to be actually useful, even something as simple as a little caching library or something. And this won't change from AIs getting better in the future; it is a fundamental information theory problem about just how far the prompt can be expanded even in theory into a working program.

This is not targeted at the OP, I'm just commiserating with you. This program does not correlate with my own experience with one-shot vibe coding, which is that I generally can't go literally 5 seconds without hitting an issue of some sort. I've spent weeks on an app for my kids and I started to measure my progress by "how long I can use it before I hit an issue". I considered it a bit of an event when I hit five minutes. It's hovering around 15 to 20 right now, but I've still got a ways to go before it is "indefinite".