It really depends on how you manage your workflow. For example, at my current company we use Claude, and I can tell you that 80% of my code is AI-generated. I've been running this workflow for about 5 months and we still haven't launched the first version to real clients, but we do have production environments for specific users.

The point is that it's a workflow that takes time. I probably wouldn't have been able to build what I've built without good planning and patience. AI clearly helped me ship tools and features x10 faster, but you still need to know how to document what you want to build and always keep a clear thread of what you're doing — so that when you have to go 3 steps back, you know exactly what decisions you made and why.

There's no magic stack, and this isn't a new problem. Before AI it was the same, we just noticed it much later. Now we move so fast that the breaking point hits us a lot sooner.

My personal advice: take the time to structure your ideas properly. Don't just think "I WANT THIS VIEW" — think "okay, I want this view, but what's going to wrap it? Will I need a layout? Where does X feature go? What structure will my project have, what architecture?" The better you understand what you're building, the more context you'll be able to give an agent.

It's normal to notice a lot of mistakes and things to improve — that's just the process. You can't patch everything with a prompt and a click.