Learn how CLAUDE.md works, what to put in it, and why it's the single most powerful thing you can do in Claude Code.
Every time you open Claude Chat, you start over. You re-paste your client knowledge base. You re-explain your workflow. You re-establish your preferences.
With Claude Code, there's a solution: CLAUDE.md.
CLAUDE.md is a file you create in your project folder. Claude Code reads it automatically at the start of every session. You never paste it. You never explain it. It's just there, every time.
A plain text file written in Markdown format. Claude Code reads it when it starts, then refers to it throughout your session.
Think of it as your employee handbook for Claude — what to know, how to work, what matters.
| Level | Location | What it covers |
|---|---|---|
| Global | ~/.claude/CLAUDE.md |
Rules that apply to everything you do in Claude Code |
| Project | your-folder/CLAUDE.md or .claude/CLAUDE.md |
Rules for a specific project or client |
| Personal project | your-folder/CLAUDE.local.md |
Your personal notes — not shared with the team |
All three are read at once. More specific ones take priority.
Your global CLAUDE.md should contain things that are true for all your work:
# My AI Assistant Setup
## Who I am
- Name: [Your name]
- Role: [Sidekick / Content Creator / VA]
- Organization: HivePowered AI
## How I work
- I prefer concise, clear responses — no unnecessary filler
- When I say "draft," give me a full first version, not an outline
- When I say "refine," keep the structure but improve the language
- Always ask if you're unsure what I want
## Writing style preferences
- Use plain, conversational English
- Avoid jargon unless the context calls for it
- Active voice over passive voice
- Short paragraphs — max 3 sentences each
## Things to always do
- Before making changes to any file, tell me what you're about to do
- When you finish a task, summarize what you did in 2-3 sentences
- If something feels unclear, ask one clarifying question before starting
For a client project, your CLAUDE.md becomes your knowledge base:
# InSync Healthcare Staffing — Project
## Client overview
- Company: InSync Healthcare Staffing
- Owner: Beverly White (prime@hivepowered.ai is our contact)
- Industry: Healthcare staffing
- What they do: Connect RNs and allied health professionals with facilities
## Brand voice
- Warm, mentor-like, encouraging
- Beverly speaks like a career coach, not a recruiter
- Never: corporate language, jargon, salesy phrases
- Always: supportive, specific, personal
## Current priorities
- Launch travel nurse placement service
- Grow Facebook and LinkedIn following
- Drive discovery calls: calendly.com/insync-discovery
## File organization
- Content drafts → content/drafts/
- Final approved pieces → content/approved/
- Do not edit anything in content/approved/ without asking
## Key rules
- Never publish anything without Prime review
- Tag all new content with [DRAFT] until approved
Include:
- Your preferences and working style
- Client background and brand voice
- File organization rules
- Commands to run the project (npm run dev, python script.py)
- Things Claude always gets wrong without reminders
Leave out:
- Things Claude already knows how to do
- Explanations of obvious things
- File-by-file descriptions (Claude can read them itself)
- Anything that changes frequently (put that in your prompt instead)
Rule of thumb: If you'd write it in an employee handbook, put it in CLAUDE.md. If you'd just say it to someone verbally once, just say it in your prompt.
CLAUDE.md is a plain text file that can be read by anyone who has access to your project folder. If it gets committed to a shared git repository, its contents become visible to everyone.
Sensitive values belong in a .env file — which must be in your .gitignore and never shared. If you're unsure whether something is safe to put in CLAUDE.md, ask Prime first.
Option 1 — Auto-generate:
In Claude Code, type:
/init
Claude will scan your project and generate a starter CLAUDE.md based on what it finds.
Option 2 — Ask Claude to write it:
"I want to create a CLAUDE.md file for this project. Here's what I want Claude to know: [describe your client, preferences, and workflow]. Please write a clear, useful CLAUDE.md."
Option 3 — Download the template:
Use the CLAUDE.md Template in the Templates folder and fill it in.
When you work on an InSync project:
No pasting. No explaining. Just results.
The project CLAUDE.md is committed to git — the whole team shares it. Everyone who works on InSync gets the same Claude behavior.
Your personal CLAUDE.local.md is never committed — it's your own notes. Different style preferences, private reminders, things you don't want to share.
Download: The CLAUDE.md Template is ready in the Templates folder.
Next lesson: Skills, hooks, and MCP — the three features that separate power users from everyone else.
Download and use these templates in your own projects.
HivePowered AI — AI Like a Pro Training