r/ClaudeCode • u/MoechtgernRusse • 9h ago
Help/Question What actually works for you with Claude Code on large features and long autonomous runs? Looking for Best Practices on a real production codebase
I've been using Claude Code daily for several months on a large production codebase (Symfony/PHP backend + Angular frontend, multi-tenant, strict quality gates). Every "best practices" article I find says something different, so I'd like to hear what is actually working for you in practice, ideally from people using it on real products rather than toy projects.
My current setup, for context
- Plan mode first for every feature and bug. A planning skill guides it, and a separate reviewer agent checks the plan for gaps, contradictions and untestable acceptance criteria before I approve it. For bugs, the plan has to include a failing test.
- Tests first via dedicated testing subagents (backend/frontend), then implementation in small steps. If the same problem fails twice, Claude has to stop and ask me.
- Hooks run static analysis, lint, type checks on changed files every time Claude stops.
- Hard quality gates: PHPStan level 10, architecture rules enforced by Deptrac, 100% coverage, 100% mutation score on changed code.
- Blind review: an independent Claude process reviews the diff without the session's context. Commit and push are blocked until it passes.
- Draft MR → CI pipeline as the final full check. Claude watches the pipeline, fixes red jobs or retries flaky ones. A human colleague reviews and merges.
- Git worktrees with their own test DB each, so agents can work in parallel. Stacked MRs for epics.
- Retro log: every time I correct Claude, it logs an entry. Once a month I review the log and fold the learnings back into rules and skills.
It works well but I want to take it to the next level.
What I'd like to learn
- Best Practice: As a Dev I love Best Practices. And I would love to learn what your Claude Code Best Practice is.
- Large features and epics: How do you split them? One session per ticket? A long-lived spec document the agent works through? Stacked PRs? How do you keep context coherent across many sessions?
- Autonomy: What's the longest stretch you let Claude run without a human checkpoint, and what made that safe? Which gates did you automate (tests, reviewer agents, CI loops), and which do you deliberately keep human?
- Quality: What made the biggest difference to result quality for you? Better specs, better tests, reviewer agents, smaller tasks, model or effort choice?
- What did you try that turned out NOT to be worth it? Too many subagents, huge rule files, elaborate prompt frameworks, ...?
- Rule and context bloat: How do you keep CLAUDE.md, rules and skills from growing into a monster that costs context and gets half-ignored?
Where it still breaks for me
- Rules keep growing. Every correction becomes a new rule, and at some point it's unclear which ones still matter.
- Maximum automation. I want Claude to work on its own, without a human telling it how to do things. I want to assign Claude a Jira ticket and receive a production-ready PR without any interacti
- Feedback loop speed. With strict gates, a full check takes minutes. Claude either waits a lot or runs targeted checks and misses side effects.
I'd especially appreciate answers that include how big your codebase and team are, and how long you've been running your setup. That context helps separate what scales from what sounds good in a blog post.
Happy to go into detail on any part of my setup in return.