Welcome to your Business Brain OS, You.

Skills are pre-built instructions that tell Claude how to handle a specific type of task — in your voice, for your audience, using your context files.

• What Are Skills? — what they are and why they matter
• How to Call a Skill — the three ways to run one
• How Skills Improve — the feedback loop that makes them better over time
• Creating Skills — turning your own frameworks into repeatable workflows
• Improve or Change Skills — editing what's already there to work the way you want

There's one habit that makes the difference between a system that compounds and one that stays flat: running the wrap-up at the end of every session.

This module is short on purpose. One lesson, one habit.

• End Every Session — what the wrap-up does and why it matters

▶

There are three ways to call a skill.

The slash commands and run syntax are shortcuts for when you already know what you want.

The cheatsheet lists all 51 of your skills with a one-line description of what each one does. Keep it open in a separate window when you're starting out, as it's the fastest way to find the right skill for any task.

After every skill run, the system asks if you have any feedback. If you do ("make the emails shorter", "skip the bullet lists", "don't open with a question"), that gets saved to a file called learnings file inside the skill folder. The next time you run that skill, it reads those notes first and applies them before it starts.

You never have to repeat yourself. The system gets better the more you use it.

At the end of every session, running wrap-up also checks whether anything from your conversation is worth saving to your permanent memory files: preferences, decisions, context that matters next time. Two minutes at the end of each session, and nothing gets lost.

▶

If you have any repeatable framework, process, or template you use again and again, you can turn it into a skill. Claude walks you through the whole thing.

How to do it

You don't need to copy your document into the Business Brain OS folder first. Just tell Claude what you want to build and point it to where the file lives — it can reference files from anywhere on your drive. Tell Claude what you want the skill to do, and it handles the rest: it looks at how existing skills are structured, builds the new skill, registers it in your system, and gives you a summary of how it works.

Once it's built, test it a couple of times. Anything that feels off — give Claude the feedback, and it'll update the skill. The more you refine it, the better it gets.

The principle

The install comes with a full skill library, but the most powerful skills are often the ones you build yourself — based on the frameworks and formats that work for your specific business. If you keep doing something the same way every time, that's a skill waiting to be built.

▶

The skills that come with your install are a starting point. They're not a fixed system you have to follow — you can edit any of them, give them feedback, or build new ones from scratch. The idea is that over time, this becomes your system, not ours.

Understanding how a skill works

Every skill has a section at the top called Front Matter — a summary of what the skill does and how it runs. If you're not happy with how a skill is behaving, ask Claude to explain it first: "How does this skill work? Walk me through the workflow." Once you understand the logic, it's much easier to know what to change.

Making changes

Give Claude your feedback on how you want it to work differently — longer, shorter, different format, skip a step, add a step. Claude updates the skill's learnings file with your changes. The next time you run it, those changes are already baked in.

You don't need to go into the files yourself. Do it through the chat.

The one thing to do before you close Claude every time.

Run this every time before you close Claude. It takes about two minutes and it's what makes the system compound over time.

Type at the end of every session:
/wrap-up

What it saves

The wrap-up skill writes three things:

memory/sessions/[date].md — today's session log. What you worked on, what decisions were made, what was produced.

memory/MEMORY.md — the persistent facts index. Key decisions, preferences, and context Claude should remember across all future sessions.

context/tomorrow.md — your open threads list. Anything left unfinished, any decisions still pending, any tasks carried forward.

What happens without it

Claude's built-in memory doesn't persist between sessions. Without wrap-up, the next session starts cold — no memory of what you decided, no open threads, no captured feedback. The system loses what it learned.

With wrap-up, every session builds on the last. This is the habit that makes the whole thing work.

The skills built specifically for how you work. Start with these.

Turn one recording into a full week of content — Facebook, LinkedIn, Instagram, and email.

This is your primary content workflow. You record a voice note or video — talking about something you're thinking about, a client situation, a pattern you've noticed — and Claude turns it into a full batch of platform-ready posts.

The whole process takes about five minutes of your time. Claude does the rest.

What you get from one recording

• 2 Facebook posts (different angles and frameworks)
• 1 short Facebook post + first comment (for engagement)
• 2 LinkedIn posts
• 1 Instagram caption
• 1 Instagram carousel (slide copy)
• 1 nurture email with subject line options

Everything lands in Airtable as a draft for you to review. Nothing gets posted without your sign-off.

Save your audio or video file to this folder in Dropbox:

Folder:
brand-context/Videos and Audios to repurpose/

Any format works — .m4a, .mp3, .mp4, .mov. Name it something recognisable, like Client questions.m4a or Monday voice note.m4a. You don't need to tidy it up.

If you already have a written transcript or an .srt subtitle file, you can drop that in the same folder instead — Claude can read those directly and skip the transcription step.

Open a Claude Code session and say:

Type:
Transcribe [filename] — it's in brand-context/Videos and Audios to repurpose/

Claude will run the transcription tool and save a .md file in the same folder. The file will be named with the date and topic, like 2026-08-27-energetic-triggers.md.

