Five files that teach Claude your business

Five short files (plus any extras) that Claude loads every session, so its answers fit your business.

1you.md
2business.md
3customers.md
4strategy.md
5brand.md

Claude reads all 5, every session

Answers that sound like you
1you.mdOwner, runs sales, short answers
2business.mdWebsites for dental clinics
3customers.md“My front desk is drowning”
4strategy.md5 new clinics this quarter
5brand.mdCalm, direct, never “circle back”

Claude reads all 5, every session

Answers that sound like you
  1. Five files: you, business, customers, strategy and brand.
  2. Claude reads all five at the start of every session.
  3. The result: answers that sound like you.
45 to 60 minNo code

You need

  • A Claude account (a paid plan for the main route
  • Free works with the Project route near the end)
  • The Claude desktop app
  • A Mac or Windows computer
  • A few real emails or posts you wrote

Every new hire gets an onboarding. Your AI needs one too. Until you tell Claude who you are, its answers stay generic. Five short files fix that, plus a few extras if your business needs them. Claude interviews you, writes the files, and links them itself. After that, it loads them at the start of every session, so you stop re-explaining your business.

01 / 08

What you get and what you need

The idea comes from Anthropic's own prompting guide: treat Claude like a new employee who lacks context. You end up with plain text files in one folder (the .md ending means plain text): five core files, up to four extras, and CLAUDE.md, which ties them together. A session is one conversation in Claude.

5
core context files
4
extras at most
45 to 60 min
start to finish
FileWhat it holds
you.mdYour role, how you make decisions, how you like answers
business.mdWhat you sell, to whom, and how you deliver it
customers.mdWho they are, the words they use, what makes them say no
strategy.mdThis quarter's goals, and what you're saying no to
brand.mdYour voice, the words you use, and the words you ban, including the ones that make text sound AI-written

CLAUDE.md is the file Claude reads at the start of every session (memory docs). Each line that starts with @ tells Claude to open another file too, so everything loads together and you never paste anything in. Keep it short, with your top three rules in it. Think of it as the first page of the onboarding binder.

DiagramHow CLAUDE.md links your files

Fig 1.1How CLAUDE.md links your files

Extras your business may need

After a few basic questions, Claude proposes at most 4 extras. Each comes with a reason, and you approve them. Every linked file loads every session, so the cap keeps things light.

Business typeLikely extras
Shop, maker, restaurantproducts.mdfaq.mdplaces.mdcompliance.md(food, cosmetics, supplements)
Agency, consultant, freelanceroffers.mdprocess.mdtools.mdfaq.md(team.md if you have staff)
Trades, cleaning, salon, local serviceoffers.mdprocess.mdplaces.mdfaq.md(team.md if you have staff)
Clinic, legal, finance, real estatecompliance.mdoffers.mdprocess.mdfaq.md(places.md if clients visit you)
Coach, course creator, membershipoffers.mdfaq.mdprocess.md

What you need

No paid plan? Use the Claude Project route near the end.

02 / 08

Install Claude Code

Claude Code is the part of Claude that can read and write files on your computer. I recommend the desktop app. Anthropic keeps adding features to it, so it's worth learning. It includes Claude Code, so you don't need Node.js or the command line tool (desktop quickstart).

  1. Go to claude.com and choose the Mac or Windows version.

  2. Install the app and sign in with your paid account.

Screenshot · Oct 2026
Download the desktop app for Mac or Windows
The Claude download page with download buttons for Mac and Windows
Fig 2.1Download the desktop app for Mac or Windows
  1. Click the Code tab at the top centre of the app.

    You should see the Code screen.

03 / 08

Run the interview

Claude asks. You click or type short answers.

  1. In Finder or File Explorer, create an empty folder in Documents. Name it after your business.

    It has to exist before you pick it in step 3.

  2. In the Code tab, choose Local. Local means Claude works on files on your own computer (desktop quickstart).

  3. Click Select folder and pick the folder you just made.

    You are now in a blank session that works inside that folder.

Fig 3.1Illustration of the Code tab with Local chosen and the Select folder button
  1. Set the mode next to the send button to Manual.

    Manual makes Claude ask before it edits a file (desktop docs).

The interview prompt

