ha-entity-platform-addlisted

Scaffolds one active platform entity into an existing Home Assistant Custom Integration — a command-driven domain (climate, cover, light, fan, lock, media_player, and peers) whose entity exposes async command methods — conforming to spec/ha/entity-platform-types plus the matching ha/entity-platforms-* family spec. Creates the platform module with the entity subclass, its EntityDescription where the family uses one, the supported_features bitmask, the async command methods, and the async_setup_entry wiring. The operator names the target domain and confirms the family first. Activate on "add a climate/cover/light entity", "scaffold an active platform entity", or equivalent German requests. Do not activate for declarative read-type entities via EntityDescription tables (ha-entity-description-map), the coordinator itself (ha-coordinator-add), greenfield scaffolding (ha-integration-scaffold), device-automation triggers (ha-device-automation-add), or deploying to a live HA instance.
nolte/claude-home-assistant · ★ 1 · AI & Automation · score 68

Install: claude install-skill nolte/claude-home-assistant

# HA Entity Platform Add Spec: `spec/claude/ha-entity-platform-add/en.md` (EN canonical) / `spec/claude/ha-entity-platform-add/de.md` (DE translation). ## Why this is a skill, not an agent - **Human-visible scaffolding surface** — the operator describes a device capability and reads back the platform module, the feature bitmask, the command methods, and the conformance report; a skill keeps this on the visible command surface, like the sibling augment skills (`ha-coordinator-add`, `ha-entity-description-map`, `ha-device-automation-add`). - **Mid-flow interactivity** — the platform/domain decision and the family confirmation are per-run dialogues the operator approves before generation. - **Bounded, inline generation** — one platform module plus its description and setup fit inline; no isolated agent context is needed. - Counter-dimension considered: the draft→validate loop could be an agent, but the domain decision and the active-vs-declarative gate belong in the operator's working context; skill wins. ## When this skill activates Use this skill to scaffold **one** active platform entity — a command-driven domain (`climate`, `cover`, `light`, `fan`, `lock`, `media_player`, `vacuum`, `valve`, `humidifier`, `water_heater`, `siren`, `lawn_mower`, …) whose entity exposes async command methods — into an existing integration. ## When NOT to activate - datapoints authored declaratively as `EntityDescription` tables — read-type `sensor`/`binary_sensor`/`button`, and the descri