← All media

The skill that changes your life isn’t prompting.
It’s building your personal AI OS.

Most people use AI like a chat window. Every new chat starts from zero, and you are still the one copying answers between apps. A personal AI OS flips that: you onboard your agent like a new hire, and it keeps what it learns.

my-os/
  • CLAUDE.md# who I am, how I work
  • context/# brand, offers, ICP
  • .claude/skills/# my SOPs
  • projects/
The whole system is one folder: who you are, what you sell, how you work, and the projects it all applies to.

The problem

Right now, you’re the router

Chat AI answers questions. You still carry every answer between apps by hand: the brief, the chat window, the email tool, the design tool, the ads manager. Copy, paste, switch tab. Repeat.

Every new chat starts from zero, so you re-explain your brand, your offer and your rules. Every single time.

  1. Brief
  2. Chat AI
  3. Email tool
  4. Design
  5. Ads manager

You, the manual routerCopy, paste, switch tab. Repeat.

Five tools, one person doing the routing between them.

The shift

From answers to results

An agent works in a loop: look at the situation, decide the next step, do it, and repeat until the goal is met. What comes back is a finished result, not a draft for you to copy somewhere else.

You stop being the operator and become the approver. You set the goal and check the result.

  1. ObserveLook at the situation
  2. ThinkDecide the next step
  3. ActDo it
Repeat

Finished resultnot a draft to copy

Observe, think, act, repeat. The loop ends when the goal is met.

The framework

Onboard your AI like a new hire

A great employee needs three things on day one. So does your agent.

  • Context is the orientation: a CLAUDE.md file, your brand voice, your ICP.
  • Tools are the equipment: your apps, connected through MCP.
  • Skills are the SOPs: workflows saved as SKILL.md files.
  • OrientationContextCLAUDE.md, brand voice, ICP
  • EquipmentToolsYour apps, connected via MCP
  • SOPsSkillsWorkflows saved as SKILL.md
Orientation, equipment and SOPs. The same three things, for an agent.

01 · Context

Stop re-explaining yourself

Your context lives in plain text files on your computer. Editable, portable, and never hidden in a chat history.

  • CLAUDE.md is loaded every session: who you are and the rules that always apply.
  • context/ holds brand voice, offers and ICP, read when a task needs them.
  • Memory holds your corrections, saved as lessons for next time.

Claude Code reads CLAUDE.md files automatically, so the rules are in place before you type a word.

  • CLAUDE.mdLoaded every sessionwho you are, the rules that always apply
  • context/Brand voice, offers, ICPread when a task needs them
  • memoryCorrections saved as lessonsfor next time

Claude Codereads CLAUDE.md files automatically

Three places the agent reads from, and when it reads them.

02 · Tools

Give it hands

The Model Context Protocol (MCP) is an open standard that connects AI agents to your apps. One plug, many tools.

Now “draft the follow-ups and log them in the CRM” is one request, not five tabs.

Your agent
Model Context Protocol
  • Email
  • Docs
  • Team chat
  • CRM
One protocol between the agent and every app it needs to act in.

03 · Skills

Turn your process into a skill

Only a skill’s short description sits in memory. The full steps load when the task needs them, so you can have dozens without crowding the context.

Build one: do the task once with your agent, say “save this as a skill”, then improve it every run.

The spinealways loadedname: ad-analyst

Use when asked to review ad creatives.

The pagesloaded only when needed
  1. Pull this week’s ads
  2. Score each hook
  3. Compare to winners
  4. Flag what to cut
  5. Write 5 new angles
The spine is always loaded. The pages load only when the task calls for them.

Put it together

Your life, as a folder tree

Global rules at the top. Each brand or project gets its own CLAUDE.md, loaded when you work there. Skills live in one place and work everywhere.

A prompt then names the folder and the skill: @my-brand pulls in that brand’s context, /ad-analyst runs the skill, and the rest is the ask.

  • my-os/
    • CLAUDE.mdRules for everything
    • .claude/Skills live here
    • my-brand/
      • CLAUDE.mdThis brand only
      • marketing/
    • health/Goals and baselines
@my-brand/ad-analyst10 new hooks for next week
  • @ pulls in a folder’s context
  • / runs one of your skills
One tree, one rule file per brand, and a prompt that reaches both.

Start tonight

One folder, one file, one tool, one skill

Start small. It compounds.

  1. Create one folder for your OS
  2. Write your CLAUDE.md
  3. Connect one tool with MCP
  4. Turn one weekly task into a skill
Claude Code docscode.claude.com/docs
Four steps for one evening, and the official setup guide.

AI enablement

Want this built for your whole team?

We set up the context, the tools and the first skills with your team, and leave them running it. Start with a free audit of how your marketing work runs today.

Continue exploring

The agentic content system