CLI

The regex-based structural diff extractors landed and worked – then hit a ceiling regex was never going to clear. Here’s how coco’s diff pipeline actually moved onto tree-sitter: sharper structural context for commit messages, a layered regex fallback, lazy-loaded grammars – plus the bonus the same parser bought us, syntax-highlighted diffs in the Workstation.

I got one of those “your key is expiring” emails from Humble Bundle, opened my library, and realized I had no idea how many unclaimed games were sitting there. So I wrote a tool. What followed was a crash course in everything Playwright throws at you when you’re automating a real, bot-averse, React-rendered storefront.

localpress is a CLI tool that processes your WordPress media library locally – compression, WebP/AVIF conversion, AI background removal, and round-trip desktop editing – with no cloud SaaS, no recurring credits, and no plugin required on the WordPress side.

Doorman 2.0 ships Cloudflare WAF support alongside Vercel Firewall, a new .doorman.json config format, and 1,100+ tests backing a production-ready multi-provider firewall CLI.

A look at everything that’s landed in ink-enhanced-select-input on the road to 1.0: a headless hook for custom renderers, multi-select mode, inline search, item groups, scroll indicators, Escape/cancel support, and 133 tests – including a real bug caught by writing edge-case tests for backspace handling in searchable mode.

A client needed help managing a few VPSes, so I wrote a small bash script. Three rewrites and 21 releases later, it’s Strut: an open-source CLI for deploying Docker stacks anywhere there’s SSH, built agent-first for the way I actually code now.

Hitting OpenAI’s 1MB / 30-operation cap on Custom GPT actions when your real API has 150+ endpoints is maddening. Spec Shaver is the CLI I built to reduce a bloated OpenAPI spec down to the operations that actually matter, while keeping the schema valid.

Fargo Flags is the feature-flag toolkit I wished existed for Next.js: zero infrastructure, type-safe, and small enough to drop into any project. Here’s the design call that shaped it and the trade-off I’m still not sure about.

I built Vercel Doorman because clicking through firewall rules in a dashboard is the kind of thing infrastructure-as-code was supposed to fix. This is what it does, why JSON config beat a DSL, and what I’d change if I started over.

Coco is the AI-powered Git assistant I built because I was tired of writing terrible commit messages at 11pm. The story of how it grew from a one-off script into something I now use daily across every project.

A Sunday backlog on coco that should have eaten the whole day took about an hour. Not because the AI wrote my code, but because steering files and specs meant it already knew the project instead of me re-explaining it every session. Here is what is in mine, and what I left out.

Every guide blames a fancy zsh prompt when your AI coding agent cannot read the terminal. So I deleted mine, then deleted bash too, and the commands still were not running. Here is where the trail actually led.

After years of building terminal apps and a growing inability to justify my GitKraken subscription, I built a Claude Skill for TUI design. Here’s what’s in it, why I made it, and what I’m planning to build with it next.