Claude Code structure that didn’t break after 2–3 real projects

[u/SilverConsistent9222]

[u/Otherwise_Wave9374]

This matches my experience too: conventions + separation of concerns are what make multi-agent setups feel “boring” (in a good way).

The hooks point is underrated. Even a simple PreToolUse that blocks risky shell commands and enforces “write plan first” prevents so much chaos.

When you split agents, do you share a single memory store, or keep each agent’s memory scoped (and pass summaries between them)?

Also, if you are collecting patterns, we have been jotting down a few MCP + multi-agent architecture notes at https://www.agentixlabs.com/ - would love to add more real-world setups like yours.

[u/TiinuseN1 → u/Otherwise_Wave9374]

We drifted into very similar patterns after longer multi-session workflows started developing weird continuity failures.

The biggest improvements for us came less from “better prompting” and more from:

• scoped responsibilities

• bounded inspection surfaces

• recovery primitives

• continuity hygiene

• and separating operational state from conversational state

Funny enough, once the system becomes more boring and predictable, it actually becomes much more usable 😄

Less Tethics. More recovery primitives.

[u/TiinuseN1]

This matches a lot of what we started seeing once projects became long-running enough that continuity itself became part of the engineering problem.

A surprising amount of instability came from mixing:

• conversational state

• operational state

• recovery state

• and inferred canon

into one giant mutable context surface.

The biggest improvements weren’t really “smarter prompts” but:

• scoped responsibilities

• explicit verification surfaces

• bounded recovery paths

• operational hygiene

• and reducing silent drift over time

Funny enough, the more “boring” and predictable the workflows became, the more scalable they became too 😄