The interview prompt
Interview me so you can write short context files about my business. Do not write any file until I have said yes to your summary. HOW TO INTERVIEW ME 1. Ask 3 to 5 basic questions first, as clickable choices. In Claude Code, use the AskUserQuestion tool so I can click my answers. If you can't, give lettered options (A, B, C) and I will type a letter. Always include "Other". 2. Then ask numbered follow-ups, up to 3 per message, all on one topic. Where you can guess, offer your guess as an option so I can just confirm. 3. Start each message with where we are, for example "Topic 2 of 5". The five topics are the five core files, in order. The basic questions are Topic 0. Questions about extra files start with "Extras". 4. Do not move on until you are completely clear. If I'm vague, ask for a real example, or something I actually wrote or received, word for word. 5. Never invent. If I don't know, mark it (check) and move on. If two of my answers about timing or numbers don't fit together, ask me which is right before you write either into a file. 6. At the end of each topic, play back that topic's key facts in 3 to 5 bullets, with every number and timeline in my words, and wait for my yes before the next topic. 7. When you think you are clear, stop and play back: what you understood (short bullets), what is still unclear, and which files you will write. Ask "Is this right? What is missing?" 8. If I correct you, fix it and play it back again. Do nothing until I say yes. 9. After 20 questions, pause. Say what is still unclear, ask whether to keep going, and wait for my answer. 10. If I say "enough, write it", stop asking. Show me a one-screen summary with the gaps marked (check), and write the files once I say yes. BASIC QUESTIONS (they also decide the extra files) - What do I mainly sell? Physical products, services or projects, subscriptions or courses, a mix, other. - Who buys? Everyday consumers, other businesses, both. - Who works in the business? Just me, me plus a few people, a bigger team. - How do customers deal with me? Online only, at my place, I go to them, a mix. - Could one wrong sentence put me at risk (health, legal, money, children, food, personal data)? Yes, maybe, no. CORE FILES (always write these five) 1) you.md: my role, how I make decisions, how I like answers. 2) business.md: what I sell, to whom, how I deliver it. 3) customers.md: who they are, the words they use, what makes them say no. Ask me to paste one sentence a customer wrote to me, word for word. 4) strategy.md: this quarter's goals and what I'm saying no to. 5) brand.md: my voice, words I use, and a "Words I never use" list. Fill that list with the words that make text sound AI-written, plus any I name. Ask me to paste one or two real examples of my writing, such as an email or a post. EXTRAS (at most 4, only if my answers call for them. Tell me why for each) - compliance.md: one wrong sentence could put me at risk, or I mention claims, disclaimers or private data. Write only rules I told you. Put your own suggestions under a separate heading "Ideas to check", never as rules. - products.md: I sell physical products or a mix, or I have a menu or catalogue. - offers.md: I sell services, subscriptions or a mix, or I have packages, tiers or quotes. - faq.md: customers ask the same questions again and again. - process.md: the work has 3 or more steps after a customer says yes. - team.md: I don't work alone. - tools.md: I use 3 or more tools. - places.md: customers don't deal with me online only. If more than 4 fit, pick in this order: compliance, offers or products, faq, process, team, tools, places. List the rest as "later". If something important fits nowhere, you may use one of the 4 for a custom file named after the topic. WRITING THE FILES After I say yes, save the files in a folder called context. Create the folder if it does not exist. - Plain English, bullet points, under 200 words each. In brand.md, keep my writing examples word for word on top of that. - Only use what I told you. Do not invent anything. - Mark anything you are unsure of with (check). Finally, create CLAUDE.md in this folder. Put my top three rules at the top: 1) use my customers' words, and never a word from my "Words I never use" list, 2) never invent a fact, price or client, and write (check) if unsure, 3) ask me before anything is sent, posted or published. Below the rules, add one plain line per file, like @context/you.md, for every file you wrote. Do not put these lines in backticks, quotes or a code block. Show me CLAUDE.md when you are done.

DiagramHow the interview works

1Claude asksClick a choice, then follow-ups
2You answerShort is fine
3Claude plays it backWhat it understood
4You confirm or correctNothing is written yet
You say yes, files savedOr say enough, write it
1Claude asksClick a choice, then follow-ups
2You answerShort is fine
Until it’s clear
4You confirm or correctNothing is written yet
3Claude plays it backWhat it understood
You say yes, files savedOr say enough, write it
  1. Claude asks basic questions you can click, then numbered follow-ups.
  2. You answer. Short is fine. This repeats until Claude is clear.
  3. Claude plays back what it understood.
  4. You confirm or correct it. Nothing is written yet.
  5. Only after you say yes are your files saved. You can also say: enough, write it.
Fig 3.2How the interview works
  1. Paste the prompt and send it.

    You should see a few basic questions with answer choices.

  2. Click or type your answers.

Fig 3.3Illustration of the first basic question arriving with answer choices
  1. Answer the numbered follow-ups in your own words. Short answers are fine.

  2. Paste a customer's sentence, and one or two emails or posts you wrote, when Claude asks.

  1. Read the summary Claude plays back.

    You should see what it understood, what is unclear, and the files it will write.

  2. Correct anything wrong, then type yes.

    Claude writes nothing before your yes.

Short on time? Type "enough, write it". Claude shows what it has, with the gaps marked (check).

05 / 08

Test it in a new session

  1. Close the interview session.

  2. Start a new session in the Code tab.

  3. Choose Local, then Select folder, and pick the same folder.

  4. Paste the test task below and send it. Give Claude nothing else. No notes, no attachments.

The test task
Write a short post to my customers about what we're working on this quarter.
76 characters

DiagramWhat the test tells you

1The test requestA short post to your customers about this quarter
No other info
2Claude writes the postUsing only your five files
3Two checks
Sounds like you?Uses your customers’ words?
Both yes
Your files work
Either no
Fix the thinnest filethen test again
  1. Ask Claude for a short post to your customers about this quarter, with no other info.
  2. Claude writes it using only your five files.
  3. Check two things: does it sound like you, and does it use your customers' words.
  4. Both yes: your files work. Either no: fix the thinnest file and test again.
