_  / AI BRAIN KIT
Preview · Chapter 1 unlocked

Upgrade your business to AI Level 4.5

Everything from the webinar, in one page that works offline: the nine-chapter build, the starter vault, twenty-two ready-made skills, and the model cheat sheet. Work through it in order, or take just the piece you need today.

Get access
9 chapters22 skills11 agentsstarter vaultmodel cheat sheet
What's in the pack
THE BUILD 9 chapters
The AI Brain Guide
Nine chapters in build order, plus the step that comes before Chapter 1 — download the vault, run the Structure Interview, and work through to a Brain that remembers, maps itself, and runs with your team.
BUILD YOUR OWN 4 templates
Skills, Agents, Council
Four templates to hand to Claude when you want to build your own — the standards doc for writing a new skill, the loop builder that grades a skill against a definition of done, the brief for standing up a decision council, and the full agent builder.
TOOLKIT 22 live
The Skills Library
Ready-made skills that teach Claude one job properly — morning brief, weekly review, invoice organiser, sales prep, business travel, your own decision council. Drop one in your Brain and call it by name.
THE MAP 6 levels
The climb to Level 4.5
Where you are now, and what each step up actually costs you — the six levels, the tools that belong to each one, and the setup underneath them. Most businesses stall at three; this is the page that shows you why.
TOOLKIT
Model × Effort cheat sheet
Four models, four effort levels, and the two mistakes that quietly cost you the most. Pick what you're doing and the matrix lights up the right combination.
Grab a skill in the kit
Twenty-two ready-made skills, one click each
the pack, or one at a time · in the kit
Get access
Step one, then the nine chapters
STEP·01 —
Build your shoebox
CH·00 —
What an AI Brain is
CH·01 —
The Structure Interview
CH·02 —
Obsidian & plugins
CH·03 —
The Page layer
CH·04 —
Graph View
CH·05 · OPTIONAL —
The Vault Index optional
CH·06 —
Keeping it alive
CH·07 —
Your team & Git
CH·08 —
CLAUDE.md deep dive
·The AI Brain Kit·Webinar pack·
The climb · L1 → L6
Each tier is a different relationship with the models, not a different subscription. The dashed line is where this kit lands you: level four, plus the habit that keeps it there.
Levels five and six — where this is all going
named, with the tools and the setup each one takes · in the kit
Get access
The map · where you are

The climb to AI Level 4.5

Six levels sit between typing into a fresh chat and a business that mostly runs itself. Almost everyone stalls at three. This kit is the climb from three to four and a half.

Level · abilityTools · mode · setup
↑build a Brain it understands, not just reads
L4Brain ownerYou are here
Models that know enough to execute from a single prompt.
CoworkClaude Code
on one AI Brain
Setup · infraStructured folders, real files, skills, and approval loops.
↑give your context a permanent place
L3Organiser
A place, not a Brain. Access — not understanding.
ProjectsCustom GPTsa loose folder
a place to put files
Setup · infraFiles uploaded, nothing structured. The ceiling most people hit.
↑stop retyping — save and reuse context
L2Prompter
Decent one-offs. Nothing persists.
ClaudeChatGPT
chat + saved prompts
Setup · infraNone — you re-explain the business daily.
L1Tinkerer
Fresh chats, no memory.
ClaudeChatGPT
chat only
Setup · infraNone.

Level four is a Brain your models can read and act on. The half is the habit that keeps it there. The kit walks the whole climb — and names the two levels above it.

Chapter 01 · Your Brain gets built

The Structure Interview

Your job in this chapter: answer questions and say yes. Claude does everything else — every folder, every file move, every word of your constitution.

What the interview is

The starter vault you downloaded ships with a skill called the Structure Interview — about 30 questions, the ground a good General Manager would cover in their first week. What the business sells and where the money comes from. How a job actually flows from enquiry to paid. Where your own time goes. Who does what, who decides what, which tools run the place, what's written down and what lives in heads. And then: what you expect with Claude in place — the jobs it takes first, the things it must never touch, what "worth it" looks like in three months.

