claude-code
Skills Instead of Setup Docs
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 a separate USB
Monitoring with Claude Code
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 to
Feature Workflow Updates: Driving Features on Autopilot and More
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.
Fallow and Skylos: Static-Analysis Gates for AI-Generated Code
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.