My agent harness
The setup I built around the AI model: memory, rules, guards, tools and checks. Claude Code runs all of it, and Codex works from the same files.
Two cooks
Claude Code is my main kitchen. Codex, from OpenAI, is a second cook trained in a different kitchen. A model is weakest at catching its own mistakes, because it reviews with the same blind spots it wrote with. A cook from elsewhere tastes the dish fresh.
- Runs in both
- Four shared skills, and the impeccable design check that runs after interface edits. A project can carry an AGENTS.md file, which Codex reads the way Claude reads CLAUDE.md.
- Shared plain files
- My Second Brain notes and each project's plan and handoff files are plain text. Either cook can open them, so a Codex session can start from the same menu and the same notes.
- Claude Code only
- The hooks and guards, the mods, the slash commands, the helper agents and most skills. The guards at the pass do not protect a Codex session, so Codex runs read-only by default.
How I use it: the codex skill asks for a second opinion on a plan, an approach or a bug with several plausible causes, and I treat its findings as hypotheses to check. double-review runs Codex and a separate Claude reviewer on the same change and combines their verdicts. For risky builds, codex-loop has Codex review the plan until we agree, then build the coding steps, with two points where I approve.
The recipe binder
A skill is a recipe card in a binder: a folder with written instructions, often with scripts and reference files beside them. Claude sees only each skill's one-line description until a task matches, then opens the full card, so know-how costs almost no counter space until it is needed.
A rule file is always on and says how the kitchen runs. A skill is opened for one kind of job and followed by the head chef in the main session. A subagent is a job handed to a separate helper. My skills folder holds 174 skills, 72 of them from the GSD framework; these are the ones I reach for. Tap a binder to open it. Borrowed recipes name their author, and skills tied to a client stay off this page.
Closing the kitchen End of every sessionsession-handoff, end-session, om-idea-capture
- session-handoffEnds a long session by writing a handoff file with what was done, what is open and the next step, so a fresh session picks up with a clean counter.
- end-sessionCloses a session without a handoff file: it saves the session to memory, proposes any notes worth keeping, and states the next step. For work that is finished.
- om-idea-captureFiles content ideas that come up during work into my ideas database. The end-of-session step calls it, so I rarely run it by hand.
Reading the ticket Before I build anythinggrilling, brainstorming, explain-like-im-12
- grillingHas Claude question me hard about a plan or design before anything is built, to find the gaps while they are still cheap to fix.Borrowed from Matt Pocock
- brainstormingWorks through intent, requirements and design before build work. I use it for open questions, like what on a long roadmap should go first.Borrowed from Jesse Vincent (Superpowers)
- explain-like-im-12Switches Claude to plain English with analogies for a technical topic. I use it when an explanation is accurate but hard to follow.
A second taste Second opinions and reviewscodex, codex-loop, systematic-debugging, agy
- codexAsks Codex, a model from a different company, for a second opinion on a plan, an approach or a tricky bug. Its findings are hypotheses to check.
- codex-loopFor risky multi-step builds: Claude plans, Codex reviews the plan until both agree, then Codex builds the coding steps, with two points where I approve.
- systematic-debuggingStarts when something breaks and has Claude find the root cause before it proposes a fix.Borrowed from Jesse Vincent (Superpowers)
- agyPuts a Google Gemini model on call through the Antigravity CLI, mostly for a parallel research pass or a third opinion.
Plating Design and building leanimpeccable, ui-ux-pro-max, taste, ponytail
- impeccableA design skill for layout, type, color and accessibility, with a check that runs after interface edits. It shapes how a page looks; the words come from me.Borrowed from Paul Bakaus
- ui-ux-pro-maxA large reference of design styles, palettes and font pairings. Useful for options; choosing among them stays my job.Borrowed from Next Level Builder
- tasteSteers front-end work away from templated, generic layouts. I pair it with impeccable when helpers build interface pieces.Borrowed from Leonxlnx
- ponytailHolds code work to the smallest change that fully solves the task. My helpers start in its lightest mode, since every extra line is one more to review.Borrowed from Dietrich Gebert
Morning prep Daily workmorning2, email-sweep, explain-deck, om-contract-generator
- morning2My morning briefing: helpers gather calendar, email, projects and news in parallel, and the main session turns them into one page.
- email-sweepTriages a full inbox: applies labels, flags what is urgent and starts reply drafts. It shows the plan before it changes anything.
- explain-deckTeaches me a large topic in layers, simple first, built only from my own material so every slide has a source.
- om-contract-generatorTurns an accepted proposal into a statement of work, filling in my standard terms without inventing new ones.
Front of house Client-facing writingcopywriting, om-proposal-generator
- copywritingConversion-focused copy for web pages, starting from a brief. I use it for structure and review, and edit the final wording myself.Borrowed from Corey Haines
- om-proposal-generatorTurns a discovery call into a proposal with scope and pricing. I read, edit and send it myself.
Also in the kit Used less, still on the shelfwatch, video-clipper, notebooklm, frontend-slides, find-skills, caveman
- watchLets Claude watch a video from a link or file, using still frames and a local transcript, so it understands what is shown as well as what is said.Rebuilt from bradautomates (claude-video)
- video-clipperCuts a long talking-head video into a website cut and short clips, with my approval before anything renders.
- notebooklmDrives Google NotebookLM from Claude, so research I have gathered can become explainers.Borrowed from teng-lin
- frontend-slidesBuilds slide decks as web pages. I keep mine light on text, since they support a talk.Borrowed from Zara Zhang
- find-skillsSearches the public skills directory before I build something, in case a skill for it already exists.Borrowed from Vercel
- cavemanMakes Claude answer in clipped, minimal language to save tokens, for sessions where I only need terse status.Borrowed from Julius Brussee