Project Memory FAQs

Question 1

What is the precedence hierarchy for Claude Code project memory?

Accepted Answer

Claude reads instructions in a specific order: Enterprise policy (highest), User memory (~/.claude/CLAUDE.md), Project memory (CLAUDE.md), Modular rules (.claude/rules/), and Local memory (CLAUDE.local.md). Later sources override conflicting instructions from earlier ones.

Question 2

How do I create rules that only apply to specific folders?

Accepted Answer

You can create modular rules in the .claude/rules/ directory using YAML frontmatter. By defining a 'globs' array (e.g., globs: ['src/api/**/*.ts']), the instructions in that file will only be active when Claude is working within those specific paths.

Question 3

Can I reference external documentation in my project memory?

Accepted Answer

Yes, you can use the import syntax (e.g., @docs/ARCHITECTURE.md) within your CLAUDE.md file. This allows you to keep the main memory file concise while still providing Claude access to detailed technical documentation when needed.

Question 4

What is the difference between CLAUDE.md and CLAUDE.local.md?

Accepted Answer

CLAUDE.md is the primary project instruction file that is checked into Git and shared with the team. CLAUDE.local.md is intended for personal preferences or machine-specific paths and should be added to your .gitignore to keep it local to your environment.

Project Memory

Key Features

Use Cases

Project Memory

Key Features

Use Cases