01 // Engineering with AI
Engineering with AI
I build with Claude Code as a pair: it drafts, I direct and review, and nothing ships that I can't explain. These are the tools I've built on top of that loop; the full method and toolkit live in the repo.
How I work
- Grill the plan before any code: one decision at a time, dependencies first.
- Walking skeleton first, then fan out the hardening with file-level ownership.
- Review, simplify, and tests on every change; steering files keep it honest and on-spec.
GRC Fleet Auditor
FlagshipThe flagship, built with an AI pair across four security-hardening passes: ~4,500 lines of Python, 200 tests, and a design that refuses to certify a host it didn't actually assess. The same auditor listed above, here for how it was built.
clear-not-compact
Deprecated pluginA Claude Code plugin I shipped and have since deprecated: it persisted a session to disk so you could resume it instead of /compact. Built-in auto-compaction and the 1M-token context window removed the problem, so it is no longer maintained. The workflow comes from an r/ClaudeCode thread (credited); the packaging, the ADRs, and the one-command install are mine.
These are tools I drive, and I'm exact about what's mine. The engineering, the steering files, and the guardrails are mine; the frameworks I run on top of Claude Code are other people's, and credited.