Original Reddit post

Hey everyone, I’ve used Claude Code for personal projects before, mostly by writing prompts and letting it implement things. Now, I’ll be using it for the first time on a large professional project, and I want to approach it more seriously. The project involves a substantial backend, followed by a frontend. Since this is a real business application, I want to minimize bugs, avoid architectural mistakes, and keep the codebase maintainable as the project grows. For those of you who have used Claude Code on large production projects: How do you structure your workflow? Do you follow a spec → plan → implementation → testing process? How do you manage CLAUDE.md and project documentation without making them too large or difficult to maintain? What practices have helped you catch mistakes early and prevent Claude from making changes that break existing functionality? Do you use custom skills, subagents, hooks, or other tools? Which ones have actually made a difference? What are the biggest mistakes you’ve made when using Claude Code on a large project, and what would you do differently if you were starting over? I’m not looking for a magic prompt or a fully autonomous setup. I’m more interested in a reliable development workflow that keeps the developer in control while making the most of Claude Code. I’d really appreciate any practical advice, lessons learned, or resources you’d recommend. Thanks! submitted by /u/Best_Lavishness4037

Originally posted by u/Best_Lavishness4037 on r/ClaudeCode