claudecode-rules-organizing

Dynamic loading via paths frontmatter lets you organize file-type specific rules into .claude/rules/ and load them on-demand. Extract targeted rules from CLAUDE.md, structure them by category in .claude/rules/, and annotate with paths frontmatter so rules load only when relevant files are accessed, shrinking initial context.

Separate universal rules that stay in CLAUDE.md from file-type specific rules moved to .claude/rules/. Create subdirectories for API, frontend, testing, and other categories, then add paths frontmatter to each rule file to trigger on-demand loading when those file types are opened.

Universal rules apply across all files and belong in CLAUDE.md for immediate availability. Category-specific rules target API, frontend, testing, or other file types and should live in .claude/rules/ with paths frontmatter to load selectively, keeping startup context lean.

Yes. Dynamic loading via paths frontmatter is designed for large projects where selective rule loading optimizes context. Organize rules by file type or domain in .claude/rules/, annotate with paths matching your project structure, and rules load on-demand for relevant files.

Paths frontmatter is metadata that specifies which file patterns trigger a rule's load. Annotate each rule file in .claude/rules/ with paths matching your file types—e.g., paths: src/api/**—and the rule loads only when those files are accessed, reducing unnecessary context consumption.

Your CLAUDE.md retains universal rules that apply everywhere. Extract only file-type specific guidance into .claude/rules/ with explicit paths, keeping CLAUDE.md lean and focused on project-wide conventions, then both sources load together when relevant.