Downloads

Working files, not lead magnets

Everything here is something I actually use, cleaned up so you can open it, edit it, and make it yours. No email gate: the files are yours either way. They’re plain text – open them anywhere, edit them, or hand them straight to your AI.

The page starts small on purpose. I’d rather hand you a few files that earn their place than thirty that pad a list.

~/downloads · no email gate
claude-code-test-drive.txtdownload · txt

The Claude Code test drive – what would Claude Code do with your files?

A read-only, paste-in test: Claude Code looks at a folder of your files, interviews you, and hands you a verdict on what moving would actually take. It’s allowed to say stay. The story behind it, and the test itself, live here.

first-file-template.txtdownload · txt

The first file – a starter memory file for your AI

You just need to start with one file: who you are, what you’re working on, how you like things done. Tell your AI to read it first, every time. Start tiny means start here.

wiki-kickstarter.txtdownload · txt

The wiki kickstarter – a starter wiki that builds itself

Paste in the prompt and your wiki will set itself up. The idea is Andrej Karpathy’s. I run mine in Claude Code.

how-to-use-your-wiki.txtdownload · txt

How to use your wiki day to day

The daily habits: talk to your wiki like a chat session, keep sessions single-purpose, and end them on purpose.

wiki-under-the-hood.txtdownload · txt

Wiki under the hood – the technical lessons

The technical lessons: parallel-session safety, the always-read-on-start hook, raw-folder routing, secrets handling, and the harvest habit.

prompts-i-actually-use.txtdownload · txt

The prompts I actually use

No magic phrasing. These are just plain sentences I say over and over to keep my AI honest, anchored to what I actually gave it, and me in charge of the work.

three-starter-upgrades.txtdownload · txt

Three starter upgrades for your AI wiki

The first three things I’d add to a fresh wiki: a “what’s hot” page, the save-everything rule, and the harvest loop. Hand the file to your AI and it builds its own versions. Step 4 of the build path teaches why.

New to all of this? Build your own AI second brain is the on-ramp, and the blog has the stories behind these files.

The newsletter

New files go to the list first

When something new earns its place here, subscribers hear about it before the page updates. A letter every week or so, no hype.

Double opt-in · unsubscribe anytime · GDPR-compliant