home-ops

Use when classifying, triaging, or organizing Paperless documents; reviewing the paperless inbox; assigning document metadata; discussing taxonomy conventions; or running `./scripts/paperless.sh classify`. Triggers on phrases like "classify documents", "triage paperless", "check the inbox", "what needs classification", "paperless taxonomy". Do NOT use for uploading documents, managing users/groups/workflows, or general paperless CRUD.

Use when querying or mutating Home Assistant via `./scripts/hass.sh` (entity states, attributes, templates, history, logbook, areas, energy dashboard, Lovelace dashboards, automations, scripts, repairs, registry entries); authoring, editing, or debugging HA automation/script YAML or Jinja templates; inspecting entities, devices, integrations, or areas on the HA instance at `home.${SECRET_DOMAIN}`; firing events or calling services. Triggers on phrases like "check HA", "Home Assistant entity", "trigger this automation", "what's the state of sensor.X", "run the script", "HA template", or any edit under `scripts/hass/`. Do NOT use for unrelated smart-home/IoT platforms.

Use when adding, modifying, debugging, refactoring, or reviewing `hops` CLI commands and domain modules in `scripts/hops/` and `scripts/hops.sh`; creating new subcommands, click groups, or output formatters; changing core helpers (`core/runner.py`, `core/format.py`, `core/nodes.py`, `core/workload.py`, `core/time.py`, `core/resolve.py`, `core/helm.py`); extending cluster introspection coverage (node, storage, app, flux, query, debug, dns, backup, validate). Triggers on phrases like "add a hops command", "fix hops output", "new hops domain", "extend hops", the `hops` escape hatch in AGENTS.md, or any edit to files under `scripts/hops/`. Do NOT use for simply running existing `hops` commands during diagnosis (no skill needed) or for non-cluster/app-specific scripts (e.g., `hass.sh`).

Use when diagnosing DNS resolution failures, investigating blocked domains, debugging website or app connectivity problems reported by users, querying Blocky DNS query logs, or editing Blocky allowlist/denylist configuration in `kubernetes/apps/dns-private/blocky/`. Covers `./scripts/hops.sh dns` subcommands (`search`, `logs`, `blocked`, `test`) and the `log_entries` table in the Blocky CNPG cluster. Triggers on phrases like "site X is broken", "DNS isn't working", "why is this domain blocked", "check Blocky logs", "allowlist this domain", or any edit to `blocky/data/config.yaml`. Do NOT use for authoritative/external-dns troubleshooting (different providers, different tooling).

Use when searching, reading, creating, updating, moving, archiving, or deleting Outline wiki documents and collections via the `ol` CLI (`@doist/outline-cli`, installed via mise); managing the household knowledge base at `wiki.${SECRET_DOMAIN}`; scripting bulk document operations with `--json`/`--ndjson`; authenticating or updating the CLI. Triggers on phrases like "search the wiki", "create an Outline doc", "update the Outline page", "list collections", "move this doc", or any invocation of the `ol` command. Do NOT use for content that belongs in the repo `docs/` directory (ADRs, investigations, runbooks, AGENTS.md directives) per the Outline vs docs/ boundary.