split-memory

To split a large CLAUDE.md file, use a root-as-index layout pointing to a `.claude/instructions/` folder organized by a single splitting axis like concern, module, or team to ensure conflict-free rules and predictable discovery.

Modularize CLAUDE.md instructions when the file exceeds approximately 300 lines, or in multi-team repositories and modular monoliths where scoped, topic-specific instruction files are needed to prevent rule conflicts and reduce maintenance overhead.

The precedence order for modular CLAUDE.md files is deterministic: root instructions take priority over concern, which overrides module, and module overrides team, ensuring clear conflict resolution across scoped instruction files.

The best way to organize CLAUDE.md for multi-team repositories is using the root file as a concise table of contents and splitting detailed rules into a `.claude/instructions/` folder by team, module, or concern to avoid contradictory conventions.

No, you should enforce a single splitting axis when modularizing CLAUDE.md. Splitting by multiple axes simultaneously creates overlapping instructions and anti-patterns that cause contradictory rules across teams and modules.