Tal EckerlingAI Specialistעברית
Building with Claude CodeLesson 14 of 16 · 5 min

CLAUDE.md and memory: Claude that knows your business

In this lesson you'll learn

  • The CLAUDE.md file
  • Auto memory
  • Skills in Claude Code
  • How the three work together

Listen to this lesson

7 min · 7 parts · AI narration

The problem this lesson solves

If you've worked with Claude Code for a few days, you've probably met the small frustration: in every new conversation, it once again doesn't know your business's name, what tone you write in or how the project is built. And you explain again. And again.

Three tools close the gap: the CLAUDE.md file, auto memory and skills. Together they turn Claude from a talented assistant with chronic forgetfulness into a seasoned employee who knows the place.

The CLAUDE.md file: the employee handbook

CLAUDE.md is a text file that sits in the project folder, and Claude reads it at the start of every conversation. Whatever's written there, it knows.

How to start: inside Claude Code, type /init. Claude scans the project and writes a first draft, and if there's already a file, it suggests improvements instead of overwriting it. You polish from there.

What goes in it: what Claude can't guess on its own. Who you are and what the project is, language and style rules, how to check that everything works, and what's off-limits. What stays out: anything it understands on its own from the files. According to the official docs, the target is under 200 lines, and a bloated file makes Claude ignore exactly the instructions that matter to you.

Here's what a complete file for a small studio can look like. Notice how short it is:

# Noa Studio website - graphic design

## About the project
A brand website for the studio. Audience: small business owners.
The most important page for the business: the packages page (packages.html).

## Language and design rules
- All copy in English, speaking to the reader as "you".
- No exclamation marks and no emoji in the site copy.
- Brand colors are defined in style.css only.

## How to check
- After every change: open the page in the browser and make sure there are no errors.
- Always check the mobile view too.

## Boundaries
- Don't touch the originals folder (the logo source files).
- Any change to the packages page needs my approval before you make it.

The trick: every time Claude repeats the same mistake, add a line that prevents it. You can just tell it: "Add to CLAUDE.md that our dates are always in day/month/year format."

Two layers: besides the file in each project, there's a personal file, at ~/.claude/CLAUDE.md, that applies to all your projects. It loads first, and the project file adds to it.

And if you already have an AGENTS.md, an instructions file other coding tools use: Claude Code reads it when the project has no CLAUDE.md.

Auto memory

As of October 2026, Claude Code also has auto memory, which is on by default in conversations on your computer. It takes notes for itself: your preferences, corrections you gave it, and context about the project that can't be understood from the files. The notes are saved separately for each project and load in later conversations.

The question CLAUDE.md Auto memory
Who writes it You Claude
What's in it Instructions and rules Things it learned along the way
Where it lives In the project folder On your computer only

Say "Remember that this client prefers updates on WhatsApp", and it saves that to memory. Want it in the file instead? Say "Add this to CLAUDE.md". The /memory command shows you both, opens them for editing and lets you turn auto memory off. Note: this memory doesn't move to another computer, or to Claude Code conversations in the cloud.

Skills in Claude Code

A skill is a bundle of instructions for a process that repeats, and Claude pulls it out when it's needed. In Claude Code every skill is also a command: a skill called proposal gives you the /proposal command. And it has an advantage over CLAUDE.md: its full content loads only when you use it, so a long process doesn't take up space in every conversation.

The rule for choosing, from the official docs: a fact that's always true goes in CLAUDE.md. A process with several steps, or something that's relevant to only part of the work, goes in a skill.

How do you create one? You don't write it from scratch. Do the task once, really well, with all the polish, and then ask:

Ready prompt

"Take everything we did here and turn it into a skill called proposal, so next time I can type /proposal with the client's name and get a draft in exactly this format."

Claude will create a folder with a SKILL.md file inside the project's .claude/skills. And if you're signed in to Claude Code with a Claude account, the skills you turned on in your account and the plugins you installed there come here too.

How the three work together

Say you run an event photography studio:

  • In CLAUDE.md: "Light Studio's website. Audience: couples before their wedding. Warm, personal tone. English only. After every change, check the page in the browser."
  • What built up in auto memory: "The client prefers galleries of 12 photos", "The most important page is the packages page".
  • In skills: /new-gallery, which adds a gallery in the fixed format, and /price-update, which updates the price list in all the right places.

A new conversation now starts from a completely different place: Claude knows who you are, remembers what it learned, and has ready tools for the regular jobs. That's the difference between an assistant and an employee.

The habit that closes the loop, a tip from the community that I've happily adopted: end a big work session by asking "What did you learn in this conversation that's worth saving?", and send each answer to the right place. And every few months, the /doctor prompt-audit command checks whether outdated or conflicting instructions have piled up in the files.

Try it now

  1. Open Claude Code in the folder of one of your projects.
  2. Paste:
Ready prompt

"Interview me with five short questions about my business, my audience and my style rules, one question at a time. Then write a short CLAUDE.md file, under 40 lines, with four sections: about the project, language and design rules, how to check, and boundaries. Show it to me before you save."

  1. Fix whatever isn't accurate, and approve.
  2. Clear the conversation with /clear and ask for a small task. Notice whether Claude already works by the rules.
  3. Type /memory and see where everything is saved.

What to take with you

CLAUDE.md is what you decided, memory is what Claude learned, and skills are your fixed processes. Every mistake that happens twice is a line missing from the file.

Want to keep your progress?

Sign up once, at no cost: the lessons you finish are marked in your library, and the shelf of recipes and tools opens up.

Join the academy
CLAUDE.md and memory: Claude that knows your business | The Claude Academy | Tal Eckerling