Notes on things I build and learn.
A personal site has a lifecycle. You scaffold it once, then it lives for years — accumulating SEO improvements, security patches, and dependency churn. Instead of treating each of those as a one-off engagement, I encoded them as three Claude Code skills that share a single source of truth. Here is the architecture, the maintenance contract, and why the pipeline is the spec.
Most projects have typecheck, lint, unit tests, e2e, and visual screenshots — each in its own corner with its own output. A pipeline that fuses all of them into one HTML report changes the incentive structure, especially when an agent is doing the work.
When you have access to Opus, Sonnet, and a file-based skill system, the same project sorts itself into three buckets: one-off planning, routinized procedure, and bulk execution. A walkthrough of doing this in Claude Code, and how the same pattern lands in ChatGPT Codex.
Classic search, AI answers, and model training are three different control planes now. Here is how to think about them as a site owner.
Subscribe to Notes
New notes delivered when I publish. No spam.