split-memory

To split CLAUDE.md into modular instructions, create a root index file and divide the content into non-conflicting, single-axis modules organized by concern, module, or team, using explicit precedence rules to prevent contradictions across files.

You should modularize CLAUDE.md when the monolithic instruction file exceeds approximately 300 lines, becomes too hard to navigate, or when different teams require distinct conventions that risk conflicting within a single file.

Prevent conflicting instructions across multiple CLAUDE.md files by establishing a root index strategy and applying explicit precedence rules that define priority before splitting the content along a single axis like concern or team.

Yes, the split-memory modular instruction management approach directly applies to .NET project repositories where guidance becomes too large, enabling teams to maintain separate, precedence-safe configuration files within the directory layout.

The best way to organize team-specific conventions is splitting the monolithic configuration file into focused modules by team, maintaining a root CLAUDE.md index that establishes clear priority to ensure rules do not contradict across files.