Almost every question comes with lettered answers, so most replies are a single letter. You can always type your own answer instead. Claude also reads whatever files you've put in the folder first, so it confirms what it can see rather than asking you things your own documents already answer.

When the questions are done, Claude proposes a folder structure shaped around your answers — your words, your workflows — and waits. Nothing is created, moved, or changed until you say yes. On the yes, Claude builds the whole tree, files every document you gave it, flags anything it wasn't sure about rather than guessing, and writes your constitution.

Watch an interview run
ClaudePress play to watch a real interview excerpt — Brightwater Plumbing, a fictional six-person business. The full transcript lives in the appendix.
A real excerpt, replayed. Single-letter answers, own words whenever you'd rather.
End of the free chapter

The rest of Chapter 1 — and the eight after it

You have just seen the interview that starts a Brain. What follows is the part that turns the answers into a working folder — and then eight more chapters that fill it.

  • The rest of Chapter 1 — from answers to a structure that holds
  • Chapters 2–8 — the wiki, the graph, the index, the habits
  • The starter vault — the folder, ready to go
  • Skills, agents, cheat sheet — the whole toolkit
Get access Everything above stays free
Chapter 00 · The idea

What an AI Brain is

An AI Brain is a folder. That's the whole trick.

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

One folder on your computer that holds what your business knows — who you are, how you work, what you've decided, what you've learned — written in plain files that both you and Claude can…

The system, live
your documents meeting transcripts decisions projects CLAUDE.md THE CONSTITUTION one folder the Brain pages · meetings · sops · agents Claude answers, with sources quotes & drafts filed & up to date
Everything feeds one folder. Claude reads it under the constitution — and answers from what the business actually knows.

The three apps

Everything in this guide happens in three applications with buttons and windows. No terminal, no code, nothing typed into a black screen — anywhere in this guide.

Claude CoworkClaude Code
Where the work happens — the tab in the Claude desktop app that works on a folder. Point it at your Brain and talk to it: it reads the files, follows the constitution, and does the building, filing, and writing.Where the work happens — the tab in the Claude desktop app that works on a folder on your machine. Point it at your Brain and talk to it: it reads the files, follows the constitution, and shows you every change it wants to make before it makes it.
Obsidian
How you look at your Brain — linked pages, and the living graph of everything your business knows. Chapters 2 and 4.
GitHub Desktop
How the Brain gets shared, backed up, and given a history — your team on one Brain without emailing files around. Chapter 7.
The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

Start in CoworkStart in the Code tab

This is the one thing to get right before Chapter 1. A normal Claude chat in the browser can't touch files on your computer — it can only read what you paste into it. The desktop app can.…

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

How this guide runs

The chapters are a build order, not a menu. Each one stands on the previous: the interview in Chapter 1 fills your folder, Chapter 3's topic pages create the links, and those links are…

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access
Chapter 02 · Make it visible

Obsidian & plugins

Your Brain exists. This chapter makes it visible — as linked, browsable pages, and later, as the graph.

Install and open

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access
Obsidian
Obsidian
Create new vault
Create a new Obsidian vault in a folder.
Create
Open folder as vault
Choose an existing folder of Markdown files.
Open1
Open vault from Obsidian Sync
Set up a synced vault.
Sign in
Obsidian's welcome screen — ① Open folder as vault, pick your Brain folder.

Community plugins, in plain English

Obsidian can be extended with plugins — small add-ons built by the Obsidian community, installed from a browser inside the app. Think of them the way you'd think of apps on a phone: the…

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access
Obsidian — Settings
Options
General
Editor
Files and links
Appearance
Hotkeys
Core plugins
Community plugins
About
Community plugins
Restricted mode is currently on. Community plugins are disabled. Plugins are built by the community and are turned off by default — turning them on lets you install add-ons.
Turn on community plugins1
One click — Restricted mode off.
Settings → Community plugins — ① the Restricted Mode toggle.

The one plugin this guide needs: Obsidian Git