Once it's saved, Claude will tell you it's done. You can read it back to check, but you don't need to — it goes straight into the next step.

If you already dropped in a transcript or SRT file, skip this step entirely.

Once the transcript file exists, say:

Type:
Repurpose this voice note — [brief description of the topic]

For example: "Repurpose this voice note — it's about how people get energetically triggered by others who are spiritually open."

The description helps Claude pick the right angles and offer connection. Keep it to one sentence.

What Claude does next

• Reads the transcript and extracts the core insight and angles
• Writes each piece using a different framework and angle — no repetition
• Runs everything through the humaniser to remove AI tells
• Saves files to projects/social-posts/[date]_[topic]/
• Saves all 7 pieces to Airtable as You to check

Claude will ask you one question at most — usually about the CTA if it's not obvious from the recording. Otherwise it runs through without stopping.

When the skill finishes, your content is in Airtable. Open the You to check view and you'll see the new posts listed.

Airtable:
your content base → SM Content → You to check

Click into each record to read the post. If you're happy with it, move it to Finalised. If you want changes, drop a note in the record or come back to Claude and say what needs adjusting.

You don't need to review everything at once. The drafts sit there until you're ready.

Where all your content drafts live between being written and being published.

Your Airtable base is called your content base. The main table you'll work in is SM Content.

The three views

• You to check — drafts that Claude has written and saved. These are ready for your review.
• You's feedback — posts you've flagged for rework. Add a note in the record and come back to Claude to fix them.
• Finalised — approved posts ready to schedule or publish.

You move a post between views by changing its Status field. That's all there is to it.

Other tables

• Videos and Audios — a record of source recordings and what's been repurposed from them
• Freebies — lead magnet tracking
• Testimonials & Case Studies — client results and quotes

When new content appears in You to check, open each record and read it through.

If you're happy with it

Change the Status to Finalised. It moves out of You to check and into the Finalised view.

If something needs changing

Change the Status to You's feedback and add a note in the record — what's off, what direction you want instead. Then come back to Claude and say:

Example:
"The Facebook Post 1 from the [batch name] batch needs reworking — the hook is too abstract. Can you try a more personal story angle instead?"

Claude will rewrite it and save the updated version back to the same record.

What to look for when reviewing

• Does it sound like you?
• Is the opening strong enough to stop the scroll?
• Is the offer or CTA the right one for where you are right now?

Once you're happy with a post, change its Status to Finalised. It moves into the Finalised view, where you can schedule or copy it across to your platform.

The Date and Published fields are there if you want to track when something went out — these are optional but useful if you want to look back at what's been posted.

Scheduling

Airtable doesn't post to social platforms directly. You'll copy the content into Meta Business Suite, LinkedIn, or your scheduling tool of choice. The Airtable record is your review and tracking layer — not a publishing tool.

Work through one recording's batch at a time. Review, approve, schedule — then move on to the next. It's faster than dipping in and out.

Write the copy first, then ask Claude to build the HTML. The skill reads your brand guidelines automatically so every page matches your design system.

This is a two-step workflow. The copy and the design are separate jobs — getting them in the right order means you're never retrofitting words into a layout, or redesigning around copy that's going to change.

The two steps

1. Write the copy — use a writer skill to draft it, review and approve it
2. Build the HTML — run web-page-builder, which reads your brand guidelines and existing pages to produce consistent HTML ready for Divi

What web-page-builder does

• Reads your brand guidelines (colours, fonts, CSS variables, usage rules)
• Studies the existing pages to match the established patterns
• Plans the section structure and waits for your approval before building
• Produces a single self-contained HTML file saved to brand-context/Website/pages/

Use the right writer skill for the page type:

• Service page (individual services) → service-page-writer
• Sales / programme page (signature programme, group offer) → sales-page-writer
• Short page (opt-in, thank you) → write it yourself or ask Claude to draft it directly

Say:
Run service-page-writer for my [offer name] page

The skill will ask you questions about the offer, the audience, and the keyword you want to target. Answer them one at a time. It will produce a full copy draft.

Before moving to Step 2

Read through the copy. Make any changes — add specifics, adjust the tone, swap out any lines that don't sound like you. Once you're happy with it, say: "The copy is approved — build the HTML."

With the copy approved, say:

Say:
Build the HTML for this page using web-page-builder

The skill will:

1. Read your brand guidelines and study the existing pages
2. Plan the section layout and show you the structure — hero, content sections, CTA
3. Wait for you to confirm the plan before building
4. Produce the full HTML and save it to brand-context/Website/pages/[Page Name]/

Reviewing the output

Open the saved HTML file in your browser to preview it. You can ask Claude to adjust anything — spacing, section order, colours, copy tweaks — before it goes into WordPress.

Once you're happy with the preview:

1. Open the HTML file and copy the entire contents
2. In WordPress, open the page in Divi Builder
3. Add a full-width section → insert a Code module
4. Paste the HTML into the code module and save
5. Preview the page in WordPress to check it renders correctly

