2.3 Reviewing and Refining

🎥 Video lesson — video not yet migrated (source Skool video id: 5b90f39b59244d5da62352951522c953).

Learning Objective

Learn how to review every file Claude generated, spot common issues, and refine your Business Brain until it accurately represents your business.

Walk Through Each File

Start with your **Global **CLAUDE.md. Read it carefully and ask yourself: does it accurately describe who I am? Does it capture how I want Claude to work with me? Are the references to context files correct and pointing to real files?

Next, open your **Project **CLAUDE.md. Does it describe your business correctly? Are the key commands and workflows accurate? Does it mention the right tools and platforms you actually use?

Then check each context file one by one. Look at team info - are roles and responsibilities right? Look at goals - do these match your actual priorities? Look at your stack and tools - is anything missing or wrong?

Common Issues to Watch For

The most common problem is content that is too generic. If your Business Brain says "We provide solutions to clients" instead of "We build custom AI voice agents for real estate agencies," it needs fixing. Specificity is what makes this system work.

Watch for missing key workflows. If you mentioned a process briefly during the interview, Claude might have skipped it entirely. If something important is missing, you need to add it.

Check for wrong business descriptions. This happens especially if you have multiple businesses or recently pivoted. Claude might have mixed things up or used outdated framing.

Finally, check the length. Your CLAUDE.md should stay under 300 lines. If it is longer, some of that detail belongs in separate context files instead.

How to Tell Claude to Fix Things

You do not need to edit files manually. Just talk to Claude naturally in Claude Code and it edits the files for you.

Tell it things like "Update my agency overview - we focus on AI voice agents and chatbots, not general consulting." Or "Add my Revolut and Stripe integrations to the tools section." Or "The team section is missing my CTO Nick - add him with his role."

You can also ask Claude to reorganize things. For example: "Move the detailed client list from CLAUDE.md to a separate context file." Claude handles all the file editing - you just describe what needs to change.

Tip: Drop Your Existing Business Files In

If you already have a running business, you probably have documents that contain valuable context - SOPs, knowledge base files, onboarding docs, process guides, client briefs, pricing sheets, anything that describes how your business works.

Create a folder inside your business directory called reference/ or docs/ and dump those files in. Then update your Project CLAUDE.md to point to that folder. Something like: "For detailed SOPs and reference documents, see the reference/ folder."

Claude does not need to read all of these files every session. It just needs to know they exist and where to find them. When it needs specific information about a process or a policy, it will go read the relevant file on demand. This is one of the fastest ways to make your Business Brain smarter - you are feeding it years of accumulated business knowledge in one step.

Do not worry about formatting or cleaning up those files first. Claude can read messy documents, PDFs, spreadsheets, and plain text. Just get them into the folder and point to them.

This Is a Living System

Your Business Brain is not a one-time setup. It evolves as your business evolves.

New tool? Update the stack. New process? Add it. Pivoted your business model? Rewrite the overview. Set a monthly reminder to review your CLAUDE.md files and keep them current.

The better your context stays, the better every single interaction with Claude becomes. Think of it as maintaining a relationship - the more up-to-date your partner is on your life, the better the advice they give.

Action Items

  • Read through every file Claude generated - do not skip any
  • Make a list of things that are wrong, missing, or too generic
  • Ask Claude to fix each issue using natural language (no special syntax needed)
  • Verify your CLAUDE.md is under 300 lines - move excess detail to context files
  • If you have existing business docs (SOPs, guides, knowledge bases), drop them into a reference/ folder and point your CLAUDE.md to it
← Previous
Next →