This Brain runs on one required plugin: Obsidian Git. It's what will keep your Brain synced and backed up from inside Obsidian once Chapter 7 sets up the sharing layer. Installing it now…

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

Next

Open a few of your filed documents in Obsidian and click around. Then Chapter 3 — where the Brain gets its memory.

Chapter 03 · Memory

The Page layer

This is where the Brain stops being organised storage and starts being memory.

The pattern

The approach is based on Andrej Karpathy's LLM Wiki pattern, adapted here for a business vault. The idea: instead of Claude re-reading your raw documents and transcripts every time you ask…

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

What a page looks like

Your vault ships with 10-Business/_example-page.md — the shape every page follows, wherever it lives. Hover each part (or tap it) to see what it's for:

Anatomy of a page
You never write these pages yourself. Claude builds and maintains them, inside the folder the topic belongs to.

Running the page layer

The rules live in your constitution and in the skill file 90-Skills/page-update.md. In Claude Coworkthe Code tab, with your Brain folder selected:

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access
ChatCoworkCode
+New session
Sessions
Page update
Weekly review
⚙ Customize
Local▦brightwater-brain+6 −2
run the Page Update
▤Read 05-Inbox/ — 3 files✓
▤Read 70-Delivery/hydroflow-supplies.md✓
Three inbox files all name the same supplier. One page to update, one decision to add.
✎Edit70-Delivery/hydroflow-supplies.md+6 −2
## The facts
− Account #4471 · Net 20
+ Account #4471 · Net 30 · 12% trade discount over $2k/mo
## Decisions
+ 2026-07-14 — gas fittings moved to them
## Sources
− 1 filed transcript
+ 2 filed transcripts · 1 price list
Apply this edit?RejectAccept1
+Reply to Claude…Manual ▾Sonnet 5 ▾↑
The best reason to run the Brain in Claude Code — ① the exact wording of every page change, red for what leaves and green for what lands, before a word of it is saved.
05-Inbox
▤email-thread-mar.pdf
▤meeting-notes-old.docx
▤price-list-v3.xlsx
three raw files that all mention one supplier
⟶
Obsidian — 70-Delivery / hydroflow-supplies.md
Hydroflow Supplies
The facts
Account #4471 · Net 30 · 12% trade discount over $2k/mo
Decisions
2026-07-14 — gas fittings moved to them
2026-03-02 — 30-day terms agreed
Related
[[pricing-rules]] · [[gas-work]]
Sources
2 filed transcripts · 1 price list
Before and after — three raw files become one living page.

Why answers get better

Two things change once the pages exist. Claude's answers come from pages that are already distilled and current, instead of from whatever raw file it happened to find. And every answer can…

Next

Those [[links]] your pages now carry aren't decoration. Open Chapter 4 and look at what they've been building.

Chapter 04 · Your map

Graph View

The shortest chapter, and the one you'll screenshot.

Open it

In Obsidian, click the Graph View icon in the left ribbon (or press Cmd+G).

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access
A Brain, drawn live
drag the nodes
Generated from link structure — exactly how Obsidian draws yours. The filters below mirror the graph-settings search box.
Obsidian — Graph view
▤◇☰⌕
pricing-ruleshydroflow-suppliesbathroom-renosmonday-meetingsreno-websitesupplier-review
Graph View in Obsidian — every dot a note, every line a [[link]].

Make it readable

Two settings turn a pretty picture into a useful one. Open the graph settings (the gear in the graph pane):

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access
Obsidian — Graph view
▤◇☰⌕
pricing-ruleshydroflow-suppliesbathroom-renosmonday-meetingsreno-websitesupplier-review
Filters
Groups1
● 10-Business
● meetings
● 70-Delivery
Graph settings — ① colour groups per folder, ② a filter typed in.

Next

The graph is how you see the Brain's connections. Chapter 5 builds the version Claude uses — optional, and best left until the vault is big enough to need it. If you're still in your first…

Chapter 05 · Claude's map
OptionalNot part of the day-one build — come back to this one later

The Vault Index

