claude-home-assistant

Deploy a Home Assistant Custom Integration from a local repo into a running HA pod inside a Kind / local Kubernetes cluster — lint pre-flight, file copy via `kubectl cp`, mandatory bytecode-cache cleanup, HA-process restart via `kill 1` (NEVER `kubectl delete pod`), wait-on-ready, and post-restart log tail — and return a structured PASS/FAIL report. Use when the user says "deploy the integration to HA", "rollout to the kind cluster", "kubectl-cp the integration", "ship the latest code to HA", or equivalent German requests ("Integration auf HA ausrollen", "ins Kind-Cluster deployen", "den aktuellen Stand auf HA bringen"). Don't use for production deployment (HACS / add-on distribution), don't use for firmware / device flashing, don't use for backend-side work, and don't use to commit / push / open a PR — those are caller follow-ups. Returns a tight summary plus a full-text log artifact under `.audits/deploy/`.

Diagnose a deployed Home Assistant Custom Integration in a running HA pod inside a Kind / local Kubernetes cluster — pod-status check, recent-log scan with error-pattern detection, installed-files verification — and return a structured health report. Read-only: never deploys, never restarts, never modifies state. Use when the user says "verify the integration on HA", "check the kind-cluster HA", "diagnose the HA pod", "is the integration loaded", or equivalent German requests ("Integration auf HA prüfen", "den HA-Pod diagnostizieren", "läuft die Integration?"). Don't use to deploy (`ha-integration-deploy`), don't use to restart HA, don't use to test pytest-based behaviour (that's the test harness), and don't use for production HA instances. Returns a tight summary plus a full-text diagnostics artifact under `.audits/verify/`.

Augment an existing Home Assistant Custom Integration config flow with an additional pattern — multi-step tenant / account selection, zeroconf discovery, reauth flow, reconfigure flow, or OAuth as alternative to API key — non-destructively. Activate on phrasings like "add a multi-step tenant selection to the config flow", "add zeroconf discovery to the existing config flow", "add a reauth flow", "add reconfigure flow", "add OAuth login as alternative to API key", "erweitere den Config-Flow um Tenant-Auswahl". Do not activate for greenfield scaffolding (use ha-integration-scaffold), pure schema edits, or destructive refactors.

Append a new DataUpdateCoordinator to an existing Home Assistant Custom Integration — separate role, separate update interval, full integration with RuntimeData mapping, options-flow entry, translations, and tests. Activate on phrasings like "add a new coordinator for alerts", "split the existing coordinator", "add a faster polling coordinator", "füge einen Coordinator für X hinzu". Do not activate for greenfield scaffolding (use ha-integration-scaffold), coordinator removal, or push-based coordinators.

Generate EntityDescription tuple lists for an HA Custom Integration platform module from a datapoint table or API-schema JSON, plus matching strings.json and icons.json entries. Activate on phrasings like "add sensors from this datapoint list", "generate EntityDescriptions from this CSV", "add binary_sensors for the alert types", "erweitere die Sensor-Plattform um folgende Datapoints". Do not activate for greenfield scaffolding (use ha-integration-scaffold) or when the platform file does not yet exist.

Scaffold a complete Home Assistant Custom Integration skeleton — manifest, lifecycle, config flow, coordinator, entity, platforms, translations, icons, diagnostics, plus pytest harness — in one go, conformant to every MUST pattern in spec/ha/*. Activate on phrasings like "scaffold a new HA Custom Integration", "create a Home Assistant integration", "neue HA-Integration scaffolden", "skeleton einer HA Custom Integration anlegen", "bootstrap a new HACS-compatible integration". Do not activate when the user only edits an existing integration, scaffolds a Lovelace card, scaffolds an ESPHome component, scaffolds a blueprint, or asks for a YAML-to-config-flow migration — those have their own skills.

Scaffold a vanilla-JS Lovelace card under custom_components/<domain>/www/<card-name>.js with every mandatory lifecycle method, shadow DOM, entity-change detection, HA CSS custom properties, and auto-registration in __init__.py. Activate on phrasings like "scaffold a Lovelace card for the integration", "add a custom Lovelace card called `<name>`", "erstelle eine Custom-Card für `<Resource>`". Do not activate for greenfield setup (use ha-integration-scaffold), TypeScript / Lit cards, or card removal.