split-memory

Split oversized CLAUDE.md files into modular instruction files with precedence rules.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/shahdanish/vibepos --skill split-memory-shahdanish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: split-memory
Source: https://github.com/shahdanish/vibepos/tree/main/skills/split-memory
Command: npx skills add https://github.com/shahdanish/vibepos --skill split-memory-shahdanish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the maintenance and clarity problem of a single monolithic CLAUDE instruction file becoming too long, hard to navigate, and prone to contradictory rules.

Core Features & Use Cases

  • Splitting strategy with precedence: Defines a safe order for how rules across multiple files should override each other to prevent conflicting behavior.
  • Right moment to split: Recommends splitting only when the instruction set grows beyond practical limits (e.g., around 300 lines) or when multiple teams/concerns need different guidance.
  • Organized folder patterns: Provides concrete layouts for splitting by concern, module, or team using a root index and additional topic files.
  • Use-case example: When you have a growing codebase like a .NET solution and your CLAUDE guidance spans architecture, testing, data access, and deployment, you can split instructions so each topic lives near its domain and remains easy to find.

Quick Start

Ask the AI to reorganize your CLAUDE instructions by concern or module, create a root index, and apply the stated precedence rules to ensure there are no contradictory instructions across files.

Frequently Asked Questions about split-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split an oversized CLAUDE.md file into multiple instruction documents?

To split an oversized CLAUDE.md, create an index-style root file and divide instructions across additional topic files using a single splitting axis like concern, module, or team. This modularization prevents conflicts and preserves consistent behavior across your project.

How do I prevent conflicting rules when using multiple CLAUDE instruction files?

Prevent conflicting rules across multiple CLAUDE instruction files by applying explicit precedence rules within a root index file. These rules define a safe override order so that instructions split by concern, module, or team never contradict each other during processing.

What is the best folder pattern for modularizing team workflows in CLAUDE.md?

The best folder pattern for modularizing team workflows uses a root index file that points to additional topic files organized by a single axis. Splitting instructions by team, concern, or module ensures each topic lives near its domain and remains easy to find.

When should I not modularize my CLAUDE instructions?

You should not modularize CLAUDE instructions if your project is small enough that a single document remains clear and navigable. Splitting prematurely adds unnecessary overhead, so wait until the instruction set grows beyond approximately 300 lines or multiple teams need different guidance.

Can I organize CLAUDE.md instructions by module for a growing codebase?

Yes, you can organize CLAUDE.md instructions by module for a growing codebase. By using a root index file and splitting instructions by module, each topic lives near its specific domain, making architecture, testing, and deployment guidance easier to locate and maintain.