Home › Blog › CLAUDE.md Best Practices When You’re New to It

CLAUDE.md Best Practices When You’re New to It

The best CLAUDE.md file is a short, specific document that encodes your business context, not someone else’s. If your file came from a template and you haven’t edited it much, it is almost certainly doing less than you think. Anthropic’s getting-started guide shows where this file sits in your Claude workspace.

I configure Claude for solo operators and small business owners, and the single most common mistake I see is a CLAUDE.md file that was copied, not written. Standing, owner-specific context is the entire premise of Claude’s design. This guide covers the CLAUDE.md file best practices that actually move the needle when you are just getting started. If you have not created the file at all yet, start with my walkthrough on how to create your first CLAUDE.md file, then come back here.

Why a Copied Template Is Working Against You

Template or purpose built decision test - a guide to CLAUDE.md file best practices
The one-line test that separates a copied template from a configured CLAUDE.md.

A template gives you someone else’s priorities. A working CLAUDE.md file encodes yours.

When I sit down with someone for a one-on-one Claude session, I almost always find the same thing: a file full of instructions that apply to a software developer, a content agency, or a research team. That person is a solo bookkeeper, a freelance designer, or a small ops manager. The file and the person have almost nothing in common.

Claude reads your CLAUDE.md file at the start of every session and uses it to orient itself. If that file is noisy or generic, Claude spends its attention on instructions that do not apply to your work. Most public CLAUDE.md examples were written by developers, full of build steps and architecture notes. Those are developer priorities. If you are a solo consultant or small business owner, your priorities look different, and your file should reflect that.

CLAUDE.md File Best Practices: Start with Your Business Context

Write your first CLAUDE.md in this order - a guide to CLAUDE.md best practices
Context first, preferences second, rules third. Corrections keep it alive.

The first section of your CLAUDE.md file should answer one question: who am I, and what do I do?

This is not a formality. Claude uses context to make judgment calls every time it responds. If it does not know you run a 3-person marketing consultancy focused on B2B SaaS clients, it defaults to generic. Give it the context and the defaults improve immediately.

Here is what I tell clients to write at the top of their file:

  • Your role or title
  • What your business does and who it serves
  • The primary types of work you bring to Claude
  • Any industry-specific language or terminology Claude should know

Two to four sentences is enough. This is a CLAUDE.md file best practice that costs you almost nothing and pays off in every session.

Keep It Short. Seriously.

One of the most counterintuitive CLAUDE.md file best practices is that shorter usually performs better than longer.

Claude reads the whole file at the start of every session, so every line you add competes for attention with the lines that actually matter. A bloated file does not make Claude smarter. It buries your real instructions under filler.

I aim for under 300 words for most first-time clients. If you find yourself writing paragraphs of explanation, stop. Claude does not need justification. It needs clear direction.

Write Instructions as Plain Statements

This is the part most people get wrong when they write their first CLAUDE.md file from scratch.

Plain statements outperform polite requests every time. Do not write “Please try to keep responses concise.” Write “Keep responses under 150 words unless I ask for more.” Do not write “I prefer a friendly tone.” Write “Use a direct, conversational tone. No corporate phrasing.”

Claude is not a person who needs coaxing. It is a system that follows instructions. The more specific and declarative your instructions, the more reliably it follows them. This is one of the core Claude for small business insights I share in every onboarding call.

Do This, Not That: A Quick Comparison

Here is how the difference between a vague file and a working one looks in practice.

Avoid ThisDo This Instead
“Be helpful and professional.”“Use direct, plain language. Avoid corporate jargon.”
“I work in marketing.”“I run a solo B2B content consultancy. My clients are SaaS companies with 10 to 200 employees.”
“Please format things nicely.”“Default output: plain paragraphs. Use bullet points only when I ask.”
“Try not to be too verbose.”“Cap responses at 200 words by default. I will ask if I need more.”
A 600-word template copied from the internetA 200-word file written specifically for your work
“Never say anything offensive.”“Never recommend competitors by name. Never speculate on pricing.”

Encode Your Output Preferences Explicitly

What a working CLAUDE.md encodes - a guide to CLAUDE.md file best practices
Four short blocks beat six hundred copied words.

One of the highest-value blocks I show clients is a simple output preferences block. It takes five minutes to write and changes almost every response you get.

Tell Claude exactly what a good response looks like for your work. Consider specifying:

  • Default length (short, medium, long)
  • Format (plain text, bullet points, structured sections)
  • Tone (formal, conversational, punchy)
  • What it should never do by default (no headers unless asked, no disclaimers, no em dashes)

This is the part of how to use Claude effectively that most tutorials skip. A tutorial will show you how to open a session. It rarely shows you how to make every session feel configured for your brain.

Think of output preferences as your standing order. You write it once, and Claude follows it every time without you having to repeat yourself.

Add Corrections as You Discover Them

Your CLAUDE.md file is not a document you finish. It is a document you refine.

