How I work
Every project starts as a written spec. That's how I move fast without losing track of why things were built.
01 Spec
Requirements, in writing
Each project starts with a product requirements document: who it's for, what it does, and what success looks like.
02 Plan
A technical plan before code
The spec becomes a technical plan: stack, architecture, data model and the order to build things in.
03 Build
Build, review, ship
I build with Claude Code as my pair and review every change. The docs stay in the repo as a record of each decision.
I write a spec for every project, then build with Claude Code as my pair. The decisions, the review and the result are mine. This site was built the same way.