Chapter 4 gave you the map of your Brain. This chapter gives Claude one — when the Brain gets big enough to need it.

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

The problem it solves

This is a scaling problem, and only a scaling problem. As your Brain grows, "read everything, then answer" stops being smart. A year of transcripts, dozens of topic pages, live jobs —…

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

What gets built

Two layers of map, both maintained by Claude — you'll rarely open either:

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access
Map first, then open only what's needed
00-Meta/index.md
hydroflow-supplies — primary fittings supplier · 4 links
pricing-rules — markup + quote rules · 6 links
jul-supplier-review — July meeting, filed · 3 links
bathroom-renos — core offer page · 5 links
van-stock — consumables list · 2 links
team-roster — who does what · 3 links
warranty-claims — process page · 2 links
…41 more notes mapped
Claude, answering
Press "Ask it" — the question: "what did we agree with Hydroflow?"
The index pointed at two notes. Two got opened. The other forty-six stayed shut.

When to turn it on

Not on a fresh vault. The index earns its keep when the Brain outgrows a single read — roughly a few months of real use. The signals, any one of which is enough:

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

Build it — when you get there

In Claude Coworkthe Code tab, with your Brain folder selected:

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access
Claude Cowork — brightwater-brain
rebuild the index
Index rebuilt.
42pages mapped
117links found
2pages with zero links1
Unlinked: warranty-notes.md, old-flyer-copy.md — invisible to your graph. warranty-notes could link to [[bathroom-renos]]. Want me to add the links?
+Reply to Claude…Sonnet 5↑
The rebuild report — pages mapped, links counted, ① zero-link pages flagged with suggested homes.
ChatCoworkCode
+New session
Sessions
Index rebuild
Page update
⚙ Customize
Local▦brightwater-brain+118 −96
rebuild the index
▤Read 90-Skills/index-rebuild.md✓
◇Walked the vault — 42 pages✓
✎Wrote 00-Meta/index.md + 8 MOC files✓
Index rebuilt.
42pages mapped
117links found
2pages with zero links1
Unlinked: warranty-notes.md, old-flyer-copy.md — invisible to your graph. warranty-notes could link to [[bathroom-renos]]. Want me to add the links?
+Reply to Claude…Accept edits ▾Sonnet 5 ▾↑
The rebuild in the Code tab — ① zero-link pages flagged. This one is running in Accept edits: the index and the MOCs are Claude's own bookkeeping, so there's nothing to read line by line.

Keep it current

Page-by-page updates keep the rows Claude touched accurate, and nothing else. Transcripts filed by other skills, pages you edit by hand in Obsidian, links added and removed elsewhere — none…

Next

Structure, memory, your map — and Claude's map waiting for the day the vault needs it. Chapter 6 is the habits that keep the whole thing alive, and those you start now.

Chapter 06 · The habits

Keeping it alive

A Brain that isn't fed goes stale, and a stale Brain gives stale answers. This is the feeding routine — two habits, both mostly Claude's work.

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

Habit one: transcripts in the drop zone

If the interview found that your meetings get recorded — Fathom, Otter, Zoom, Teams, anything that produces a transcript — this is the highest-value habit in the guide.

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access
05-Inbox
Favourites
▦ Desktop
▦ Documents
▦ 05-Inbox
▤_example-filed-transcript.md
▤2026-07-28-monday-meeting.md
▤fathom-mon-4-aug.txt1
dragged in, as-is
⟶
Claude Cowork — brightwater-brain
file the new transcript
Filed2026-08-04 — Monday meeting · Dana, Mike, Lisa
SummarySpring schedule locked; supplier pricing reviewed
DecisionsHarbour St reno starts 11 Aug
Actions☐ Lisa — chase 3 overdue invoices
Pages[[bathroom-renos]] · [[hydroflow-supplies]] updated
Full transcript kept in full underneath — filed, never replaced.
The drop flow — ① a transcript dragged in, then the filed note beside it.
05-Inbox
Favourites
▦ Desktop
▦ Documents
▦ 05-Inbox
▤_example-filed-transcript.md
▤2026-07-28-monday-meeting.md
▤fathom-mon-4-aug.txt1
dragged in, as-is
⟶
ChatCoworkCode
Local▦brightwater-brain+52 −3
file the new transcript
▤Read fathom-mon-4-aug.txt✓
✎Wrote 60-Sales/meetings/2026-08-04-monday-meeting.md✓
✎Edited 2 topic pages✓
Filed2026-08-04 — Monday meeting · Dana, Mike, Lisa
SummarySpring schedule locked; supplier pricing reviewed
DecisionsHarbour St reno starts 11 Aug
Actions☐ Lisa — chase 3 overdue invoices
Pages[[bathroom-renos]] · [[hydroflow-supplies]] updated
Full transcript kept in full underneath — filed, never replaced.
The same drop flow in the Code tab — ① a transcript dragged in, the filed note beside it. The +52 −3 counter opens every line of it.

