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
Shipped pluginA Claude Code plugin I shipped: persist a session to disk and resume it instead of /compact. The workflow comes from an r/ClaudeCode thread (credited); the packaging, the ADRs, and the one-command install are mine.
evidence-builder
BuiltA skill that turns real homelab artifacts (configs, logs, topology) into a push-ready repo, and never a topic on its own. Real work in, verifiable evidence out.
Five-team research engine
BuiltA research skill whose five teams run blind to each other, with disconfirmation built into the structure and a run that ends by declaring a ceiling instead of one confident number.
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.