The 30-second version (for people who don't want to read)
- Use the form just above to grab the kit (drop your email). It is a
.zip. - Unzip it somewhere stable like your Documents folder (not Downloads, which gets cleaned out), then open that folder with an AI coding agent: Claude Code, Codex, or Cursor (you'll need a paid plan on one of them).
- Tell it: "Read START-HERE and run the kit."
- Answer its questions. It asks where to build your workspace, then creates it on your own machine and handles the rest. Done.
The rest of this is the why, if you want it.
A few weeks back I showed you how to give Claude a memory: one interview that becomes a Master Statement, so it stops guessing who you are every time you open a new chat. A lot of you built one. The question that kept coming back was the same: okay, now where does everything else go?
Fair question. The Master Statement fixes who you are. It does nothing about the mess. Your notes live in one app, your projects in another, a big chunk of your useful context is buried in old chats you will never scroll back through, and the rest is sitting in some company's cloud you do not actually control. The memory was step one. This is the rest of it.
So I built the next rung. You open the kit, you say one line, and your AI interviews you and builds you a real workspace on your own machine. Not a blank template you have to fill in. A structure that falls out of your own answers, so you only get the parts you actually use.
What it builds
From one conversation, on your disk, as plain files:
- A second brain for what you know, your notes, organized around the areas of your life and work you actually care about.
- Project homes for what you make, sorted by kind (code, video, writing), and only the ones you need. If you do not film, there is no empty Video folder sitting there.
- A local change history so every edit your assistant makes is recorded with its name on it, and any single change can be undone. It runs on your computer. Nothing gets uploaded.
- A small config that any future AI reads first, so it lands already knowing how your workspace is laid out.
You do not paste anything
This is the part people do not expect. You are not copying prompts into a chat window one at a time. You drop the kit folder where you want your workspace, open it with an AI coding agent, and say one line: "Read START-HERE and run the kit." It does the interview, builds the workspace, and sets up the history. You answer questions. That is the whole job.
Point it at your mess and watch it sort
This is where it goes from "nice folders" to "oh, I get it." The kit builds you a clean structure, then hands you an inbox. Drop your actual scattered files in, say "file my inbox," and watch it put each thing where it belongs. Your own stuff, organized in front of you. That's how you know it's useful, not because I told you it is.
And it never touches your originals: it copies things into place and leaves what you dropped exactly where it was. It copies, it never moves or deletes. Do it today with a handful of files just to see it work, or six months from now when you find another old folder.
Why I keep harping on the "you own it" part
I have built software for 13 years, and the pattern I trust least is the one where all your context lives inside a product that can change its mind, its price, or its terms next quarter. The convenient version of your life lives in someone's cloud. The version you own lives on your disk, in formats any tool can read, with a history you can actually inspect. Run git log on your workspace and you can see exactly what changed in every session, and who changed it, you or the assistant. That is the whole point: the day a tool or a company changes, you lose nothing that matters.
It is a beta, and I want you in it
Straight with you: this is an early release. It works, I have run it end to end, but a stranger's machine always finds something mine did not. That is exactly why it is free right now and why I am asking for your help. Run it, break it, tell me what was confusing. When you finish, the kit points you to a 2-minute feedback form, and the rough edges are the thing I most want to hear about.
What you need: an AI coding agent that can read files and run commands. Claude Code, Codex, or Cursor all work; a normal chat window like ChatGPT in a browser won't, because it can't touch files on your computer. All three run on a paid plan; the free tiers don't give the agent the file-and-folder access the kit needs. Then about twenty minutes and a willingness to answer some questions about yourself. Use the form at the top of this page to grab it. Your originals stay yours, and so does everything it builds.
