ha-card-preview-addlisted

Ensures an existing custom Lovelace card's preview is completely and correctly implemented, conforming to spec/ha/lovelace-card-preview — the card-picker gallery preview (preview flag plus a getStubConfig rendering a real non-error tile), the editor live preview (deterministic from setConfig/hass, re-rendered on config-changed), reading the preview element property (and legacy editMode), and preview correctness (no real service calls while previewing, a graceful placeholder over a thrown render). Completes the missing preview pieces on an existing card and validates them; produces a CONFORMANT / NEEDS-WORK report. Activate on "make my card show a preview in the card picker", "the card preview is broken / empty", or equivalent German requests. Do not activate for scaffolding a new card (ha-lovelace-card-scaffold), the config editor itself (ha-card-editor-add), card layout/sizing (ha/lovelace-layout-antipatterns), 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 Preview Add Spec: `spec/claude/ha-card-preview-add/en.md` (EN canonical) / `spec/claude/ha-card-preview-add/de.md` (DE translation). This skill makes an existing custom card's **preview** complete and correct, per `spec/ha/lovelace-card-preview/en.md`. It completes the missing preview pieces (picker preview, editor live preview, the `preview` property guard, preview correctness) and validates them — it does not scaffold the card (`ha-lovelace-card-scaffold`) or build the editor (`ha-card-editor-add`). ## Why this is a skill, not an agent - **Human-visible augmentation surface** — the user describes the card and reads back the `window.customCards` change, the `getStubConfig`, the `preview`-property guard, and a conformance report; a skill keeps this on the visible command surface, like the sibling `ha-card-editor-add`. - **Mid-flow interactivity** — whether a live picker preview is wanted (`preview: true`), the demo entity/placeholder for the stub config, and which side-effects to guard are per-run dialogues the user confirms. - **Bounded, inline generation** — the customCards flag, the `getStubConfig`, and the preview guards fit inline; no isolated agent context is needed. - Counter-dimension considered: the audit-then-complete loop could be an agent, but the demo-entity choice and the report belong in the user's working context; skill wins. ## When this skill activates Use this skill to ensure an **existing** custom card previews completely and correctly — it