Give Claude Code system-wide memory with CLAUDE.md
Put your KPIs, role, and writing style in one file at ~/.claude/CLAUDE.md and Claude Code reads it on every prompt — across every project.
Tired of telling Claude the same things over and over? There’s one file in your home folder — ~/.claude/CLAUDE.md — that Claude Code reads at the start of every session, in every project. Whatever you put in it becomes context Claude always has.
~/.claude/CLAUDE.md is global. It applies whether you’re working in your finance folder, a marketing project, or a quick scratch session. Use it for things that are true about you or your company — not things that belong to one specific project.
What you’ll achieve
- A single file at
~/.claude/CLAUDE.mdthat Claude Code reads at the start of every session, in every project. - Persistent context for things you’d otherwise repeat: your KPIs, role, tools, and how you want Claude to write.
What to put in it
Anything you find yourself repeating. For most people that’s:
- Your KPIs — weekly active users, MRR, churn, whatever you actually track. Claude can then frame answers around them.
- Who you are — your company name, what you sell, one line about your role.
- How you want Claude to write — “plain English, no jargon” goes a long way.
- Tools you use — Slack, Notion, BigQuery, etc.
Step-by-step guide
Step 1: Open the file
Copy this into your Mac terminal and hit enter. It creates the folder, creates the file, and opens it in TextEdit (the text editor that comes with macOS):
mkdir -p ~/.claude && touch ~/.claude/CLAUDE.md && open -e ~/.claude/CLAUDE.md
mkdir -p creates the .claude folder if it doesn’t exist yet. touch creates an empty CLAUDE.md file (or leaves it alone if you already have one). open -e opens the file in TextEdit, the editor that ships with macOS. You can run this command again any time you want to edit the file — it won’t overwrite anything.
Step 2: Write what you want Claude to remember
A short, plain example:
# About me
I run product at Acme. Our main KPIs are:
- Weekly active users (WAU)
- Monthly recurring revenue (MRR)
- Net revenue retention (NRR)
When you analyse data, always reference these KPIs by name.
Write in plain English. Avoid jargon.
Save and close. That’s it.
Verification / Testing
Open a new Claude Code session in any folder and ask: “What KPIs should I be tracking?” If the file is set up correctly, Claude will name yours back to you.
Keep the file short — long memory files dilute. Every time you find yourself
re-explaining the same thing to Claude, add it here. Things that only matter
for one specific project belong in a CLAUDE.md inside that project’s folder,
not in this system-wide one.
What you learned
- Why a system-wide
~/.claude/CLAUDE.mdsaves you from repeating yourself across projects. - What belongs in it (you, your company, your KPIs, your writing style) and what doesn’t (project-specific rules — those go in a project-level
CLAUDE.md).
Related articles
Connect Tableau Server to Claude Code via MCP + PAT
Wire Claude Code into Tableau Server using the official MCP server, authenticated with a Personal Access Token — list workbooks and views from chat.
Connect Claude Code to Slack with the official plugin
Install the official Slack plugin for Claude Code with one command, then post to channels and read threads from any session — no custom MCP server needed.
Connect Claude Code to BigQuery in 2 steps with MCP
Wire Claude Code into BigQuery with Google's prebuilt MCP toolbox in two steps — list datasets, inspect schemas, and run SQL from any session.