Home / About

As of November 2026

What I run today

Every name on this page is an example. Swap any of them and the lessons still hold. I list them because people ask.

Where the truth lives

Git
Carries what is true between chats. One branch and one pull request per slice.
A PRD
One project document every agent reads first.
Git worktrees
One working copy per agent, so nobody overwrites anybody.

The lesson behind this

Skills I use

Grill Me
Made by Matt Pocock. The opening interview: read first, then ask everything that matters in one batch.
Cavecrew
Made by Julius Brussee. Agents report in short lines that keep decisions and evidence visible.
Unslop
Made by Lauren Tan. Removes filler and vague language while keeping the meaning.
I have ADHD
Maintained by Ayoub Ghriss. Keeps the next action clear and the steps short.

The skill library

Who checks the work

Bugbot
Code defects on the complete branch.
Thermos
Security, structure and how easy it will be to maintain.
A vulnerability scanner
Dangerous paths and leaked secrets.
Gstack
Walks the user journey in a real browser.

The lesson behind this

How the system remembers

A project wiki
Architecture, decisions and history.
Repository rules
The failures every agent must read.
Mem0
Preferences and lessons across sessions.
Hooks
Inject context and enforce rules without relying on recall.

The lesson behind this

Keeping it safe

A secret store
Values stay outside the repository and are injected only at run time.
An isolated database branch
Agents work on their own branch of the database and can break it freely.
A loopback check
Local tools refuse any address that is not this machine.

The part of the job behind this

Which model does what

Faster, cheaper models
Mechanical work.
A capable middle lane
Ordinary building.
The strongest models
Migrations, security and final review.
One pinned model
Coordinates a long AFK run.

The lesson behind this

What you should not copy

The exact gates. Mine are merging, the production database and publishing. A low-risk internal prototype may need fewer. A product that handles money, personal data or public claims may need more.

The exact tools. Another team may replace every product named here. What matters is that each task on this page is done by something.

The weight of what I built. What I would skip and keep in a smaller system.

Try “secrets”, “merge”, “handover” or “database”.