Blog/No. 012

How to set up your own Claude OS

my laptop died from running too many claudes

Frost Thirlwell

Founder, Summit AISOct 14, 2026

Get these by email

Last night I had so many Claude sessions open in VS Code that my laptop ran out of memory and every one of them crashed. Including the one I was drafting this letter in.

When I opened it back up, it still knew who I am, what I run and how I write. None of that lives in the chat. It lives in files in one folder, and that folder is the whole trick.

So this week, instead of showing you mine, here is how to build yours. It is the same setup I gave a client this month, cut down to what you need to start. You do not write any code.

1. get claude code

  1. Download VS Code, it is free: code.visualstudio.com. Install it and open it.
  2. Get a paid Claude plan at claude.ai. Pro is $20 a month. The free plan does not include Claude Code.
  3. In VS Code, click the four squares on the left, search Claude Code, and install the one made by Anthropic. Or open it straight from the marketplace.
  4. Click the Claude icon and sign in with your Claude account. That is your Claude Code.

I drag the Claude panel to the bottom of the screen, so my files sit on top and Claude sits underneath. On a Mac, if it asks to install command line developer tools, click Install. On Windows, install Git for Windows first.

2. give it a home

  1. Make a free GitHub account at github.com/signup. This is where your assistant gets backed up.
  2. Make a new folder in Documents and name it whatever you want to call your assistant. Mine is called Taya.
  3. In VS Code, click File, then Open Folder, and pick it. If it asks whether you trust the folder, say yes. It is yours.

3. let it learn who you are

Open the Claude panel, paste this in as your first message, and answer its questions one at a time. It takes about half an hour. Type skip on anything you do not want to answer.

PASTE THIS INTO CLAUDE
You are my new AI assistant. This folder is your home, and its name is your name.

Interview me so you can actually be useful. One question per message, wait for my answer, and if I say skip, move on. Use my words. Never guess a fact or a number about me. Save what you learn after every answer, so nothing is lost if I stop halfway.

Cover these in order:
1. You: what I call you, and how you talk to me. Blunt or warm, and anything I hate.
2. Me: who I am, where I live, what I do, and who depends on me.
3. Goals: what has to be true a year from now for me to call it a win, with a number and a date. Then the three things that matter most in the next 90 days.
4. My days: when I start, when I am sharpest, when I stop, and what is eating my time that I want off my plate.
5. People: the names I will mention most and who they are to me.
6. Tools: what I run my work and life on. Email, calendar, apps.
7. Voice: I will paste two or three things I wrote so your drafts sound like me.
8. Never: what you must never do without asking me first.

Write the core into CLAUDE.md in this folder: who you are, who I am, my goals, how I like answers, and the never list. Keep the details in a folder called context: me.md, goals.md, people.md, tools.md, voice.md, and state.md for where we stopped and what is next. List those files in CLAUDE.md so you know when to read each one.

Rules from today on: never send anything to anyone unless I say "send it" in that message. Never delete anything outside this folder. Never put a password or a card number in any file. When I correct you, save the correction in CLAUDE.md and check it before you do that kind of job again. When I ask for the same kind of job three times, offer to turn it into a skill.

When we finish, give me a ten line summary of what you know about me. Start now with your first question.
You can build a great system, but it needs to be personalized. It needs to be you.

4. give it three skills

A skill is a job written down so it gets done the same way every time. Paste these in one at a time. When they are in, type / in the chat and you will see them.

SKILL 1, MORNING
Make me a skill called morning. Save it as .claude/skills/morning/SKILL.md, with a name and a description at the top, so it runs when I type /morning or say good morning.

When it runs: read CLAUDE.md, context/goals.md and the top of context/state.md. Give me today's date, one line on where we left off, and the three things that matter most today, in order, each with why in a few words. Twelve lines max, one question at most. Never invent a meeting, a task or a number that is not in a file.
SKILL 2, REMEMBER
Make me a skill called remember. Save it as .claude/skills/remember/SKILL.md, with a name and a description at the top, so it runs when I type /remember, say "remember this" or "from now on", or correct you.

When it runs: turn what I said into one clear sentence in my words and add it to the right file. Facts about me go in context/me.md, people in context/people.md, rules and corrections in CLAUDE.md. Add to the file, never rewrite what is already there. Confirm in one line what you saved and where.
SKILL 3, HANDOFF
Make me a skill called handoff. Save it as .claude/skills/handoff/SKILL.md, with a name and a description at the top, so it runs when I type /handoff or say I am done for the day.

When it runs: add an entry at the top of context/state.md with today's date, what got done, the one next action, and anything waiting on someone. Five lines max. If I corrected you today, check the correction is in CLAUDE.md. If this folder is on GitHub, commit everything with a short message. End with one line: where we pick up next time.

5. back it up

  1. Click the Source Control icon on the left, the one that looks like a branch.
  2. Click Publish to GitHub, sign in, and pick private. Only you can see it.
  3. After every /handoff, click Sync Changes. That is your backup, so if your laptop dies, what it knows does not die with it.

the first week

That is the whole setup. For the first week, type /morning when you sit down, correct it out loud every time it gets something wrong, and type /handoff before you close the laptop. That loop is how mine learned how I work. I told it once to never use dashes in anything it writes. It saved that, and you will not find one in this letter. And open one session per job, not ten. Ask me how I know.

Frost Thirlwell

Get the next one by email

Every Wednesday I write up one system we built, with the prompt to build it yourself. On Sundays, a letter about the week. Reply to any of them and it comes straight to me.

Free. Unsubscribe any time.