Habit two: the Weekly Brain Review

Once a week, in Claude Coworkthe Code tab:

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

The one rule that keeps it all working

Anything that doesn't have an obvious home goes in 05-Inbox/ — never force-filed, never guessed into a folder. The inbox is supposed to catch things; the weekly review is supposed to empty…

Next

Your Brain is now structured, remembering, mapped, and fed. Chapter 7 gives it to your team — with history, rules, and an undo button.

Chapter 07 · Share it

Your team & Git

The longest chapter, because it earns it: this is where your Brain stops living on one computer.

What Git gives a business

Git is a system that tracks changes to files. For your Brain it means three things worth having:

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access
Commit · push · pull, live
GitHub — private the shared copy You your Brain folder Teammate same Brain, own computer commit + push ↑ pull ↓
Snapshots go up with a note; teammates pull them down before they start. That's the whole daily loop.

Put the Brain on GitHub

GitHub is where the shared copy lives. A free account includes private repositories — private means invisible to everyone except people you invite.

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access
GitHub Desktop
Current repositorybrightwater-brain
Current branchmain
Fetch originLast fetched just now
Publish repository
Name
brightwater-brain
✓Keep this code private1
ticked = invisible except to people you invite
Publish repository
GitHub Desktop — Add Local Repository, then Publish with ① 'Keep this code private' ticked.

The daily rhythm: commit, push, pull

Three words cover everything:

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

Let the plugin do it for you: Obsidian Git

Commit, push and pull are three moves you now have to remember. You won't, not every day — nobody does. So hand them to a plugin: Obsidian Git runs all three on a timer from inside the…

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

Bring on the team

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

The rules layer

The technology is now done; what keeps a shared Brain sane is social. Your vault ships with 00-Meta/team-rules.md — a folder-owner table and six working rules, waiting for your names:

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

Next

One file has come up in every chapter: the constitution. Chapter 8 makes yours strong.

Chapter 08 · The constitution

CLAUDE.md, the constitution

The single biggest difference between a Brain that behaves and one that drifts is the quality of this file.

Why it's the constitution

CLAUDE.md is the one file Claude reads at the start of every session in your vault. Not sometimes; every time. Whatever it says shapes everything that follows — which makes it the…

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

Anatomy of a strong one

Six blocks, each answering a question Claude would otherwise guess at:

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access
Obsidian — CLAUDE.md — the constitution
▤◇☰⌕
Identity
## Who we are
Brightwater Plumbing — six people, Nelson–Tasman.
Hard rules
## Hard rules
2. Never delete anything without asking.
3. Never invent numbers or sources.
Folder map
## Folder map
70-Delivery/renos/ — one folder per live reno
05-Inbox/ — unsorted, never guessed
Page rules
## Page rules
One page per topic, in its own folder. Answers cite pages.
Update rules
## Update rules
Transcripts filed per 90-Skills. MOCs current; full index rebuild once the vault is big.
Team rules
## Team rules
See 00-Meta/team-rules.md. Changes: Dana.
The six blocks of a constitution, labelled down the margin.

The strength checklist

