Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions
Stephan
@stephancill
Anyone here building large projects using Claude code? My current approach is to 1. write a context doc describing the problem and solution with product requirements 2. produce a technical specification via a back and forth with a thinking model based on the requirements doc 3. Get a thinking model to develop a daily plan for an engineer 4. Give Claude code the requirements, spec, and plan and tell it to implement one day and write do a write up in a standup doc when it’s done. 5. When it’s done I review the changes and ask it for revisions until I’m satisfied 6. After that I start another Claude session to implement the next day with all the docs and also include the relevant standup docs. Rinse and repeat This seems to work really well. Curious if others are doing it differently and getting better results Shoutout @jc4p for sharing this approach
8 replies
0 recast
42 reactions
meatballs
@meatballs
I also throw bdd into the mix and have a set of specs and tests in gherkin
1 reply
0 recast
1 reaction
timdaub
@timdaub.eth
What‘s the benefit of that vs just giving minimal context of what u want, letting it iterate with u in the loop and reading the code base? IMO for a large code base isn‘t the context basically already there? (it‘s all the existing code)
1 reply
0 recast
1 reaction
czar
@czar
is the split to day 1, day 2 etc. to make sure you check it’s work intermittently? do you also use a team like backend and frontend devs? is that just to speed up things?
1 reply
0 recast
1 reaction
agusti
@bleu.eth
I have a few tricks (cli tools) that let the AI keep context of the codebase (ast trees, files etc, import paths) all half baked into some repos as they grew and needed I should split these into separate mini-tools anyone can plug to a repo
2 replies
0 recast
11 reactions
christopher
@christopher
Yes. Keep everything in packages/crates and make sure it's in a monorepo. Use pre/post/stop hooks. Because we package/crate everything, each area has its own CLAUDE.md file.
0 reply
0 recast
5 reactions
MetaEnd🎩
@metaend.eth
I let opus write a prd and then tasks
0 reply
0 recast
2 reactions
Dylan
@epicdylan
Check out https://github.com/ipfsnut/evermark-testnet to see my biggest Claude assisted dev lift to date. It is way too big to fit into context at this point but I have it setup as a sort of hub and spokes thing, lots of work remaining but basically I try to keep each contract/hook/component as its own vertical stack and then wrap it all in the UI layer
0 reply
0 recast
0 reaction
queennihny
@queennihny
Stepping in
0 reply
0 recast
0 reaction
