ha-card-editor-addlisted

Adds an ha-form-based visual configuration editor to an existing custom Home Assistant Lovelace card, conforming to spec/ha/lovelace-card-editor. Generates the editor custom element (a LitElement implementing setConfig + a hass setter + a render() over <ha-form> with a schema, .data, and computeLabel, plus a _valueChanged handler that dispatches config-changed with bubbles/composed and detail.config), the card's static getConfigElement() returning that element, static getStubConfig() for a default config without the type parameter, and the customElements.define registration. Activate on "add a config editor to my card", "wire up the ha-form editor", "make my card configurable in the UI", "füge meiner Card einen Editor hinzu". Do not activate for scaffolding the card itself (ha-lovelace-card-scaffold), base card-level patterns (ha/lovelace-card-patterns), entity-selector filtering (ha/lovelace-card-entity-selector), 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 Card Editor Add Spec: `spec/claude/ha-card-editor-add/en.md` (EN canonical) / `spec/claude/ha-card-editor-add/de.md` (DE translation). ## Why this is a skill, not an agent - **Human-visible augmentation surface** — the user names an existing card and reads back the editor element, the `ha-form` schema, and the conformance report; a skill keeps this on the visible command surface, like the sibling frontend skill (`ha-lovelace-card-scaffold`). - **Mid-flow interactivity** — the editor field set, the selector choices, and the `computeHelper`/`assertConfig` decisions are a per-run dialogue the user approves before generation. - **Bounded, inline generation** — one editor element plus the two card hooks (`getConfigElement`, `getStubConfig`) and the `customElements.define` registration fit inline; no isolated agent context is needed. - Counter-dimension considered: the draft→validate loop could be an agent, but the field/selector decisions belong in the user's working context; skill wins. ## When this skill activates Use this skill to add **one** `ha-form`-based visual configuration editor to an **existing** custom Lovelace card — the editor `LitElement`, the card's `static getConfigElement()` and `static getStubConfig()`, and the `customElements.define` registration. ## When NOT to activate - scaffolding the card itself (file layout, `set hass`, render, registration) → `ha-lovelace-card-scaffold` - base card-level patterns and portfolio house style → `ha/lovelace-card-