Divi's own header and footer wrap the page automatically — the HTML Claude produces is just the page body content, so there's no duplication.

If something looks off

Come back to Claude and describe what's wrong: "The hero text is too small", "The CTA button isn't showing", "The spacing between sections is too tight." Claude will fix the HTML and you re-paste it.

Two settings that turn every Zoom call into usable material for Claude.

1. Switch to local recording

Zoom defaults to saving recordings to the cloud, but cloud recordings don't include a VTT transcript file. To get the transcript, you need to switch to local recording and enable the caption option.

In Zoom: go to Settings → Recording. Under Other settings, tick Save closed caption as a VTT file. Then change the save location from cloud to local, and set the folder to your Dropbox so recordings are easy to find.

At the end of each recorded call, your Dropbox folder will contain both the video and a .vtt transcript file.

Please be aware these video files can be extremely large — once you have the transcript, you may want to delete the original video file to free up space.

2. Move the transcript to your Business Brain OS folder

Copy the .vtt file across to your Business Brain OS Dropbox folder. A good place for it is source-material/calls/ so your call transcripts stay in one place and are easy to find.

You can do this yourself by dragging the file across in Finder or File Explorer, or you can ask Claude to move it for you: "Move the VTT file from [location] into my source-material/calls folder."

Once it's there, drop it into Claude and say what you want to do with it: content, session notes, a summary, action items. It can work from that directly, without you needing to retype anything.

▶

Before you can use Business Brain OS, you need to get the files onto your computer. This module walks you through getting your copy via Dropbox — and how to pick up new skills when they're released.

• Set Up Dropbox — make sure it's installed and syncing
• Accept Your Shared Folder — the master copy of the system
• Make Your Working Copy — where you'll actually work
• Getting New Skills — how to add updates to your copy

The video above shows you how the whole process works: accepting the shared Dropbox folder, making your own copy of it, and where to save it on your computer. The following lessons take you through each step.

Business Brain OS is delivered via Dropbox. If you don't already have it installed on your computer, do that first — it needs to be the desktop app, not just the website, so the files actually sync to your machine.

What to do

