Memory Management FAQs

Question 1

When should I use the .claude/rules/ directory?

Accepted Answer

Use the rules directory for modular, file-specific instructions that should only load when relevant, such as specific patterns for React components, SQL migrations, or test files using glob matching.

Question 2

What is the priority hierarchy for Claude Code memory?

Accepted Answer

Claude loads memory in this order: Global (~/.claude/CLAUDE.md), then Project Root (./CLAUDE.md), then Project Config (./.claude/CLAUDE.md), and finally conditional Rules (./.claude/rules/*.md) which always have the highest priority.

Question 3

Can I share memory settings with my team?

Accepted Answer

Yes, by committing the project-level CLAUDE.md and .claude/rules/ files to your version control system, all team members using Claude Code will benefit from shared context and standards.

Question 4

How do I manage personal versus project preferences?

Accepted Answer

Store personal preferences like tab width or tool shortcuts in the global ~/.claude/CLAUDE.md file, which acts as a fallback that project-specific configurations can override.

Question 5

What are common mistakes to avoid in memory configuration?

Accepted Answer

Avoid putting project-specific content in global files, creating overly large CLAUDE.md files instead of modular rules, and including vague instructions or redundant documentation that Claude can already discover.

Memory Management

Key Features

Use Cases

Memory Management

Key Features

Use Cases