Every time Claude does something that annoys you, ask yourself whether it is a one-off or a pattern. If it is a pattern, add a correction to your file. One sentence is enough. “Do not add a summary paragraph at the end of responses.” “Do not suggest follow-up questions unless I ask.”

This is one of the most practical habits I point people toward: using your daily sessions as a feedback loop for your configuration. The file gets better every week if you treat it that way. When you are ready to go deeper than the day-one version, the complete CLAUDE.md configuration guide covers the full structure.

This is also a big part of the answer to whether Claude is worth it for most small operators. The value compounds over time precisely because you are building a configuration that fits your actual work patterns, not someone else’s defaults.

Review It Monthly

Clean desk with notebook ready for a monthly configuration review - a guide to CLAUDE.md file best practices
Ten minutes a month keeps the file honest as your work changes.

Your work changes. Your CLAUDE.md file should change with it.

I recommend a 10-minute monthly review. Read through the whole file. Remove anything that no longer applies. Add anything new you have been repeating in prompts. Update your business context if your focus has shifted.

This is especially relevant for small business owners using Claude who are still figuring out where AI fits in their workflow. The file you write in month one will not be the right file in month three. That is fine. Build the habit of updating it.

If you would rather start from a configured baseline than a blank page, the Foundation Plugin builds that starting structure around your business through a guided intake, and the practices in this guide keep it sharp from there. If you want to go further, start with Claude solo setup help.

Your Do-This-Now Steps

  1. Open your current CLAUDE.md file. Read it from top to bottom and ask: does this actually describe me and my work?
  2. Delete anything generic. If a line could apply to anyone, remove it or rewrite it to be specific.
  3. Write or rewrite the first section as a business context block: who you are, what you do, who you serve.
  4. Add an output preferences block. At minimum: default length, format, and tone.
  5. Write three “never do this” rules based on things Claude has done in past sessions that annoyed you.
  6. Put a monthly calendar reminder to review and update the file.

These steps apply whether you are in your first week or you have been using Claude for months without getting much out of it.

Frequently Asked Questions

What goes in a CLAUDE.md file?

Your CLAUDE.md file should include your business context, the types of work you bring to Claude, your preferred output format and tone, and any standing rules about what Claude should always or never do. Think of it as a standing brief that Claude reads before every session.

How long should a CLAUDE.md file be?

For most solo operators and small business owners, under 300 words is the right target. Longer files can dilute the instructions that matter most. Write only what you actually want applied every single session.

Can I have more than one CLAUDE.md file?

Yes. You can keep a global file with your standing preferences and a folder-level file with project context. When the two overlap, the more specific project file is the one to refine. For most people just getting started, one well-written file is enough.

Is CLAUDE.md different in Claude vs Claude Code?

Claude Code is Anthropic’s developer-focused tool, and the CLAUDE.md file originated there. Claude applies the same configuration logic to business workflows for non-developers. The best practices are largely the same: short, specific, context-first, and plain-statement instructions. I break down the broader differences in my Claude vs Claude Code comparison.

Start Here: Your 10-Minute Action

Open your CLAUDE.md file right now. Delete the first generic line you see. Replace it with one sentence that is specifically true about your business. That single edit will do more for your sessions than any template ever will. Copying a template feels fast. Configuring on purpose is what actually pays.

If you want me to look at your file directly and tell you what to fix, I offer a free 20-minute call where I do exactly that. Book a call, bring your current CLAUDE.md, and I will help you turn it into something that actually works for you.

From reading to running

You could have this running by tonight.

This guide is the do-it-yourself route. The faster route is doing it live with me, 1-on-1, until it works on your machine. My calendar is open day or night, so pick whichever end of the day you actually have free.

See also: Claude Standing Instructions: The File Every Owner Writes.

Michael Robichaud

Written by

Michael Robichaud

Claude consultant and founder of Strategized.ai. Michael sets Claude up one-on-one for professionals and small teams, connected to your tools and trained on your real work, and designs custom Claude plugins for specific professions.

 ·  Connect on LinkedIn →

On this page

  1. Loading sections…

About the Author

Michael Robichaud

Founder of Strategized.ai and CoworkConsultant.com. 30 years across enterprise sales, digital marketing, and building businesses. Configuring Claude for professionals who came to AI from the business side, not the other way around.

Stuck on something specific?

Book a free 20-minute call. Open calendar, evenings and weekends included.

The Strategy Stack Ecosystem

Consultant is one part of a larger system.

Want this set up for you instead?

Reading is one thing. Having a Claude workspace built around your business is another. That is the work I do with owners and teams here at CoworkConsultant.com, and it starts with a short call.

Keep Exploring

More from the blog

Strategy, GEO/AEO, consulting perspectives.

Browse the Blog →

Need it built for you?

1:1 strategy, done-for-you workspace builds, fractional AI advisory.

Visit Strategized.ai →

Claude plugins by profession

Ready-made Claude plugins for your role, $99 each. Or start free with the Foundation plugin.

Browse the Claude plugins →