1. Go to dropbox.com/install and download the desktop app
2. Install it and sign in (or create a free account if you don't have one)
3. Make sure it's running — you should see the Dropbox icon in your taskbar or menu bar

If you already have Dropbox installed and syncing, you're good to move on.

You'll receive an email from Dropbox inviting you to a shared folder called Business Brain OS: Client Install. The invite comes from me; the email will show as being from TwoTen Solutions.

This is the master copy — it contains all the skills and shared resources. You have view access only, so nothing you do can affect it.

What to do

1. Open the invite email from Dropbox
2. Click Accept invite
3. The folder will appear in your Dropbox — check it's there before moving on

If you haven't received the invite, check your spam folder or let Cathy know.

The shared folder you received an invite to is the master, so you won't be able to make any changes to it.

Instead, make a duplicate by copy/pasting your own copy.

What to do

1. Open Dropbox on your computer and find the Business Brain OS: Client Install folder
2. Right-click it and choose Copy
3. Paste it somewhere sensible — your main Dropbox folder or Documents works well
4. Rename it to something clear, like Business Brain OS or My AI OS

This copy is yours. You'll customise it, add your context files to it, and work from it every day.

New skills are added to the master folder regularly. When one is released, you'll get a message letting you know — then it's a simple copy across to your working folder.

When a new skill is available

1. Open the Business Brain OS: Client Install shared folder in Dropbox
2. Find the new skill folder inside .claude/skills/
3. Copy that folder
4. Paste it into the same location in your working copy

Your Business Brain OS is built from a specific set of folders, each with a clear job. This module walks through each one in turn.

• Overview — the full layout at a glance
• Context Folder — who you are and how Claude behaves
• Memory Folder — what Claude remembers between sessions
• Brand Context Folder — your voice, audience language, and visual brand
• Offers Folder — detail files for each of your offers
• Source Folder — raw material you bring in (transcripts, notes)
• The .claude Folder — skills, commands, and hooks
• CLAUDE.md — the instruction file Claude reads every session

Almost everything in the Business Brain OS is stored as a markdown file — plain text with a .md extension. This module covers what that means in practice and how to work with those files confidently.

• What is Markdown? — why it's used and what it looks like
• Opening and Editing Files — how to read and update your context files
• Getting Documents In — how to bring external documents into your system

▶

This is one of the most important files in the whole system. Every time you start a conversation with Claude, this is the first file it reads.

Think of it as the map, or a breadcrumb trail.

It tells Claude what's in your system and where everything lives.

From there, depending on what you've asked it to do, it follows the trail. Going to the next relevant file, reading the context it needs, and so on. This is how the Business Brain OS always knows where to look.

When you first install the system, CLAUDE.md is already set up with everything it needs.

As you fill in your context files and work with Claude over time, it will update this file automatically behind the scenes. You don't need to open it or manage it directly.

Monthly Check-in

The one thing worth doing is a monthly check-in.

Once a month or so, ask Claude to read your CLAUDE.md and check if anything needs updating, trimming, or moving elsewhere.

The file should be an overview of your system, not a document that contains everything. If it starts getting too long, Claude can tidy it up.

Just ask it to take a look and go back and forth with it until everything looks right.

▶

The dot at the start of the name means this is a hidden folder on your computer. If you can't see it, you'll need to update your Windows settings to show hidden files.

You won't ever really need to go into this folder, but here's what's in it:

Skills

This is your library of 50+ pre-built workflows.

Each one handles a specific task, for example writing a Facebook post, running a keyword search, or drafting an email sequence.

When you run a skill, Claude goes to this folder to read the instructions, loads your context files, and does the work.

You can go in depth into the Skills in your Business Brain in this module. There you'll find a cheatsheet with all your skills, plus training on how to create your own.

Commands

These are the shortcuts that tell Claude to run a skill.

You type a forward slash followed by the skill name (e.g. /wrap-up) and it pulls it up. Nothing you need to touch in here directly, just good to know where they live.

Hooks

Behind-the-scenes automation that Claude uses. Nothing you need to do with these.

▶

The brand context folder is where we build out a picture of your business and your brand. When you first install the system, these are mostly empty templates. They get filled in as we work through the setup process together.

Here's what's inside:

About Me: where you save existing material about yourself or your business. There's a readme with ideas for what to include, and you'll be guided through finding what you need.

Audience Language: this is where you collect language from your audience, pulled from call transcripts, old content, and similar material. When the system writes for you, it draws on this folder to make sure it sounds like it's speaking to the right people.

Brand Stories: your origin story, personal stories, business stories. You'll be guided through building this out, and there are prompts to help if you're starting from scratch.

Testimonials: client testimonials go here.

Writing Samples: this one is important. You need to find samples of your own writing, ideally from before you were using AI. If you don't have anything ready, you'll be guided through how to capture your voice using audio notes. For AI to write in a way that genuinely sounds like you, it needs real examples of how you write.

The templates in this folder are filled in by Claude as we work through the brand context setup together. For now, this is just an overview. You don't need to do anything yet.

In this module, I take you through the steps of adding in your context and configuring the Business Brain OS to your business.

▶

When you first install the system, the context folder contains placeholder files. As you work through the setup, these get filled in. Here's what each one does:

ceo-north-star.md: your big picture: what you're building towards, your goals, your priorities. Once it's filled out, Claude checks in with it to make sure decisions stay aligned with what you said you're working towards. You can update it any time.

learnings.md: where Claude saves feedback you give about how the skills are working. You never need to read it. It's for Claude: it reads this when it's working to make sure it keeps improving.

parked.md: ideas, decisions, and projects you're not ready to act on yet. Instead of losing them or going down a rabbit hole, you ask Claude to park them here. They sit in the background until you're ready to pick them up.

revenue-tracker.md: if you want Claude to help you track income, this is where that lives. Keep it updated and Claude can reference it in any revenue-related conversation.

rhythm.md: your standing daily or weekly tasks. If there are things you want to do every day or every week, they go here and Claude pulls them in when relevant.

SOUL.md: Claude's personality and behaviour rules. This comes pre-configured, but as you work with the system, Claude checks in to make sure it's behaving the way you want. If something's off, you can ask it to update this file.

tomorrow.md: your to-do list. As long as you run wrap-up at the end of every session, Claude keeps this updated automatically: capturing what's outstanding, what's in progress, and any breadcrumbs it needs to pick up where you left off. One of the most useful files in the system.

USER.md: about you, your business, and your brand. Filled out during setup, and updated any time things change.

weekly-focus.md: optional. If you want Claude to help you stay focused on 2–3 priorities each week, this is where that's set. Claude can look at your tomorrow.md, open threads, and memory to help you identify and stick to your weekly focus.

▶

The memory folder is a core part of the system. When you first install it, it's empty. Over time, it becomes the record of everything you've worked on.

There are two parts to it:

MEMORY.md: the index file. Claude reads and writes to this to keep an overview of what's in the memory. You never need to open it.

sessions/: a subfolder with one file per day. Every conversation you have gets saved here. If you have five conversations in a day, they'll be saved as session one, session two, and so on.

You don't need to read any of these files. They're for Claude. At the start of a new session, when you say something like "where did we get to on X project?", Claude goes into this folder, reads through the sessions, checks your tomorrow.md, and pulls out anything relevant.

The other thing it's useful for is if something gets lost. For example, if your tomorrow.md ever gets wiped or goes wrong, you can ask Claude to go back through the memory sessions and pull out anything that was still outstanding. It can rebuild your to-do list from the session notes.

The memory system grows over time. The more you use it, the more context Claude has about you and your business. This is how the system gets smarter the longer you use it.

An important habit that makes all of this work is to run /wrap-up at the end of every session. That's what saves everything into the memory in the first place. See the lesson on the /wrap-up skill.

▶

This is where your offers live. Over time, the goal is to have all your offers in here as fully written-out sales pages, so the system has all the context and detail it needs when writing for you.

There are a few ways to fill it out. If you have existing sales pages, we can create copies of them here. If you have ideas that aren't fully developed yet, there's an offer template to help you flesh them out, so you have something for the system to work from even before you have a finished sales page.

You can also use it to test new ideas and get them out there before you need a full sales page.

We go through this in more detail when we're building out your system together.

▶

This is where you upload material about your business: documents, presentations, PDFs, Google Docs, anything you want to bring into the system. What goes in here will depend on what you've got and what you want Claude to be able to draw on.

When filling this folder out, Word documents and Google Docs are best converted into markdown files first.

Click here for the module on what markdown is and how to do it.

We do this because markdown files are easier for AI to read, more efficient, and take up less space.

The source folder is one of the most powerful parts of the system. You can give Claude everything you have and ask it to go through it and pull out what's useful: refining your offers, creating programme curriculums, writing sales pages, generating new ideas. Think of it as giving your Business Brain the full picture of your business to work from.

▶

Markdown is a plain text file — you can tell because it ends in .md.

Most of the files inside your Business Brain OS are markdown files.

They're lightweight, easy for Claude to read, and best practice for working with an AI system.

Here's what the formatting looks like in practice:

• A # at the start of a line = Heading 1
• ## = Heading 2
• Text wrapped in *asterisks* = italic

Claude reads markdown natively.

And it goes both ways — if you paste the content into a Google Doc and choose "Paste from Markdown", it formats correctly as headings, italics, and so on.

Google Docs and markdown understand each other.

As you build out your Business Brain OS, get into the habit of keeping documents in markdown format wherever you can. It keeps everything lightweight and easy for Claude to work with.

▶

There are a couple of ways to open and edit your markdown files.

You can open them directly from your folder, they'll open in Notepad, and you can edit the text there. But it's not recommended. Notepad just shows you the raw code, not the formatted version.

The best way to view and edit your markdown files is through Claude Code itself.

Once you've started a chat, go to the file panel on the right. This shows you a mirror of your Business Brain OS folder, the same files and folders you'd see in your file explorer.

Find the .md file you want, click it, and it opens in the panel on the right with the formatting applied — headings, bullets, all of it. Much easier to read.

You can also ask Claude to open a specific file for you: "Can you show me my north star file?" Claude will give you a clickable link, and when you click it, the file opens in the right-hand panel with full formatting.

Either way, reading and editing from inside Claude Code is the right habit to build.

You can see what's in the file, ask Claude to make changes, and watch the edits happen, all in one place.

▶

You can bring existing documents into your system as markdown files, or create new ones from scratch. Here's how to do both.

Converting a Google Doc

Open the Google Doc, go to File → Download → Markdown (.md). It saves to your Downloads folder. Then move it into the right folder in your Business Brain OS — source/ for reference material, offers/ for offer docs, brand-context/ for anything about your brand or audience.

Converting a Word document

Drop the Word file into the relevant folder, then ask Claude: "I've added a Word document at [path] — can you convert it to a markdown file?" Claude creates the .md version automatically. Once it's done, you can keep the original Word file or delete it — the markdown version is what Claude works from.

Creating a new file

You don't need to create markdown files manually very often — Claude creates them for you when it saves memory, context, or output files. But if you need one, just ask: "Create a new file at [path/filename.md] with the following content..." and Claude will write it.

The .md extension is what tells Claude (and your computer) it's a markdown file. That's the only thing you need to get right.

Before you start configuring your system, you need to be comfortable in the tool that runs it. This module walks you through getting Claude Code installed, understanding the interface, and knowing what it can and can't do.

• Install and Open — get Claude Code running and open your folder
• The Interface — the chat panel, the file sidebar, and the modes
• Permissions — what Claude is and isn't allowed to do
• Connecting External Tools — how Airtable and other MCPs connect
• Your Memory System — how Claude remembers things between sessions

▶

You might already be using Claude in your browser, which is the online version at claude.ai, with your projects and chats listed on the left.

The Business Brain OS runs specifically through the Claude desktop app, not the browser version. So the first step is to download it.

Go to claude.com/download and download the version for your computer, Windows or Mac. Once it's installed, you launch Claude as an app rather than opening a browser tab.

The desktop app has the same functionality, but it keeps everything in one place. You're not distracted by the various options in the browser version — you just open the app, go straight to the Code tab, and work from there.

From now on, whenever you're working on your Business Brain OS, open the Claude desktop app, not the browser.

▶

When you open the Claude desktop app, the chat panel is in the middle. This is where you interact with Claude through your system. It works the same as any chat you're used to in Claude or ChatGPT.

The important step when you start a new chat is to connect it to your Business Brain OS folder.

At the bottom of the chat panel, you'll see an option to add a folder. Click it and select the folder where your Business Brain OS is installed, whatever you've named it on your computer.

Once you've connected the folder, everything in that conversation is working with the contents of that folder. Claude has the full context of everything inside it: your brand voice, your offers, your context files, all of it.

You do this once per new chat. From that point on, Claude knows where it is and what it's working with.

▶

The mode selector sits at the bottom of the chat panel. There are four options — here's what they mean and which one to use.

Auto (use this one)

Claude acts on your instructions without asking permission for every step. It still respects the hard limits built into the system — it can't delete files, log into anything, or do anything outside its configured permissions. But within those limits, it just gets on with it. Use Auto for everything.

Plan

Before doing anything, Claude writes out a step-by-step plan and shows it to you. You can read it, revise it, ask questions, and approve it before anything actually happens. Good for big or complicated jobs where you want to see the approach first. It also uses fewer tokens at the planning stage, so it's worth using for large multi-step tasks.

Manual

Claude asks for permission at every individual step. This slows everything down significantly. You can use it if you're curious to see exactly what Claude is doing under the hood — but it's not practical for day-to-day use.

Bypass Permissions

Don't use this. It removes the safety guardrails built into your system and lets Claude override the configured limits. There's no reason to ever switch to this mode.

▶

The context bar shows how much of the current chat has been used up. You'll find it when you click the icon at the top of the chat panel.

Every time you ask Claude to do something, it reads back through the entire conversation from the top before responding.

The longer the chat, the more it has to read, and the more tokens it uses each time. It also becomes more likely to start making mistakes, because it's holding more and more in memory at once.

The limit is 200,000 tokens. When you hit that, Claude will start compacting the chat automatically, keeping what it thinks is relevant and discarding the rest.

The problem is you don't want Claude deciding what's important. You want to be in control of that.

A good rule of thumb: when the context bar gets to around 50-70%, start wrapping up that chat.

The system comes with a built-in skill for this. Type /wrap-up and Claude will go through the conversation, pull out anything relevant, save it to your memory files, and flag anything outstanding.

Once that's done, you can start a fresh chat with confidence, knowing nothing useful has been lost.

▶

Every chat you have with Claude gets saved in the left sidebar, most recent at the top. You can rename chats and pin the ones you're still working on.

Groups

You can organise chats into groups, but be aware that Claude periodically asks you to log out and back in, and when that happens, groups reset and everything goes back into one flat list. It's not worth relying on groups for organisation.

Pinning and archiving

Pin any chat you haven't fully wrapped up yet. Once you've run /wrap-up and confirmed nothing's been lost, archive it. Treat archived chats as gone — you may not be able to retrieve them. That's fine, because the memory system has captured everything worth keeping. You don't need to keep every conversation in the sidebar.

Artifacts and Routines

Artifacts are visual outputs Claude generates — HTML pages, diagrams, that kind of thing. Use them as a scratchpad. Once you're happy with something, get it saved properly as a file back into your Business Brain OS folder so it's in the system.

Routines let you set Claude up to run tasks on a schedule — daily content, folder tidying, whatever you need. They currently only run when your laptop is open, not in the background, so bear that in mind.

▶

The $20/month Claude Pro plan gives you a usage allowance split across two levels: a weekly total and a 5-hour session limit. Most day-to-day marketing work stays well within both.

Weekly allowance

You're given a set number of tokens per week, which resets on Saturday. Keep an eye on it if you're doing heavy work — building systems, processing large files, or running multiple complex sessions in a day.

5-hour session limit

Within any 5-hour window, there's a cap on how many tokens you can use. If you hit it, you have two options: wait for it to reset, or add usage credits to your account which top you up automatically when you hit the limit.

If you hit your limit

Use the time for work that doesn't need Claude: recording videos, reviewing content, admin tasks. Most users only bump into the limit occasionally and during heavier-than-usual sessions.

Claude Code is not running in the background. It doesn't do anything unless you open a session and give it an instruction. When you close the app, nothing runs.

The Business Brain OS comes pre-configured with a permissions file that controls exactly what Claude is and isn't allowed to do.

What it's allowed to do

• Read, edit, and write files inside your Business Brain OS folder
• Run specific scripts that power the skills
• Basic file navigation: listing folders, checking where things are

What it's blocked from doing

• Installing software — blocked by default
• Deleting files or folders permanently — blocked by default
• Reading your credentials or .env files

Even if Claude misunderstood an instruction and tried to delete a folder, the system would stop it.

The mode selector controls how much Claude checks in with you before acting — not what it's capable of doing. The guardrails above apply regardless of which mode you're in.

Left to itself, Claude can only work with files on your computer. It can't see your email, your Google Drive, your Airtable, or any other external tool — unless you connect it.

That's what MCP connections do. MCP stands for Model Context Protocol — the standard that lets Claude plug into external apps. Each connection is something you set up deliberately, and it only gives Claude access to that specific tool.

What becomes possible with MCP connections

• Airtable — Claude can read your content queue, save posts, and update records directly
• Google Drive — Claude can read documents from a link, without you copying and pasting
• WordPress — Claude can publish blog posts as drafts straight from a session

If a connection isn't set up, Claude simply can't access that tool. And the connections only work within the scope of what you've configured.

Airtable: your access token

Airtable uses a Personal Access Token to allow Claude to read and write to your content system. You generate it once in Airtable, then share it with Cathy so she can connect it to your system.

How to generate your token

• Go to airtable.com/create/tokens (or: sign in → click your avatar top right → Developer hub → Personal access tokens)
• Click Create new token
• Give it a name (e.g. "Claude Code")
• Set the scopes: data.records:read, data.records:write, schema.bases:read
• Under Access, choose your workspace so the token has access to your bases
• Click Create token
• Copy the token immediately — Airtable only shows the full token once, at this step. After that it's hidden for security.

Once you have the token, don't paste it into the chat — chat messages can be logged or visible in session history. Instead, open Claude and say: "I have my Airtable Personal Access Token — where should I save it securely so you can use it?" Claude will tell you exactly where to put it on your computer so it stays private.

▶

The Initial Install is where you run the setup skills that build your Business Brain's core files. You do this once when you first get started. Everything else builds on top of what this creates.

Before you begin, spend some time gathering existing material into your folders — a rough first pass is enough. The system works with what it's given and gets better as you add more over time.

The setup skills

Run these in order from the chat panel. Type the skill name and Claude picks it up automatically.

setup-user-profile

Builds your user profile from whatever's already in your brand-context/about-me folder. Anything missing, and it walks you through questions one at a time. The output is USER.md — a file Claude reads at the start of every session so it already knows your business, your offers, and how you like to work.

setup-north-star

Creates your strategy layer: your mission, what you're working toward, your 90-day priorities, and your income target. It writes two files: ceo-north-star.md and revenue-tracker.md. Both are meant to be updated as your business evolves.

setup-brand-voice

Reads your writing samples and brand stories and builds your voice profile — the tone, rhythm, and patterns that make your writing sound like you. Every content skill reads this before writing anything. The more examples you give it, the better it gets. You can run it again any time you add new material.

setup-icp

Builds your ideal client profile and your first audience language file. Copy skills draw on these whenever they're writing anything promotional. You can build separate language files for different offers over time as you gather more material.

setup-language-rules

Creates a list of words and phrases Claude is never allowed to use in your content. It starts with the most common AI writing patterns and asks a few quick questions to personalise it. Any time Claude produces something that jars, say: "Add that to my language rules." That phrase won't appear again.

After the install

Close Claude Code and reopen it. Type: Who am I and what am I working on? Claude should respond with your name, your brand, and your current priorities.

The install is not a one-off event. As you work, the system keeps refining these files based on the feedback you give it. Run /wrap-up at the end of every session — that's what makes it self-learning.

▶

Before you run the setup skills, spend some time gathering existing material and putting it in the right places. You don't need everything — just whatever you already have. A useful starting point: open a new Claude chat and ask it to help you sort through your Downloads, Documents, and Google Drive to surface anything relevant.

Brand Context

The core folder Claude draws from when writing or designing for you. Put in:

• Old bios, LinkedIn profiles, any "about you" writing you've created
• Discovery call transcripts (text only — no need for the video files)
• Testimonials and case study screenshots
• Brand stories
• Writing samples — anything that sounds like you at your best
• Logo files, photos, icons, banners

There's no minimum. Start with what you can find and add to it as you go.

Offers

Everything related to your current and past offers — sales pages, PDFs, course content, templates. Organise by status: live, potential, retired. That way Claude understands what you're actively working on versus what's kept for reference.

Source

Anything you want the system to draw on as raw material — old blog posts, video transcripts, Facebook Lives, lead magnets, training recordings. Think of it as your content library: everything worth keeping, in one place.

Whatever you put in becomes the context your Business Brain works from. Imperfect is fine — keep adding as you go, and don't wait until you feel like you have it all.

Run the setup skills that load your voice, strategy, and audience into Claude. Once done, every session starts with Claude already knowing your business.

• Initial Install — getting the system open and running for the first time
• Filling Out Your Folders — what to put where before you run the setup skills
• Your Strategy Layer — mission, priorities, income target
• Your Brand Voice — how Claude learns to sound like you
• Language Rules — words and phrases Claude must never use
• Map Your Audience — your ideal client profile and audience language
• Your Visual Brand — brand guidelines Claude uses for any design work

Your User Profile

Type run setup-user-profile in the chat panel. It will pull in any material you already uploaded to your brand-context/about-me folder. Anything missing, and it will ask you questions one at a time: your name, your brand, what you sell, who you sell it to, how you like to communicate.

Your North Star

Type run setup-north-star. This skill writes two files: ceo-north-star.md (your mission, offers, and 90-day priorities) and revenue-tracker.md (your income target and current pipeline).

SOUL.md

SOUL.md comes pre-configured in the Business Brain OS. It controls how Claude behaves in your sessions. You don't need to edit it now — over time it will update as you develop preferences. The wrap-up skill proposes updates when it detects repeated patterns of corrections. You approve or reject each one.

Verify it's working

Once you've run both setup skills, close Claude Code completely and open it again. Type: Who am I and what am I working on?

Claude should respond with your name, your brand, and your current priorities.

Setup Brand Voice

Type run setup-brand-voice in the chat panel. This skill reads everything in your writing-samples and brand-stories folders and generates a voice profile automatically — the patterns, rhythm, tone, and things to avoid that make your writing sound like you.

It produces two files: brand-context/voice-profile.md (the voice guide every content skill reads before writing) and brand-context/writing-examples.md (a curated set of gold-standard sentences from your own writing).

Test it

Once the skill has finished, ask Claude to write a short Facebook post on any topic you know well. Read it back. Does it sound like you?

If it's way off, add more examples to brand-context/writing-samples/ and regenerate. You can run setup-brand-voice as many times as you need.

Setup Brand Stories

Run setup-brand-stories after setup-brand-voice. This skill reads everything in your brand-stories and testimonials folders, compiles them into a story bank, and updates your voice profile with real material for copy skills to draw on.

Your voice profile captures how you sound. Language rules add a separate layer: what Claude is explicitly never allowed to write.

Without language rules, Claude defaults to patterns that are technically fine but feel off: em dashes, phrases like "here's the thing", structures like "it's not X, it's Y". These are so common in AI-generated content that they've become dead giveaways.

Run setup-language-rules

Type run setup-language-rules in the chat panel. The skill starts with a curated list of the most common AI writing offenders, asks you four quick questions to personalise it, then saves your file.

Your language rules save to brand-context/language-rules.md. Every content skill loads this file alongside your voice profile before writing anything. The rules are treated as hard constraints, not suggestions.

The ongoing habit

Every time Claude produces a phrase that jars — something that makes you think "I'd never say that" — tell it in the session and then say: "Add that to my language rules."

Claude opens the file, adds the phrase, confirms it's done. That phrase will never appear in your content again.

Over time, this file becomes one of the most valuable parts of your system. The more you refine it, the less editing you do.

Set Up Your ICP

Type run setup-icp. This skill builds two files: your ideal client profile and your first audience language file. These are what every copy skill reads before writing anything promotional.

If you've saved material to your audience-language folder, it picks everything up automatically. If not, it walks you through questions one at a time: who your ideal client is, what they want, how they describe their problem, the exact words they use.

How to keep adding language over time

After every discovery call, testimonial, survey response, or comment — paste the quote directly. Say to Claude: "Add this to my audience language file" and paste what you have. It goes in as-is, verbatim.

The more you add over time, the more accurately the system can write for your specific audience rather than a generic version of them.

Your brand guidelines file is the single source of truth for how everything visual looks — website pages, carousels, presentations, any design Claude builds for you.

Where it lives

Your visual brand guidelines are stored in:

Folder:
brand-context/Visual Brand Guidelines/

The key file is brand-guidelines.md. It contains your full colour palette (with HEX values), your typography system (heading, body, subheading, accent fonts and their Google Fonts fallbacks), CSS variables ready to drop into any build, your logo variants and when to use each one, and usage rules for colour and type.

How it gets used

When you ask Claude to build a page or a visual, it reads brand-guidelines.md first. That means every page starts from your own colour palette, your heading font, and your body copy font — not something generic. You don't describe your brand each time; it's already loaded.

Building a page

The typical workflow is:

1. Write the copy — using service-page-writer, sales-page-writer, or your own draft
2. Say: "Design a page for [offer] using this copy" — Claude reads your brand guidelines and builds the layout using viz-interface-design
3. The output is an HTML file you paste into a Divi code block on your WordPress site

If your brand evolves

Update brand-guidelines.md — change a colour value, swap a font, update a rule. Every future build picks up the change automatically. The HTML version (brand-guidelines.html) is a visual reference you can open in a browser to see everything at a glance.

If you ever need to rebuild it

The guidelines were extracted from your brand PDF (Brand Guide.pdf in the same folder). If you ever need to rebuild the file from scratch — say, after a full rebrand — say to Claude: "Rebuild my brand guidelines from the PDF in brand-context/Visual Brand Guidelines/" and it will extract the colours, fonts, and rules and rewrite the file.

Every time you open Claude Code in your Business Brain OS folder, the first thing it does is read your CLAUDE.md file. From there, it reads the relevant files depending on what you've asked it to do.

Your open threads list

Your open threads list is saved in a file called tomorrow.md that carries forward between sessions. Anything left open at the end of a session gets saved here by the wrap-up skill. When you open a new session, Claude reads this file and picks up where you left off.

The context window

You'll notice a progress bar at the top of the chat panel. This is the context window — the total amount of conversation Claude can hold in memory at once. Around 120K tokens is a good point to either wrap up or use /compact.

/compact

When you're in the middle of something and don't want to stop, type /compact and save to working memory what we're working on. Claude compresses the conversation history and saves a summary so it doesn't lose the thread.

The wrap-up skill

At the end of every session, type /wrap-up. It writes to three files:

• memory/sessions/[date].md — today's session log
• memory/MEMORY.md — the persistent facts index
• context/tomorrow.md — your open threads list

Without running wrap-up, you risk losing all the learnings and context from that session. This is the habit that makes the whole system compound over time.