Recent Posts

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 small filesystem tweak that turned my open source projects into a single workspace my agents can actually reason about. Nested git repos, a centralized orchestrator, and a documentation loop that finally stays in sync.

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.

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.

After building Spec Shaver as a CLI for trimming oversized OpenAPI specs, I kept finding myself wanting a visual way to do the same thing. SpecForge is what came out of that itch: a web app for importing, curating, and exporting OpenAPI specs in the browser.

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.

Why I rolled my own SVG path editor instead of reaching for an existing one – what the off-the-shelf options got wrong for my use case, and what I learned about Bezier curves trying to make the handles feel right.

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.

Augments started as a way to give my own AI workflows a consistent set of tools across machines. This is the story of what it does, what I left out, and the cybernetic-enhancements framing I leaned into.

A bash one-liner that lists your locally downloaded Ollama models, plus the equivalent in Python, Node.js, Go, and Rust. The command I kept rewriting until I just dropped it into a shell alias.

Overcome information overload with AI tools like Fabric. Intro on how I’m starting to augment and enhance how I consume and interact with content on the daily to learn more in less time.