Build one with Claude Code (technical path)

If you are comfortable with the terminal, the technical path gives you the same knowledge system plus version history and the ability to sync it across machines. It is the same idea as the Cowork build, expressed in a code project.

1. A folder under version control

Make a folder and put it under git. This is what gives you history: every change is tracked, nothing is lost, and you can sync it to a private repository and pull it down on another computer.

2. A CLAUDE.md at the root

This is the key file. Create CLAUDE.md in the root of the folder. Claude Code reads it automatically at the start of every session, so it is the natural home for your context: who you are, how the folder is organized, and the rules you want followed.

Inside a session you can press # to add a note, and Claude Code will write it into CLAUDE.md for you.

That one file is the difference between an agent that guesses and an agent that already knows your setup.

3. Structure you will actually use

A simple, durable shape:

• knowledge for notes and concepts
• decisions for the record of what you chose and why
• dashboard for the state of things right now

Use your own names. The point is consistent places, not these exact words.

4. Capture by talking, commit by habit

You still just talk. Tell Claude Code what happened and it writes the file in the right place. Because the folder is git, you commit those changes, and your knowledge system gains a full history you can scroll back through.

This is what mini-me is

The personal system mentioned earlier, mini-me, is exactly this: a git repo, a CLAUDE.md, a knowledge folder, and a dashboard, fed by conversation and committed over time. You are building a smaller version of a thing that genuinely runs a life. The last page turns it into a weekly habit.