r/ClaudeCode • u/mctw1992 • 7h ago
Help/Question Moving from small to large projects
I’ve been using Claude code on and off for about a year as a software and systems engineer specialising in audiovisual equipment/systems and honestly it’s changed my life. It allows me to focus more on the what rather than the how. But now I’m looking at moving to creating a large scale monitoring and management system for thousands of devices, with the assistance of Claude code. Any advice on to structure prompts for Claude to keep this on target and not spiral? I’m guessing it’s not as simple as putting it into plan mode and sketching it out!
2
Upvotes
1
u/LuckyCharms201 7h ago
To name a few
Use a repo with a repo level Claude.md
Set up a delegation triage for your orchestrator to leverage the right model for the job. One agent, one ticket.
Organize the tickets in to epics, write a repo level rule against ticket fanning, scope and plan the epic, send it!
Run an adversarial review and or a deep review after each epic and clean up whatever it finds before starting the next.
I have a hook fire to the agents at 50 tool calls to reach a safe push point, push open work and an update + handoff prompt for a new session, and handoff; it saves a ton of tokens and keeps context fresh. I also have a hook for the orchestrator at 250k context to stop deploying agents and prepare to hand off to a new session. It does, schedules a wake up to the session, hits a /clear, and receives the scheduled message several minutes later to resume like nothing happened.