Made with Claude Code
Every line of every project on this site, the engines, the pages, the maps and the docs, was written with Claude Code from a terminal, a browser and a phone. Axel has learned to work really well with Claude. Here are his tips.
1Make sure Claude knows who it is
Number one. A properly constructed CLAUDE.md tells Claude what the project is, what the rules are, and how you like to work. Every session starts from it, so everything you would otherwise repeat goes there.
2Give really clear directions
Say what you want, what done looks like, and what must not change. Vague asks get confident guesses. A sentence of context saves an hour of rework.
3Make sure Claude has all the tools it needs
Database access, deploy commands, test runners, a browser for screenshots. If Claude has to work around a missing tool, the work gets worse and slower. Grant the access, then hold Claude to the result.
4Decompose the work
One feature, one branch, one pull request. Big asks become plans first, then steps that can each be checked. Claude is good at small things done in sequence and at running several of them in parallel.
5Be patient. Claude will make mistakes
Some will be silly. Point them out plainly, ask for a test that would have caught it, and move on. The mistakes are cheap; the lesson stays in CLAUDE.md.
6Kind of like working with a person, isn’t it?
Context, clear asks, the right tools, small steps, patience. The same things that make a good colleague make a good session. Treat it that way and it works.