#Tooling

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.

I rebuilt coco’s interface with a TUI design skill, then needed to show it off. Screenshots and demo GIFs turned out to be their own craft, full of subtle traps. So I built a skill for that too.

git-scenarios came together fast because the project it serves, Coco’s TUI git workstation, had very clear testing needs. A couple of weeks after the v0.1.0 extraction it’s now stable at v1.0.0: 32 scenarios, 60+ atoms, five framework adapters, 527 tests across three operating systems. The v1 work wasn’t about features, it was about trust: typed error classes, precondition guards, property-tested determinism, cross-platform CI, and shedding the last of its coco branding.

I have written the same 80 lines of git test setup more times than I want to count. @gfargo/git-scenarios v0.5.0 extracts the helper layer that grew up inside Coco: a registry of named scenarios (mid-merge-conflict, submodule-with-history, mid-bisect, and 8 more), a composable atom API for building your own, and a tool-agnostic CLI that drops any tool into a real repo in a known state.

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 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.

What I actually put in .npmignore (after the time I shipped a 600MB package by accident), why the package.json files field is usually the safer default, and the npm pack –dry-run check that saves you from publishing things you shouldn’t.

Upgrade your ink-select-input for seamless vertical and horizontal layouts enabling more intuitive and space-efficient interfaces in your Ink CLI apps