one shotting/"context engineering" larger apps or bigger code changes with claude code gives me fragile results. common issues:

- too much code gets generated. flows might work, but the code is slop.
- many UI/UX bugs. every iterative fix dirties the code further.
- claude invents new features/abstractions that I never asked for

what's working better for me is acting as the architect. I break down the task myself into what would usually be 15-30 minute sessions if I were to write the code manually.

- I ask claude to implement each increment
- I test it and give feedback to claude
- I then review the code and ask for any necessary refactors
- git commit -m "checkpoint"
- rinse and repeat

this places me in the role of PM/tech lead on a team. results in better UX and more resilient code.

exploring. prev: @clankfun, improbable, github. https://ntik.me

have you been able to parallize that? if so how?

meaning have say a team of 3 claude's working while you PM

Farcaster Development Boutique @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

right now 2 copies of a repo with 2 claudes on two branches

Peep this: https://docs.anthropic.com/en/docs/claude-code/common-workflows#run-parallel-claude-code-sessions-with-git-worktrees