Where Claude looks for your rules
Rules sit at different levels, like a company handbook, a department's way of working and the brief for one job. The level you put a rule at decides which work it applies to. Here's the map, where each file lives and when a rule belongs in settings.
Once a team has used Claude for a few weeks, the same questions come up. Why did it follow this rule in one folder and not another? Why does a new chat still remember things? Where do I put a rule so I stop repeating it? This is the map I draw for them.
Rules sit at different levels, like a company handbook, a department's way of working and the brief for one job. The level you put a rule at decides which work it applies to.
Where Claude looks for your rules
The Claude app
claude.ai and the desktop app
A separate place from your folders. Same account, so skills can show up in both.
Claude in VS Code
works on the folder you open
You, in every folder ~/.claude/CLAUDE.md
All the team's work team/CLAUDE.md
Question bank
CLAUDE.md
Gap analysis
CLAUDE.md
Proofreader
CLAUDE.md
A folder above reaches down. Folders side by side don't see each other. Keep each rule at the highest level it's true for.
Two places, same account
The Claude app (claude.ai and the desktop app) has chats, projects, skills, artifacts and scheduled tasks. Your settings and skills there apply to all your chats in the app. It's a separate place from your folders in VS Code. A skill you make in the app can show up in VS Code when you're signed in to the same account (type /skills to see which ones). To be sure, keep a copy in your personal .claude folder.
Claude in VS Code works on the folder you open, and reads rules at three levels:
- You, in every folder. The
CLAUDE.mdin the .claude folder in your user folder. How you like answers: short, in your language, ask before guessing. Only you see it. - All the team's work. A
CLAUDE.mdat the top of the team folder. The house rules: your format, trusted sources, no personal data. Shared with the team. - One job. A
CLAUDE.mdin each job folder: the question bank's format, "quote the source line" for a gap analysis, "score a draft against the rules" for a proofreader.
When you open a job folder, Claude reads your rules, then the team rules, then the job's rules.
Folders side by side don't see each other: the question bank folder doesn't see the proofreader's rules. A folder above does reach down, though. Put the team rules in the team folder once and every job folder inside it gets them.
If two files say different things, Claude may follow either one. Keep each rule in one place, at the highest level it's true for.
Claude doesn't make a CLAUDE.md for you. Type /init, or ask it: "make a CLAUDE.md for this folder from what we've agreed so far." After that it adds to it when you ask, so tell it when something's worth keeping.
Claude also keeps its own notes about each project as you work, in your personal .claude folder. That's why a new chat still remembers things. Type /memory to read or clear them.
Where each file lives
On Windows your user folder is C:\Users\<your name>. On a Mac it's your home folder, shown as ~.
- Your rules, every folder: ~/.claude/CLAUDE.md
- Your skills, every folder: ~/.claude/skills/<name>/SKILL.md (type /name to use one)
- Team rules: CLAUDE.md at the top of the team folder
- Team skills: .claude/skills/<name>/SKILL.md inside the team folder
- One job's rules: CLAUDE.md in the job folder (open this folder in VS Code)
- Settings, such as a web rule: .claude/settings.json inside the team folder
- Claude's own notes: ~/.claude/projects/…/memory/
Folders that start with a dot are hidden. On Windows, in File Explorer choose View, Show, Hidden items. On a Mac, press Cmd + Shift + full stop in Finder. When you share the team folder, check the .claude folder goes with it, or your skills stay behind.
CLAUDE.md is the one Claude reads by itself
CLAUDE.md is the only file Claude reads at the start of every chat. A voice.md, a style guide or a format file is read when CLAUDE.md points to it. Keep CLAUDE.md short and point to the rest.
There are two ways to point. Write @house-style.md and the file is loaded every time. Write "follow house-style.md when you write learner material" and Claude opens it when the job needs it. Skills work the second way: Claude uses one when the job matches, or straight away when you type its name after a slash.
Make a CLAUDE.md for this folder from what we've agreed so far. Keep it under 40 lines. Include: keep answers short, a summary first and the detail only if I ask. Use our format skill for any learner material. Only use the documents in this folder unless I say otherwise, and if you need an outside source, use official ones and tell me each time. Never put personal data in a file. Point to other files instead of copying them in. Show me the file before you save it.
A request in CLAUDE.md, a rule in settings
Claude reads CLAUDE.md and tries to follow it. Settings are rules the program enforces, so Claude can't talk its way round them.
A request in CLAUDE.md, a rule in settings
In CLAUDE.md
“Use official sources and tell me when you do.”
- Flexible: Claude can still settle a contradiction
- A request. In a long chat Claude can drift
In .claude/settings.json
{ "permissions": { "ask": ["WebSearch", "WebFetch"] } }- Enforced every time, in that folder only
- Change ask to deny for a hard stop
Use both: CLAUDE.md says which sources are good, the setting makes sure you see each one.
You don't need to type the file. Ask Claude: "In this folder's .claude settings, make Claude ask me before any web search or web page." For a hard stop, change ask to deny. Use both together: the CLAUDE.md rule says which sources are good, and the setting makes sure you see each one.
Sharing your rules, and keeping them tidy
A shared channel or drive is a good place to start: put the team folder (with its .claude folder) there, and each person copies it to their laptop. Copies drift, so agree one owner per file. When several of you edit the same rules, move to a private GitHub repository, where every change is saved with who, when and why.
Start a new chat for each new piece of work. It forgets the last conversation and goes back to your CLAUDE.md. Then put a reminder in your calendar for two or three months from now, and ask Claude to do the first pass of the tidy-up:
Read every CLAUDE.md in these folders and list anything that clashes or is out of date.