When I stumble upon an unsolved or undocumented problem and solve it, I like to document it here.
Fixing a draft used to mean regenerating the whole post. When a section didn't sound right, the new version would correct it and overwrite three others that were already fine, so I kept a corrected copy open in the Ghost editor, regenerated, and pasted the good paragraphs back
Your writing voice is already on the page. Everything you've published is a record of how you actually write — consistent enough that a tool can learn it from your posts, even if you couldn't spell it out yourself. ghost-blog-mcp is the Claude Code plugin
I've written before about my feature-workflow plugin — capture a feature, plan it, get it reviewed, ship it, mostly one repo at a time. The repos in a couple of my orgs change together, though, and coordinating a change across them in Claude Code kept hitting the same
I built much of my now-playing project with a Claude Code autopilot. I describe a feature, and it gets planned, implemented, reviewed, and shipped without me typing the intermediate steps. To do the implementation and the git work, the autopilot spawns subagents that write to the working tree. When
My now-playing kiosk has a long install document, and it's a long document. Three hundred and ninety-three lines, eight sequential phases, six environment variables that each gate a different optional install path, and a fifty-line section on a particular display whose touch input lives on
Most of the now-playing kiosk was built with my autopilot workflow, which I've written about before. I describe a feature, it gets planned, built, and reviewed, and it ships. For most of the project that's the whole story. But the kiosk's job is
Three patch releases in one evening — how using my own plugin on a real project surfaced a confusing schema field, an internally inconsistent verdict, and the case for state as a first-class concept.
How I wired fallow and skylos into a side project's pre-commit hooks and Claude Code session, then drove the kiosk frontend from a 90A to 100A health score using parallel subagents in git worktrees.
A few days ago I wrote about what happens when you tell Claude a task is urgent — the agent silently introduces correctness bugs and self-reports as confident as ever. The closing section proposed a sharper question: if the bugs are framing-driven rather than caused by any real time
I've been working with Claude Code long enough that the laughably bad time estimates have become background noise. Claude thinks a 90-second task takes 30 minutes. I ask it to plan a sprint that I know we can do in a few days and it thinks it