fiorix

Cut a chan release: the git-first rc-pinned cycle, the one-commit version-pin bump, the publish=false dry run, and the GA tag that publishes. Covers the macOS signing path.

Run the chan pre-push gate (shellcheck, actionlint, fmt, clippy, test, no-default-features build, gateway build, web checks, marketing checks) and the isolated/own-gate model for multi-agent rounds.

Spin up and tear down a local chan test server over a throwaway or existing workspace, including the rebuild cycle for frontend changes.

Code architecture, structural review, simplification, interface boundaries, refactoring discipline, configuration design, and maintainability reviews.

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

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

Linux systems engineering, low-level infrastructure, networking, containers, virtualization, storage, systemd, operational debugging, and shell/Python diagnostic tooling.

Frontend and web app work, especially TypeScript, Svelte 5, Vite, SPA architecture, browser APIs, CodeMirror 6, and Rust-backed web frontends.

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.

How to cut an sdme release across crates.io, GitHub Releases, Fedora Copr, the Ubuntu Launchpad PPA, and the Arch AUR. Use when publishing a new sdme version, bumping the version, tagging vX.Y.Z, wiring or debugging the release CI, or when a release build fails on any of those channels.

Operational guidance for using sdme and troubleshooting sdme-managed systemd-nspawn containers. Use when an AI agent needs to help with sdme commands, container lifecycle, rootfs import/build/export, OCI or Kubernetes pod workloads, networking, stop/start failures, systemd-nspawn, machined, machinectl, journalctl, systemctl diagnostics, or repository changes to sdme itself.