Documentation

I read a thread by Geoffrey Litt at Notion, based on a talk he’d given, and his argument stuck with me: as agents get better at writing and checking their own code, the bottleneck moves. It’s not whether the code is correct anymore — it’s whether the person working alongside the agent still understands what’s being built. Not to verify it, but to stay fluent enough to make the next creative call, and to keep evolving the system instead of just accepting whatever it produces. His answer was a prompt he called /explain-diff, which turns a code change into a short explainer: background, an intuition-building walkthrough, the actual code, and — in his version — a short quiz gating whether you’re allowed to ship.

I wanted to try a version of that here, but public. Partly to hold myself to actually staying informed about how this site gets built with an agent, and partly because I think that process is worth looking at in the open, not just the finished result. Every piece here follows Litt’s shape — background, then an intuition, then the real code — written from an actual moment in building this site: a real bug, a real decision, an honest debugging story, in the site’s own type and color system rather than a one-off file living outside the project. The one thing I dropped is the quiz — it was Litt’s own speed regulator, for himself, mid-project, and it doesn’t make much sense for someone dropping in from outside.

So this isn’t a blog about the site. It’s closer to a lab notebook that happens to be public — kept because staying legible to yourself, and to whoever’s curious, is worth doing in the open.