You're the lead developer on a Suffolk student team building a class project in Claude Code. You've written excellent coding standards and want every teammate to follow them automatically when they pull the repo. You put them in ~/.claude/CLAUDE.md on your laptop.
A week later, three teammates report that Claude is ignoring the standards.
What's going on?
Why did you pick that answer? Two or three sentences. The act of articulating it is what builds the judgment — not the click that follows.
The CLAUDE.md hierarchy has three levels: user-scoped (~/.claude/CLAUDE.md, personal to each developer, not shared), project-scoped (.claude/CLAUDE.md or CLAUDE.md in the repo, shared via version control), and directory-scoped (subdirectory CLAUDE.md files for area-specific conventions). Standards that should apply to the whole team must be committed to the project repo. Putting them in your home directory means they apply only to you.
There's no memory cache that needs clearing — teammates simply never received the file because it was never in the repo.
The file is correctly named CLAUDE.md. The issue is location, not name.
No such command exists. User-scoped configs are intentionally per-user; sharing them requires moving them into the project repo.