Fig 5.1What the test tells you

Judge the post with this checklist. Pass means every box ticks.

Do this now0 / 5 done
Fig 5.2Illustration of the test task and a short post from a new session

If a box stays empty, fix the file behind it.

What went wrongFix this
Sounds genericbrand.md:addtwomorerealwritingsamples
Wrong customer wordscustomers.md:pasteexactphrasescustomerswrote
Wrong goalstrategy.md:rewritethisquarter'sgoals(redo it each quarter)
A banned word slipped inbrand.md:additto"WordsIneveruse"
Invented detailsTell Claude which line is wrong and what is true. Ask it to fix the file
Claude knows nothing about your businessCheck the @ lines in CLAUDE.md: each on its own line, no backticks or quotes. Start a new session and test again

06 / 08

No Claude Code: use a Claude Project

Claude Code is my pick. No paid plan? Use a Claude Project. Projects work on Free too, up to five of them. A Project has no CLAUDE.md, so your three rules go in the project instructions and you upload every file.

  1. Open a normal chat at claude.ai and paste the interview prompt from "The interview prompt".

  2. Paste the extra line below at the end of the prompt, then send.

Extra line for a chat
You cannot save files or create CLAUDE.md in this chat, so skip that part. After I say yes, show me each file as its own text block, with the file name above it. Then show my three rules as one more text block called Project instructions, ending with the line: Read the project files before you answer. Do not put @ lines in the Project instructions, and do not mention a context folder or CLAUDE.md. I will upload the files to a Claude Project instead.
453 characters
  1. Answer the questions.

    You should get a text block for each file, plus one for the project instructions.

  2. Open Notepad (Windows) or TextEdit (Mac: Format, then Make Plain Text).

  3. Paste the first file block, then click Save.

  4. Name it you.md. In Notepad, set Save as type to All files first. On a Mac, if TextEdit asks, choose Use .md.

  5. Repeat for each other file block, using its file name.

  6. Go to claude.ai/projects and click + New Project (Anthropic help).

  7. Click Set project instructions and paste the project instructions block.

  8. Click + and upload every file.

Fig 6.1Illustration of a Claude Project with instructions set and your files uploaded

Open a new chat inside the project and run the test task from "Test it in a new session".

Claude missed one of my rules. Why?

Claude reads your files as context, not as hard rules, so it can miss one. That is why your top three rules sit in CLAUDE.md itself, written out in full. Add the missed rule there (memory docs). For anything that sends or deletes, add a setting outside Claude's files too: see AI guardrails that hold.

Should I run /init?

No. It's made for code projects. Claude writes your CLAUDE.md in this guide, so you don't need it (memory docs).

07 / 08

Bonus: pressure-test a plan with grill-me

A skill is a saved set of instructions Claude follows when you type its name. This one, grill-me, questions a plan or decision one question at a time and gives its own recommended answer to each. Use it before you launch an offer, change how you work, or make a hire. In the Code tab it also saves your decisions to decisions.md in your folder. I adapted it from Matt Pocock's skills (Copyright (c) 2026 Matt Pocock, MIT license).

The grill-me skill
SKILL.md
---
name: grill-me
description: Interview me about a plan or decision, one question at a time, with your recommended answer for each, and save the decisions to decisions.md.
disable-model-invocation: true
---

# Grill me

Adapted from grill-me by Matt Pocock. Copyright (c) 2026 Matt Pocock. MIT License: https://github.com/mattpocock/skills/blob/main/LICENSE

Interview me about the plan or decision I give you until we both understand it fully. Look for gaps, hidden assumptions and choices that depend on each other. Settle them one at a time.

- Ask one question at a time. Wait for my answer before the next one.
- Give your recommended answer with every question, so I can just agree.
- If the files in this folder can answer a question, read them instead of asking me.
- There is no fixed number of questions. Keep going until the plan holds up.

After each answer, add the decision to decisions.md in this folder. Create the file on the first decision, with a one-line header: the topic and today's date. Then add one entry per decision: the question, what we decided, and a short reason. If you cannot save files here, show the log in the chat instead.

When we finish, show me decisions.md and ask if anything needs changing.

In the Code tab:

  1. Copy the file above, paste it into a message, and add: Save this as a skill at .claude/skills/grill-me/SKILL.md in this folder.

  2. Click Accept when Claude shows the new file.

  3. Start a new session in the same folder. A new skill may not show up until then.

  4. Type /grill-me, then describe your plan.

    You should see Claude ask one question, with its recommended answer.

In a normal chat: paste the file above, then your plan, and say: Follow these instructions on my plan. Claude shows the decisions log in the chat instead of saving it.

Finish line

What to do next

Open claude.com on your computer and install the app. That is the first step of the 45 to 60 minutes.

Already have the app? Start at "Run the interview".

You reached the end of the guide