Claude Code Memory Reference FAQs

Question 1

Can I apply rules only to specific folders?

Accepted Answer

Yes, by using modular rules in the .claude/rules/ directory and adding 'paths' frontmatter with glob patterns, you can scope instructions to specific file paths.

Question 2

What is the priority order for Claude Code memory files?

Accepted Answer

Claude Code follows a specific hierarchy: Enterprise policy (1), root CLAUDE.md (2), .claude/CLAUDE.md (3), modular rules (4), user global memory (5), and finally local project overrides (6).

Question 3

How do I view what memory files are currently loaded?

Accepted Answer

Use the /memory command within the Claude Code interface to see all active memory files and their contents.

Question 4

How do I create a project-specific CLAUDE.md file?

Accepted Answer

You can bootstrap a new configuration by running the /init command within the Claude Code CLI, which creates a template in your project root.

Question 5

What is the purpose of CLAUDE.local.md?

Accepted Answer

CLAUDE.local.md is intended for personal project preferences. It is typically gitignored and allows you to set custom instructions that don't affect other team members.

Claude Code Memory Reference

About

Key Features

Use Cases

Claude Code Memory Reference

About

Key Features

Use Cases