ha-panel-config-view-addlisted

Adds or completes the configuration/options view of an existing Home Assistant custom panel, conforming to spec/ha/lovelace-panel-config-view — separating deploy-time panel.config from runtime-editable options, composing the options form from ha-form plus ha-selector selectors, persisting domain/shared state through a custom WebSocket command and per-user UI preferences through the frontend user-data store, and gating admin-only options in the UI while enforcing them server-side. Completes the missing config-view pieces on an existing panel and validates them, producing a CONFORMANT / NEEDS-WORK report. Activate on "add a settings view to my panel", "let users configure my panel", "persist my panel options", or equivalent German requests. Do not activate for scaffolding a new panel (ha-panel-add), defining the WebSocket command itself (ha-websocket-command-add), the card config editor (ha-card-editor-add), the backend integration options flow (ha-options-flow-augment), 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 Panel Config View Add Spec: `spec/claude/ha-panel-config-view-add/en.md` (EN canonical) / `spec/claude/ha-panel-config-view-add/de.md` (DE translation). This skill makes an existing custom panel's **configuration/options view** complete and correct, per `spec/ha/lovelace-panel-config-view/en.md`. It completes the missing config-view pieces (deploy-time-vs-runtime classification, the `ha-form` options form, a persistence path, admin gating) and validates them — it does not scaffold the panel (`ha-panel-add`) or define the WebSocket command (`ha-websocket-command-add`). ## Why this is a skill, not an agent - **Human-visible augmentation surface** — the user describes the panel and reads back the options-form composition, the chosen persistence path, and a conformance report; a skill keeps this on the visible command surface, like the sibling `ha-card-editor-add`. - **Mid-flow interactivity** — which values are deploy-time config vs. runtime options, whether options are shared (WebSocket command) or per-user (user-data store), and which controls are admin-only are per-run dialogues the user confirms. - **Bounded, inline generation** — the options view, the form schema, the `hass.callWS` calls, and the admin guards fit inline; no isolated agent context is needed. - Counter-dimension considered: the audit-then-complete loop could be an agent, but the ownership/persistence choice and the report belong in the user's working context; skill wins. ## When this skill activates