Claude Memory

01

The problem

Most people start every Claude Code session from scratch. Claude does not automatically know who they are, what their business does, how they communicate, or what they are currently building. The first part of every conversation gets spent repeating the same context.

Claude Code can use file-based instructions and memory to carry useful context into future sessions. Once configured, it can begin with a clearer understanding of your business, voice, working preferences, and active projects.

Set it up once. Review it monthly. Benefit from it every day.

02

How Claude Memory Works

CLAUDE.md defines how Claude should work with you. Memory files preserve useful context Claude learns while working with you.

03

Step 1: Create the global CLAUDE.md file

Run these two commands in your terminal. The first creates the folder, the second creates an empty file inside it.

mkdir -p ~/.claude
touch ~/.claude/CLAUDE.md

Open ~/.claude/CLAUDE.md in any text editor and customize the template below in your own words.

# CLAUDE.md

## Who I Am

[Your name, role, and what you do]

[Your business name and what it does]

[Your experience level so Claude can calibrate its responses]

## My Business

[What you sell and who you sell it to]

[Your price points]

[Your current stage]

[Your team and responsibilities]

## How I Work

[Your schedule and working hours]

[Your communication preferences]

[Tools you use regularly]

## My Voice

[How you write and speak]

[Words or phrases you use]

[Words, phrases, or styles you avoid]

## Rules

[Things Claude should always do]

[Things Claude should never do]

[Preferences for code, content, research, or communication]

Do not store passwords, API keys, authentication tokens, banking details, Social Security numbers, protected client information, or other sensitive data in memory files.

04

Completed CLAUDE.md example

# CLAUDE.md

## Who I Am

Sarah Chen, Founder of Momentum Consulting.

Executive coach helping technology leaders transition to fractional executive roles.

15 years in corporate leadership and two years as a solo consultant.

## My Business

- Primary offer: 12-week Fractional Leadership Accelerator ($8,000)
- Secondary offer: Group coaching ($200 per month)
- Audience: VP- and Director-level technology leaders, ages 35–50, considering independent work
- Current monthly recurring revenue: $12,000
- Team: Sarah and a virtual assistant who manages scheduling

## How I Work

- Hours: 8 a.m.–3 p.m. ET, Monday through Thursday
- Fridays off
- I review work on my phone, so mobile layout always matters
- I use Notion for project management; do not recommend alternative tools unless asked

## My Voice

- Professional but warm
- A smart friend who happens to be an expert
- Short paragraphs
- No corporate jargon
- Avoid “leverage,” “synergy,” and “circle back”

## Rules

- Use my named frameworks when relevant
- Do not recommend cold calling; my strategy uses content and referrals
- Keep responses concise unless I request detail
- Test work before calling it complete

05

Step 2: Create the memory directory

Memory lives in a different place depending on which version of Claude Code you are running, so rather than guessing at a path, ask Claude Code to set it up and tell you where it put it.

Create my memory directory and a MEMORY.md index file in whichever location this version of Claude Code reads memory from. Then tell me the full path you used, so I can find it later.

Write that path down. You will want it for the monthly review in step 5.

06

Step 3: Teach Claude what to remember

When you tell Claude Code to remember something, it writes that into the same memory files you just created. It is one system, not two. Be explicit, specific, and selective, because memory should hold durable information that will improve future work, not everything you say in a session.

• Remember that my primary offer is the Fractional Leadership Accelerator at $8,000 for 12 weeks.

  Copy

• Remember that I prefer Notion over other project-management tools.

  Copy

• Remember that I do not want recommendations involving cold calling.

  Copy

• Remember that my content strategy focuses on LinkedIn posts and a weekly newsletter.

  Copy

• Remember that I am building a new landing page for the Accelerator program. The deadline is May 15. The page will be hosted on Vercel and should convert LinkedIn traffic into applications.

  Copy

07

Memory types

You do not need to label every memory manually. These categories simply help you decide what is worth preserving.

08

What to save

09

Step 4: Add project-specific instructions

You can also place a CLAUDE.md file in a project’s root folder to describe conventions that only apply to that project.

# CLAUDE.md

## Project: Accelerator Landing Page

- Framework: Next.js 14
- Hosting: Vercel
- Styling: Tailwind CSS
- Do not add a component library
- Test at a 375-pixel mobile width before calling the work complete
- Primary call to action: “Apply Now”
- The call to action links to Typeform

When instructions conflict, verify which one Claude Code applies and update the files to remove the ambiguity.

10

Step 5: Monthly memory audit

Review the Claude instruction and memory files available in this environment.

Show me:

1. What is currently stored
2. What appears outdated, duplicated, unclear, or contradictory
3. What should be removed
4. What should be updated
5. What important recurring context may be missing

Do not change or delete anything until I approve the proposed updates.

Add a monthly reminder in whichever calendar you already use, and a recurring 15-minute block is plenty. This page does not create calendar events for you.

11

Setup checklist

• 1.Create the global ~/.claude/CLAUDE.md
• 2.Add identity and role
• 3.Add business and offer information
• 4.Add working preferences
• 5.Add voice and writing guidance
• 6.Add standing rules
• 7.Create the memory directory and index
• 8.Provide five durable business memories
• 9.Provide three working-preference memories
• 10.Add current project context
• 11.Add project-specific instructions where useful
• 12.Schedule a monthly memory review
• 13.Review stored information for sensitive data

12

Before and after

An illustrative example, not a guarantee of model behavior.

13

Final takeaway

The goal is not to store everything. The goal is to preserve the small amount of durable context that consistently improves Claude’s work.

Create the foundation once, keep it current, and begin future sessions closer to the work that matters.