Every time you open a new Claude session, you face the same problem. You have to remind it who you are. You explain your business, the project you’re working on, the tone you want, the constraints that matter. By the time Claude is properly briefed, you’ve spent ten or fifteen minutes on setup rather than work.
This is the friction that stops most business owners from getting the leverage they’re looking for from AI. The tool is capable. The session setup is what slows you down.
The fix is a context file. A context file is a document Claude reads at the start of every session. It carries the information that doesn’t change week to week — your business background, your working rules, your active projects. It turns every new session into a continuation of the last one, rather than a blank start.
This post covers what goes in a good context file, how to build one in about thirty minutes, and how to keep it useful as your work evolves. It’s part of a broader guide on using Claude AI for productivity — specifically the setup layer that most people skip.
Why Most People Under-Use Claude
The standard way of using Claude is: open a new chat, describe what you want, get a result. Repeat tomorrow.
The problem with that approach is that Claude starts fresh every time. It doesn’t know you run a consulting business with eight active clients. It doesn’t know you always want British spelling, that your email tone is direct but warm, or that the project you’re working on right now is a website launch for Q3. You carry all of that context. Claude doesn’t.
This is the gap between treating Claude as a capable tool you point at individual tasks and treating it as something closer to a team member who already knows the business. The second mode is where the real leverage is — and it requires giving Claude the full picture upfront, not question by question.
A context file bridges that gap. It gives Claude the permanent background it needs so your sessions start informed, not blank.
What a Claude Context File Contains
A useful context file has four sections. None of them needs to be long. The goal is to give Claude what a good freelancer would need to start working without a lengthy briefing call.
1. Your Business Background
Who you are, what your business does, who it serves, and what you’re focused on this quarter. Two or three paragraphs is enough. Include your revenue model, your ideal customer, and any strategic priorities that are active right now. This is the section Claude needs most to calibrate its responses — without it, every session requires you to re-establish who’s asking and why.
2. Your Working Constraints
The rules Claude should always apply: your preferred spelling (British or American), your tone, your formatting preferences, and the things you never want it to do. If you write for a specific audience, describe them here. If there are claims or topics you won’t make in client-facing copy, list them. These are the guardrails that shape every output Claude produces for you.
3. Your Active Project List
What you’re working on right now — not every task, but the major threads. One sentence per project explaining what it is and what you’re trying to accomplish with it. This is the section that changes most frequently, but it’s also the one that saves the most time. When Claude knows your active projects, it can place your requests in context rather than treating each one as an isolated task.
4. Your Output Preferences
How you want Claude to structure its responses: long-form or concise, bullet lists or prose, whether it should ask clarifying questions before producing output or just produce. Some people want to see the reasoning. Others want the result only. Define this once and you stop correcting it on every session.
How to Build Yours in 30 Minutes
The temptation is to make this comprehensive. Don’t. Start with the minimum that would get a good freelancer up to speed in an hour — you can always add more later. Here is the four-step build sequence:
Step one: Write a two-paragraph business summary. What the business does, who buys it, and what you’re focused on right now. Keep it factual and specific — not aspirational language, but the kind of plain summary you’d give someone you were hiring.
Step two: List your five most important working constraints. Tone, spelling, what you never want to see, who the audience is. If a constraint has caused you to correct Claude more than once, it belongs here.
Step three: Write down your three most active projects — one sentence each on what each one is and what you’re trying to accomplish. If a project doesn’t have a clear goal yet, it’s not ready to go into the context file.
Step four: Set your output preferences. Long or short? Lists or prose? Ask questions or produce? A single paragraph here will shape hundreds of future sessions. This is also a good place to specify how you want automated tasks structured when Claude runs them on your behalf.
The whole file will run to three or four pages. You can build it in a single focused session, and the return on those thirty minutes compounds immediately.
Where to Put Your Context File
Where your context file lives depends on how you use Claude.
If you use Claude.ai, create a Project for your business and add the context document to the Project Instructions. Every conversation inside that Project will start with Claude having read your context file automatically. You can create separate Projects for separate clients or contexts — the objective is for Claude to have the right context for the work at hand.
If you use Claude Code or another developer tool, the file is typically called CLAUDE.md and lives in the root of your working directory. This is the same setup used to turn Claude into a project manager — the CLAUDE.md provides the context, and a paired actions.md provides the task queue, so sessions start with Claude already oriented and working.
Both approaches achieve the same outcome: Claude reads the file before your first message, so the session starts informed rather than blank.
How to Keep It Current
A context file that isn’t updated becomes noise. If Claude is referencing a project that ended three months ago, it’s applying effort where it doesn’t belong — and producing output that’s calibrated to the wrong priorities.
The simplest maintenance habit: review the active project section at the start of each week. Add what’s new, retire what’s done, update the priority order. The whole pass takes five minutes when done regularly and an hour when ignored for a month.
The business background and constraints sections change less often. Update them when something meaningful shifts — a new product, a new audience segment, a strategic pivot. If Claude starts producing output that consistently misses the mark, the context file is usually the first place to look. The answer is often that the file reflects last quarter’s situation, not the current one.
This is the same maintenance logic that underpins any good system: it only works if the inputs reflect reality. The context file is no different from any other Claude workflow for business — it earns its keep when it’s kept honest.
The Bigger Shift
A context file is the foundation of a different relationship with Claude. Once it knows who you are and what you’re working on, you stop having to orient it and start being able to direct it. Sessions that used to begin with ten minutes of briefing now begin with work.
For business owners who feel like they’re carrying too much in their head, this matters beyond the efficiency gain. The mental load of running a business doesn’t reduce when you use AI poorly — you still have to hold everything in working memory and re-explain it constantly. A context file offloads that. You put the context somewhere Claude can read it, and you stop being the only place that information lives.
The NP System is built on a similar principle: the system captures and organises what’s in your head so your attention can go where it’s actually needed. A Claude context file does the same thing for your AI sessions — it gets the right information in front of Claude at the moment it matters, so the output is calibrated to your actual situation rather than to what you managed to explain in the first message.
The business owners who get the most from Claude aren’t the ones asking the best questions. They’re the ones who’ve done the work of telling Claude exactly who they are, what they’re building, and what good looks like.
Next Steps
If you want to see how this works across a whole business — including the project structure, the constraints layer, and the task-queue system that keeps Claude working between sessions — the free NP System course walks through the full setup. Or take the productivity quiz to identify which part of your current setup is creating the most friction.
Frequently Asked Questions
What is a Claude context file?
A Claude context file is a document that gives Claude persistent information about your business, working preferences, and active projects. It is loaded at the start of every session so you don’t have to re-brief Claude each time you open a new chat.
How do I give Claude context in Claude Projects?
In Claude.ai, create or open a Project and add your context document to the Project Instructions field. Every conversation inside that Project will start with Claude having read your context automatically.
What should go in a Claude context file for business?
A useful business context file covers four areas: your business background and ideal customer, your working constraints and tone rules, your active project list, and your output format preferences. Three to four pages covers all four without becoming a manual.
How long should a Claude context file be?
Three to four pages is usually enough. The goal is to give Claude what a competent freelancer would need to start working without a long briefing call — not a comprehensive reference document.
How often should I update my Claude context file?
Review the active project section weekly and update it when priorities shift. The business background and constraints sections only need updating when something meaningful changes — a new product, a new audience, or a significant strategic shift.
