claude-code-project-memory
Claude Code Project Memory (Jan 2026)
Configure CLAUDE.md project memory so Claude Code gets stable, scoped instructions across sessions while keeping token cost low.
Quick Reference
| Memory Type | Typical Location | Purpose |
|---|---|---|
| Managed policy | OS-dependent (see official docs) | Organization-wide standards (security, compliance) |
| Project memory | ./CLAUDE.md or ./.claude/CLAUDE.md |
Shared project context and conventions |
| Project rules | ./.claude/rules/*.md |
Modular, topic-focused rules (testing, security, style) |
| User memory | ~/.claude/CLAUDE.md |
Personal preferences across projects |
| Project memory (local) | ./CLAUDE.local.md (git-ignored) |
Local-only, project-specific preferences |
How Loading Works (High Level)
- Recursive loading: from the current working directory up to (but not including) filesystem root (
/). - On-demand loading: nested
CLAUDE.mdfiles under the cwd are loaded only when Claude reads files in those subtrees. - Imports:
@path/to/filepulls in additional context (max depth: 5;~supported).
More from vasilyu1983/ai-agents-public
product-management
Founder-PM toolkit for discovery, roadmaps, prioritization, and PMF measurement. Use when planning product strategy, metrics, or roadmaps.
684software-architecture-design
Designs system structure across monolith/microservices/serverless. Use when structuring systems, scaling, decomposing monoliths, or choosing patterns.
519software-ui-ux-design
Designs and audits UI/UX with WCAG 2.2 accessibility. Use when designing flows, running heuristic reviews, or defining design systems.
383qa-testing-playwright
E2E web testing with Playwright. Use when writing tests, debugging flakes, or setting up CI with selectors, sharding, and network mocking.
372document-pdf
Extract text/tables from PDFs, create formatted PDFs, merge/split/rotate, and handle forms. Use for any PDF generation or parsing task.
327qa-testing-strategy
Risk-based test strategy for software delivery. Use when defining coverage, setting CI gates, managing flaky tests, or establishing release criteria.
317