rules-migration

Migrate your monolithic CLAUDE.md into Claude Code's `.claude/rules/` directory structure by splitting instructions into path-specific rule files. This automation preserves all content, organizes guidelines by context (frontend, backend, tests), and enables path-aware distribution across teams while maintaining auditability.

Path-specific rules apply instructions only to designated file paths or types using glob patterns—for example, `src/**/*.ts` for backend code. This approach eliminates monolithic guidance, ensures context-aware compliance, and lets different teams maintain separate guidelines within a single project without manual coordination.

Yes. The modular rules system splits your CLAUDE.md into separate path-bound files like `frontend/react.md`, `backend/api.md`, and `core.md`. Each file targets specific directories and file types, making project instructions instantly accessible and actionable across frontend, backend, tests, and shared memory contexts.

Migration fully preserves all existing content while restructuring it into organized, path-specific rule files with frontmatter. The process enforces separation between global and path-specific rules, maintains auditability throughout, and supports ongoing maintenance without information loss.

Modular rules enable automated, path-aware rule distribution across teams, reducing manual coordination overhead. Each team accesses only relevant guidelines for their domain, enforcement becomes context-specific, and the system scales without sprawling documentation that grows difficult to maintain.

Monolithic CLAUDE.md files become unwieldy and hard to maintain as projects grow. Splitting into modular, path-specific rules eliminates complexity, improves clarity for team collaboration, enables granular path-aware guidance, and reduces refactoring effort when guidelines need updates or reorg across domains.