I don't think this is much of a problem with the tools rather than with your approach.

We have successfully put Claude in huge multi-thousands pr long with projects.

But this meant that:

1. Solid architectural and design decisions were made already after much trial and error

2. They were further refined and refactored

3. Countless hours have been spent in documenting, writing proper skills and architectural and best practice documents

Only then Claude started paying off, and even then it's an iterative process where you need to understand why it tries to hack his way out, etc, what to check, what to supervise.

Seriously if you think you can just Claude create some project..

Just fork an existing one that does some larger % of what you need and spend most of the initial time scaffolding it to be ai friendly.

Also, you need to invest in harnessing, giving tools and ways to the LLM to not go off rails.

Strongly typed languages, plenty of compilation and diagnostics tools, access to debuggers or browser mcps, etc.

It's not impossible, but you need to approach it with an experimentation approach, not drinking Kool aid.