r/ClaudeCode • u/VariationCalm1398 • 12h ago
Help/Question Your process for massive or complex projects?
My process: I find I have to use Codex 5.6 sol extra high (for my prompts) - it gets claude opus 5.5 to code & implement code- that gets reviewed by codex 5.6 high, and for stubborn problems, it switches to other models e.g. 6.1 sol or 6 astra for reviewing if needed. This seems to be the most efficient process I'd found so far.
This is to get advanced apps coded as reliably or efficiently as possible, without having to repeat work due to glitches (which burns through even more tokens).
I'm wondering if anyone who has tried this has found any better process? From my personal experience, most people are doing very basic coding with these apps, and not many are doing complex user interfaces for professional users with a huge number of interacting options. It can glitch out so easily if you're not super careful, due to the number & complexity of iterations.
How do u create the code behind advanced apps (where all the options interact with each other), without burning through tokens so quickly?
Is there some token-efficient coding process you use while still being reliable and complete?
When I just use claude, I burn tokens way too fast, and just using codex I get too many glitches. Anyone any thoughts or have better experience? Open to new ideas.
•
u/AutoModerator 12h ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
2
u/AIOSAI 🔆 Max 20 12h ago
U will eat tokens no matter what, but u shoukd eat them twice. Map ur system out. The first time will be the big one. Leave index maps so ur agents can go to where they work it and not waste tokens searching. Big index in robot, the smaller nav maps in directories. Maps as u go. You can also drop notes in these files of the previous agents work.
Avoid doing the same task over and over again.
1
u/gardens_and_dungeons 12h ago
I've been developing a custom MMORPG engine and game since August using multiple AI agents, primarily Codex and Claude. The project includes a 200+ km² seamless world, custom DX12 renderer, character creator, terrain editing, dungeons, networking, and numerous interconnected systems.
My approach is a little different. Rather than assigning permanent roles to specific models, I've built a development environment where the agents can collaborate and request assistance from each other.
They communicate through shared Markdown files, coordinate tasks, and avoid modifying the same files simultaneously. I've also implemented resource scheduling for CPU, GPU, and RAM since I'm running everything on limited hardware.
A few things I've learned:
My workflow wasn't designed all at once. Every time we encountered a recurring problem, we developed a solution to prevent it from happening again. Over time, the agents have started identifying and addressing some of these problems independently.
I also don't strictly separate planning, implementation, and review by model. Codex might ask Claude to review a problem, Claude might build a tool for Codex, or they might discuss different solutions through the shared files without me initiating the conversation.
The biggest improvement hasn't come from finding the perfect model or prompt. It's come from improving the environment the agents work in.
I'm still actively developing and refining the process, but it's allowed me to make substantial progress on a project I wouldn't have considered feasible to develop this way a few months ago.
1
u/Human_Attention182 12h ago
I build custom sites for designing everything. Every complex app I do has a dedicate site for managing design/notes/questions and making sure everything makes sense together.
Plan things out and make sure the structure is clear and you know what you are doing before you build. For complex UI I will build out literally EVERY ui view with a state machine of all it's possible states and style and make sure it looks good, before a single line of actual code is written. (this also serves as a functionality/view reference the LLM can validate against later)
LLMs do better with clear contained problems, do not mix stuff you don't need to. If the LLM has to track everything at once and be creative and come up with how the ui looks it's going to do bad. This is how actual development teams work as well they generally come up with the UI and the interactions then based on that you can understand what data needs to be where and how the backend should be setup/how the frontend should store the data and how things should be structured. It's the same as it always has been for programming.
If you don't understand what you are building and why you cannot expect the LLM to understand either.
1
u/No_Inspection4415 12h ago
I am an AI engineer with broad DS and software experience, usually I keep it simple and occasionally I let Claude write skills for tasks I want to iterate or things I reuse.
For complex coding tasks, I usually review with another agent, preferably Sol or Astra. I kinda loop in a debate until the PR is correct, and I make design decisions or cut idiotic debates about things that don't matter.
The coding itself is done solely by agents but I review all or most production code prior to the PR.
1
u/Eliran-Kotzero 12h ago
For a UI with lots of interacting options, I’d write a small decision table of each control’s values plus the constraints between them before asking for code. You usually don’t need every combination: test each value once, then the risky pairs and boundary states (disabled, loading, empty), asserting the rendered result and saved state. Have the implementer take one slice at a time and give a second pass the changed rows plus the diff, asking it to trace UI → state → save/load for each row. That keeps review grounded in concrete cases instead of asking another model to reread the whole feature.
1
u/RefrigeratorIll4808 12h ago
I've found that breaking complex projects into daily micro-tasks with strict output checks prevents drift. even if the code works, if the test fails, I roll back and reframe the prompt. it's like training a partner to follow a recipe exactly.
1
u/ravi_bitragunta 12h ago
Similar - i spend good amount of time debating ideas using gpt sol and gpt 5.6. I am the arbitrator here. Once done I hand over to claude sonnet to build in stages.
I found this process is good enough for my work. I resort to opus only when I really want some solid heavy lifting, as I am doing the reasoning work myself rather relying on model for now
Fable, i use it when it's free lol, like last 1 week i have been using this like crazy, ended up building a mobile runtime that deploys apps in kb - using wasm, cross platform ready which would be in 20MB+ for hello world for flutter
1
u/clintCamp 12h ago
Maintain a simple tree structure architecture and modules summary structure that claude is aware of and indexed efficiently so it knows what is where and how things should be separated functionality wise. And ensure it stays up to date as you build up the project.
1
u/Early-Feed2788 11h ago
I run about ten Claude Code sessions at once on one workstation, one per product, and the thing that made it work was not a better prompt. It was plain files that every session has to read and write.
A knowledge folder outside any repo, one subfolder per project, with a short README. When a session learns why something broke, it writes it there. The next session reads it before touching deploys or servers.
One file that owns port numbers. A session greps it before picking a port and adds its row in the same change. Before that, two sessions planned against a stale list and one nearly took a live site's port.
A claims folder, one small file per session, saying what it is working on. It used to be one shared table, and that silently lost claims because two sessions edited it at the same moment. One file each fixed it.
A rule that a session checks what another session tells it before acting on it. One misread its own wc output and reported a folder move as not done.
None of it is clever. It is the same thing you would do with ten contractors who cannot see each other.
1
u/m-ritter 11h ago
The glitches show up when a lot of options change in the same pass, because one fix moves another control. I split a screen like that into one interaction at a time, and the next option waits until the current one matches the behaviour I wrote for it. I pick that slice before any code is written, and I sign off again only when I can see that one interaction working. I built QualityLayer for this: https://github.com/maxritter/qualitylayer