Uses.

Hardware

• /Mac A Mac mini. Anything that can’t run in the cloud runs here.
• /3D A Bambu Lab 3D printer that Claude can control through bambu-mcp.
• /Energy A Huawei solar system.

The main tools

• /Claude Code I build with it, just as I do with Codex. Each project has its own workspace in Claude: one assistant keeps track of the whole, and every task gets an assistant of its own. If something can only run on my Mac, Claude starts it there and I simply confirm it.
• /Codex Codex, from OpenAI, is my second option for building. Codex reads the same rules and the same wiki as Claude and works on the same code.
• /Claude Design This is where I design every screen before it gets built, and check how it looks on a phone and on a large monitor.
• /Models I pick the model to suit the task: Sonnet 5.5 for clearly defined work, Opus 5.5 for planning and judgement, Fable 5.1 for the hardest problems and Haiku 5.5 for quick look-ups.
• /Next.js + Astro Next for apps with a database, Astro for text-heavy sites like this one.
• /Supabase Database (Postgres), sign-in and Edge Functions, which are small functions running on the server. Several apps share one project; KiHire and the health platform each have their own.
• /Vercel My sites and apps are hosted here.
• /Markdown wiki One place for everything about projects, decisions and lessons learned. Every change is recorded in git, and Claude and Codex both read and maintain the wiki.

Automation

My routines run in the cloud. A personal news digest arrives every morning and evening, and on Mondays a housekeeping run tidies up the system. Automated checks confirm round the clock that my apps are reachable and every routine has run. Only small helpers run on the Mac, such as AgentBar and an hourly storage clean-up.

The framework

• /2 reviewers An architecture review before plans that are hard to undo, and an independent review of the whole result before the merge, that is, before a change goes live. The only exception is a small text correction in a single file.
• /1 contract One file (AGENTS.md) sets out what always applies, for Claude Code and Codex alike.
• /3 steps Plan → build → sign-off, for every project. As the client, you make two decisions. Anything that can’t be undone, such as deleting data, granting access or sending messages, only happens once I have given the go-ahead.
• /Done A change is done when it is live and I have checked it on the live site.
• /Backlog in Markdown One backlog file per project, kept in git. I no longer need a separate tool for it.

Connectors

Connectors are interfaces that let Claude work with other services. Through them Claude can access the database, hosting, design tools and the browser. They belong to my account, not to any one machine, and they can only write where I have given them permission.

The idea for this page comes from usesthis.com.