hyperscaleav

The periodic fan-out audit of the docs corpus against the code, catching the semantic drift no lint can see (inverted claims, stale arguments, missing surfaces, lagging badges). Run quarterly or before a release tag; the output lands as GitHub issues, never…

Use for the per-slice review pass on any omniglass diff, and always before a feature-loop slice merges inward: a refute-not-confirm review that sweeps the repo's anti-pattern catalog (references/anti-patterns.md) against every hunk and admits only findings…

Use when a vertical-slice PR is built and about to be proposed for merge. Runs the pre-ship validation (fresh make test, make gen drift check, em-dash and attribution scan, a reviewer pass, the docs-with-everything check) and emits the standard ship-review…

Use when adding an operator-console page for an inventory-class entity (a scoped resource with list/tree + CRUD, e.g. interfaces, nodes, tasks, types, tags). Covers the rail (generated typed client + hand-written ListView config), the data layer, the page…

Use when adding or altering an omniglass storage schema element (a new column, a new table, or a rename). Covers how dbmate migrations work (run-once, never edited after applied, embedded), idempotent DDL (incl the Postgres rename DO-block, since PG has no…

Use when adding or changing a Huma API operation (a route, a custom :verb method, or its request/response shape): the registration and gated(...) permission stamp, the Storage Gateway patterns (scoped-CRUD primitive, all-scope directory, in-transaction audit…

Use when an approved definition (an Epic or Feature issue in the /define-work shape, with the architect's approval comment) is ready to execute as a feature loop: creates the sub-issues, opens the integration branch, works each slice test-first through the…

Use when drafting a body of work for architect approval before a feature loop: an Epic (multi-slice) or Feature (single slice) issue in the standard approvable shape (outcome, scope, thin cuts, out of scope, surfaces, acceptance, proposed sub-issues, planned…

Use this skill when resolving Docker Scout CVE findings in Omniglass container images (the `make scan` / `/scan` gate). Covers the build→scan→triage→pin→re-scan loop, the SBOM-project-name vs apk-package-name mapping gotcha, when to pin vs allowlist, and the…

Use this skill when adding or substantially editing a page in the Astro Starlight docs site at docs/src/content/docs/. Handles the file layout, frontmatter format, sidebar registration in astro.config.mjs (the easy-to-miss step that leaves new pages…

Use this skill when adding a new dbmate migration to db/migrations/. Enforces the YYYYMMDDHHMMSS filename prefix and the idempotency requirement. Migrations must be safe to apply against existing instances that may already have partial state.

Use this skill at the start of any change request. Creates a git worktree branched from main, does the work in isolation, then commits, pushes, and opens a PR. This is the default workflow — never commit directly to main or to whatever branch happens to be…

Use this skill when generating, updating, or reviewing a Zabbix source patch in zabbix/patches/. Handles the critical schema patching gotcha — schema changes must touch BOTH create/src/schema.tmpl AND ui/include/schema.inc.php, or DB::insert/DB::update will…