Solo builders
AI coding tools for solo builders
Building alone changes what an AI coding agent has to be good at. There is no reviewer, so the checks an agent runs on itself are the only checks, and the guardrails have to be structural rather than social: a config file the agent always reads, hooks it cannot skip, tests it must pass.
What actually changes
Nobody catches what you and the agent both miss. That makes the project config file — CLAUDE.md, AGENTS.md or `.cursor/rules` — the single highest-leverage thing to write, because it is the only place your standards exist at all.
It also makes plan mode worth the extra step more often than it would be on a team. A plan you read before any code is written is the review that would otherwise have happened at the pull request.
Recipes for your stack
These are documentation pages. Some are free to read; the rest are part of the subscription.
Where you stand
Twenty-five questions on how production-grade your AI engineering is, with a plan at the end. Free, no account.
Frequently asked questions
Which tool should I start with?
The one already included in a subscription you pay for: Claude Code comes with a Claude plan, Codex with eligible ChatGPT plans. If neither applies, start from where you want to work — an editor points to Cursor, a terminal to Claude Code, GitHub or Slack to Codex.
What should I set up first?
The project config file — CLAUDE.md, AGENTS.md or .cursor/rules depending on the tool. Working alone, it is the only place your standards exist, so it is the one artefact that keeps paying back on every session.