The Sequence Labs
Setup guide

What you asked for

AI like an employee

The full setup. Obsidian, the second brain, and Claude Code reading your whole business before you type anything.

You are not building this from scratch. The vault is already made. Download it, open it, fill in one file, and you are running the same thing I run every morning.

Download the starter vault

Every folder, the routing file, three rules, and the templates. Already wired together. Free, nothing to sign up for.

What you need

  • Obsidian free forever, no account needed
  • Claude Pro or Max the subscription you probably already pay for, no API key needed
  • A terminal PowerShell on Windows, Terminal on Mac, both already installed
  • About an hour once. After that it maintains itself.
STEP 01

Unzip the vault somewhere safe

You will end up owning this folder for years, so put it somewhere that syncs.

  1. Download the zip and unzip it. You get a folder called Brain.
  2. Move it to Documents, OneDrive, iCloud Drive or Dropbox. Anywhere that backs itself up.
  3. Not the desktop of a laptop you might drop.

Open the folder in File Explorer or Finder and you can see every file as plain text. That is the whole point. No app owns your notes, and Claude can read them because they are just files.

STEP 02

Open it in Obsidian

Obsidian is a text editor that reads a folder on your computer. That is genuinely all it is. Nothing goes to a server and there is no account.

  1. Download Obsidian from obsidian.md and install it.
  2. Choose Open folder as vault, not create new vault.
  3. Pick the Brain folder you just unzipped.
  4. Open START HERE and follow it. It repeats the next three steps inside the vault so you are not switching between windows.
Skip every plugin. Obsidian has hundreds and you need none of them. The default install does everything in this guide.
STEP 03

What is already in there

You do not have to build any of this. It is the part people give up on, so it is done. Here is what each piece is doing.

CLAUDE.md The routing file. Claude Code reads it automatically at the start of every session and it tells it what to read, in what order, and to log at the end.
START HERE.md Your three jobs before this becomes useful, sitting inside the vault where you will actually see it.
_System/
Knowledge Base/
The business, in one file. Blank headings ready to fill in. This is step 4.
_System/Rules/ Three rules to start with: log every change, nothing is an island, never guess at facts.
_System/
Templates/
The daily log and the project file, so every one comes out the same shape.
Projects/ One example client filled in, so you can see the level of detail. Delete it once you add a real one.
Daily Logs/ Empty for now. Claude fills this in on its own, one file per day.

The underscore on _System is not decoration. It sorts that folder to the top of the sidebar, above everything else, so the important stuff is always the first thing you see.

STEP 04

Fill in the Knowledge Base

This is the only real writing you have to do, and it is the single highest leverage file in the whole setup.

Open _System/Knowledge Base/Knowledge Base.md and answer every heading. Real prices, real client names, the actual words you use.

The headings waiting for you
# Knowledge Base

## The business
## Who I serve
## The problem I solve
## What I sell
## Pricing
## The guarantee
## How I talk
## Current clients and projects
## Decisions I do not want revisited

Be specific. "Small businesses" is not an answer. "Muslim coaches who have built an audience but have no system to convert it" is the level this needs.

Half an hour on this file removes most of the generic output people blame the model for.

STEP 05

Install Claude Code

This is the part people assume is hard. It is one line in a terminal.

Windows

Open PowerShell from the Start menu. Paste this, press Enter.

PowerShell
irm https://claude.ai/install.ps1 | iex

Mac

Open Terminal from Applications, Utilities. Paste, press Enter.

Terminal
curl -fsSL https://claude.ai/install.sh | bash

If you already run Node 22 or later, npm install -g @anthropic-ai/claude-code works instead.

Point it at the vault and log in

Change the path to wherever you put the Brain folder.

Windows
cd C:\Users\you\Documents\Brain
claude
Mac
cd ~/Documents/Brain
claude

Your browser opens. Sign in with the Claude account you already pay for. The terminal says login successful, you press Enter, and you are in. Pro or Max both work. No API key, no per message billing.

Always start it inside the Brain folder. Claude Code reads the folder you launch it from. Start it anywhere else and it sees nothing.
STEP 06

Test that it worked

One question. You will know in five seconds.

Ask it something only your vault would know.

In the terminal
> What do I charge, and who is my client?

If it answers correctly without you pasting a single thing, the setup is live and you are done. Everything below is optional.

If it knows nothing, you started Claude Code in the wrong folder. Close it, cd into the Brain folder, and run claude again.

LATER

Add your own rules

A rule is behavior you would otherwise repeat in every conversation. Three came in the vault. Add a fourth only when something has annoyed you twice.

One file per rule in _System/Rules/. Short. What to do, and why.

_System/Rules/rule-your-thing.md
# Short name for the rule

What to do, in one or two sentences.

Why: the reason, so future you does
not delete it by accident.

Mine include: never use em dashes. Push back on money and facts, never on taste. Save decisions without asking permission first. Every one of those exists because I corrected the same thing twice.

LATER

Turn repeats into skills

Not on day one. Do it the third time you explain the same job.

A skill is a folder with one file of instructions for one recurring task. Typing its name runs it. Mine cover call prep, proposals, deploying a site and writing outreach, because I was pasting the same context every single time.

They live outside the vault, in your Claude folder:

Path
Windows  C:\Users\you\.claude\skills\
Mac      ~/.claude/skills/

one folder per skill, each with a SKILL.md inside
.claude/skills/proposal/SKILL.md
---
name: proposal
description: Write a client proposal using
  their real project file and my real prices
---

## Instructions

1. Read the client's file in Projects/
2. Read pricing from the Knowledge Base.
   Never quote a price from memory.
3. Use the structure of the last proposal
   I sent.
4. Save it to Projects/ and log it to
   today's Daily Log.

The three dashes and the two lines between them are required. Everything under the instructions heading is plain English.

LATER

Back it up properly

This folder becomes the most valuable thing you own within a month. Treat it that way.

If the vault sits in OneDrive, iCloud Drive or Dropbox you are already covered. If you want real version history so you can go back to any single day, put it in a private Git repository. Ask Claude Code to set that up for you from inside the vault. It takes about a minute and it walks you through it.

Either way, check it is actually syncing. Open the folder on your phone once. That is the whole test.

FIRST WEEK

What to actually do now

The setup takes an hour. The useful part is what happens over the next five days.

Day 1 Set it up and stop Steps 1 to 6. Do not add anything clever.
Day 2 Use it for one real job Something you were going to do anyway. Let it write the log at the end.
Day 3 Notice what it got wrong Wrong tone, wrong assumption, wrong price. Write the correction into the Knowledge Base, not into the chat.
Day 4 Ask it something you forgot "What did we agree on Tuesday?" This is the first time it beats a normal chat window.
Day 5 Write your fourth rule Whatever you have now corrected twice. That is how it gets sharper instead of just bigger.

Where people go wrong

Downloading the vault and never filling in the Knowledge Base

Empty headings change nothing. That one file is where most of the value is.

Starting Claude Code in the wrong folder

It reads where you launch it. If it seems to know nothing, check that before anything else.

Adding skills on day one

You do not know what you repeat yet. Wait until something has annoyed you three times.

Correcting it in the chat instead of in a file

A correction in the chat dies when the session ends. A correction in a file holds forever. Every time you catch yourself repeating something, that is a file you have not written.

Quitting on day three

Day one feels the same as before, because nothing is logged yet. Week three is where it stops feeling like a chat window.

If you would rather have it built

I build systems like this for coaches and consultants, so the audience you already have turns into booked clients instead of comments you answer by hand at 11pm.

First step is free. I build a demo on your brand, you look at it, and you decide from there.

Get your free demo