dotfiles

Apply a distilled operating discipline to careful, verification-heavy work: read before you write, check the live system before asserting, treat every claim as guilty until proven, make verification adversarial, keep the plan as the spine, hold the scope line, match the house style, and report honestly. Use when starting a high-stakes build, audit, or refactor, or when the user says 'fabler' or asks to apply the operating discipline.

Grill the user about a plan while challenging it against the project's existing domain model and documented decisions, sharpening terminology and updating CONTEXT.md and ADRs inline. Use to stress-test a plan against the project's own language and docs.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use to stress-test a plan, get grilled on a design, or when the user says 'grill me'.

Use for code architecture, structural review, simplification, interface boundaries, refactoring discipline, configuration design, and maintainability reviews.

Use for Python, asyncio, typed Python, data processing, SQL, pandas, document extraction, notebooks, scraping, APIs, and scientific computing.

Use for Rust code quality, idiomatic Rust, async/concurrency, Cargo hygiene, error handling, tests, reviews, and systems programming in Rust.

Use for Linux systems engineering, low-level infrastructure, networking, containers, virtualization, storage, systemd, D-Bus, Varlink, operational debugging, C/Rust systems code, and shell/Python diagnostic tooling.

Use for frontend and web app work, especially TypeScript, Preact, Vite, SPA architecture, browser APIs, Capacitor, and Rust-backed web frontends.