hyperscaleav

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 report the architect approves from. Invoke at PR-ready, before asking for approval; re-run after addressing review findings.

Use when building or reviewing interactive overlay UI in the web/ SPA, which is built on Kobalte (@kobalte/core): tooltips, popovers, dialogs/drawers, menus, selects, comboboxes. Covers the headless-plus-Tailwind/daisyUI styling model, the portal pattern that keeps overlays from being clipped by a card or drawer, and the gotchas that waste the most time, above all that an interactive trigger placed inside a <label> silently breaks hover and steals the label. Reach for this whenever you add a floating element, wire a tooltip/popover/dialog, debug one that will not open or is clipped or has wrong accessibility, or test one in jsdom. Pairs with the solidjs skill.

Use when writing or reviewing SolidJS code in the web/ SPA (any .tsx under web/src), or reasoning about its reactivity. Solid looks like React but its model is different in ways that cause real bugs and wrong code review if you carry React intuitions over. Reach for this whenever you touch a Solid component, debug a value that will not update or an effect that will not re-run, pass or ref or mutate a DOM element, build a list or a conditional, or review someone's Solid diff. Especially load it before claiming a piece of Solid code is wrong, since the most common mistake is reviewing Solid as if it were React.

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 config, routing/nav, the test rail, and the invariants (id-as-address facets, edit-only-mutable-fields, cycle-safe parent, authz). NOT for dashboards/alarms/explore/learn surfaces, which need their own primitives.

Use when adding or editing a diagram in the omniglass docs site (docs/, Astro Starlight). Covers the D2 + astro-d2 setup (build-time inline SVG, ELK layout, the d2 binary prerequisite), the colors-live-in-CSS-not-source theming contract that makes diagrams follow Starlight's light/dark toggle, the semantic class to CSS-hook vocabulary, and the build/preview/screenshot loop.

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 RENAME COLUMN IF EXISTS), the three migration buckets, the Storage Gateway ripple, and the testcontainer round-trip RED->GREEN.

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 rule that a CVE with an available fix is never allowlisted.

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 unlinked), internal link conventions, and the .md vs .mdx choice.

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 checked out.

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 silently drop columns at runtime.