Read your constitution against these. Every "no" is your next edit — tick them off as yours passes:

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

Weak vs strong

The difference is checkability. Tap each row to reveal the strong version:

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access

You're done — and the Brain isn't

That's deliberate. You now have what almost no business has: a memory that updates itself, a map of what you know, a team working from one source of truth, and a constitution that gets…

The rest of this section is in the kit
steps · exact wording · the parts you copy
Get access
Locked · in the kit

Step one — the shoebox

The fifteen minutes before Chapter 1 that decide whether your Brain sounds like your business or like everyone else in your industry. It is the step other kits skip, and the one that does the most work.

  • What step one is — the move that comes before the interview
  • What to gather — what earns its place, and what wastes the fifteen minutes
  • The bar — how much is enough, and what falling short costs you later
  • Where it lands — the one move that sets Chapter 1 up to do the rest
Get access Chapter 1 is open in this preview
Locked · in the kit

The starter vault

The folder every chapter builds into, zipped and ready to drop on your desktop — numbered folders, the constitution template, and the first notes already in place.

  • The folder tree — set up the way the guide uses it
  • The constitution template — the file Claude reads first
  • Starter notes — so the Brain is never staring at an empty folder
  • One download — unzip, point Claude at it, start
Get access Chapter 1 is open in this preview
Locked · in the kit

The full worked example

One business taken end to end: the complete interview run, the structure that came out of it, and the finished Brain — the long version of what Chapter 1 only starts.

  • All thirty questions — the run in full, not the excerpt
  • The proposed structure — and why it was shaped that way
  • The finished folder — what it looks like once it is working
  • Everything quotable — wording you can reuse as-is
Get access Chapter 1 is open in this preview
Locked · in the kit

Skills, Agents and the Council

The templates behind everything in the kit — how a skill is written, how an agent is briefed, and how a council of agents argues a decision out before it reaches you.

  • The skill template — the shape every skill follows
  • The agent template — brief, tools, and boundaries
  • The Council — several agents, one decision
  • House standards — so what you write next still fits
Get access Chapter 1 is open in this preview
Locked · in the kit

The model cheat sheet

Which model to reach for, when, and what it costs you in time — the page most people end up keeping open all day.

  • Model by job — the pick for each kind of work
  • When to switch — the tells that you are on the wrong one
  • Speed and cost — the trade-off in plain terms
  • One page — printable, no hunting
Get access Chapter 1 is open in this preview
Locked · in the kit

Twenty-two ready-made skills

Skills are the jobs your Brain already knows how to do. Twenty-two of them ship with the kit, written and tested — drop the folder in and they work.

  • Twenty-two skills — grouped by the work they do
  • Written out in full — read them, edit them, keep them
  • One-click pack — or take them one at a time
  • Works in both — Cowork and Claude Code
Get access Chapter 1 is open in this preview
Locked · in the kit

Eleven ready-made agents

Agents are the specialists — each one briefed for a single kind of work so it stays sharp. Eleven come with the kit, in two packs.

  • Eleven agents — in two packs
  • Each one briefed — scope, tools, and when to call it
  • Ready to install — no setup beyond the folder
  • Built to be edited — they are just text
Get access Chapter 1 is open in this preview
Locked · in the kit

Terminal, without the fear

The one-page setup for people who have never opened a terminal — every command written out, with what it does and what you should see back.

  • Every command — copy, paste, done
  • Mac and Windows — both paths, side by side
  • What good looks like — the output to expect
  • When it goes wrong — the three usual causes
Get access Chapter 1 is open in this preview
Locked · in the kit

The Agent Command Centre

The dashboard that sits over the whole Brain — see what your agents are doing, kick off work, and keep the whole thing under one roof.

  • One place — every agent, one screen
  • Install guide — the full README, in the kit
  • Runs locally — your folder, your machine
  • Open source — yours to change
Get access Chapter 1 is open in this preview
✓
You're reading the preview. Chapter 1 is free — the rest of the kit is locked.
9 chapters · starter vault · 22 skills · 11 agents · cheat sheet
Get the kit