DevOps & Infra Orchestrator

The single entry skill for infrastructure work. It locates the task on the layer × operation map — containers, networks (enterprise or homelab), and the deploy/dev-env edges — and delegates to one of 13 specialist spokes. The cross-cutting rule every spoke shares — the read-only-by-default / change-window-for-mutations safety boundary — lives in devops-infra-core; read it before any command that changes state on a device, a cluster, or a production deploy.

Cluster map (spoke → role)

Containers & deploy

• docker-patterns — Docker & Compose for local dev, multi-service orchestration, container security, volumes, networking.
• uncloud — self-hosting cluster mgmt via the uc CLI (Docker + WireGuard mesh + Caddy ingress); deploy, scale, route, inspect.
• canary-watch — post-deploy smoke / canary verification of a live URL (HTTP, SSE, assets, console errors, perf regressions).

Dev environments

• flox-environments — reproducible, cross-platform dev environments (Nix-based, declarative manifest.toml); pin system deps, run local services, kill "works on my machine".