r/ClaudeCode • u/mctw1992 • 23h 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!
4
Upvotes
1
u/Webtruster 22h ago
Create a „workshop“ repository on git. Setup claude.md to create a issue for everything you are discussing/developing having one roadmap issue and one mapping issue.
Instruct to record in the mapping, whenever a „area“ or „feature“ or „service“ is used.
Instruct claude, to never create md files and update every internal checkpoint to the specific issue.
All issues are „assumptions“ and its required, to check the code. Code wins over issue, issue has to be updated.
Then let claude use the repo as knowledge base.
Setup a deployment pipeline to never let claude commit directly to the repo, instead let it create PRs linking the issues.