Built in two days, with AI. The judgment stayed mine.
Claude Code wrote most of the files. I decided what to build, what was true, and what was good enough to ship. Five moments from the build show how that split works.
- 01
I changed course when research proved me wrong
My first read of the product that inspired this was shallow. A second look showed it already covered design well, so I rewrote the positioning instead of publishing a false claim.
- 02
I measured instead of claiming
"Saves tokens" became a number: about 800 tokens of startup context. Measuring also caught a bug that would have deleted long briefs.
- 03
My own guardrails caught me
The token guard blocked the case study I was building for this site. The exception was approved, visibly, with a reason.
- 04
I curated instead of collecting
From 914 community skills I adapted about a dozen, credited each one, and rejected the rest.
- 05
Tests found what I'd have missed
A test caught the contrast checker reporting 7.37:1 for white on black. Fixed, it then found real contrast issues on my own site.