ha-panel-addlisted

Augments an existing Home Assistant integration or frontend repo with one bare custom-panel scaffold — a full-page custom element registered in the sidebar, no data wiring beyond the scaffold — conforming to spec/ha/lovelace-views-panels (custom-panel part). Creates the panel custom element (Lit or another non-React framework receiving hass/narrow/route/panel), the JS-module wiring, and the panel_custom registration in configuration.yaml. Distinguishes a custom panel from a panel-mode view and a custom view. Activate on "add a custom panel", "register a sidebar panel", or equivalent German requests. Do not activate for a production-grade end-to-end panel (ha-panel-author, the consumer front door owning the delivery-shape decision), a single card (ha-lovelace-card-scaffold), a dashboard strategy (ha/lovelace-strategies), the WebSocket command a panel calls (ha-websocket-command-add), greenfield scaffolding (ha-integration-scaffold), or deploying to a live HA instance.
nolte/claude-home-assistant · ★ 1 · Web & Frontend · score 68

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

# HA Panel Add Spec: `spec/claude/ha-panel-add/en.md` (EN canonical) / `spec/claude/ha-panel-add/de.md` (DE translation). ## Why this is a skill, not an agent - **Human-visible augmentation surface** — the user describes a full-page sidebar page and reads back the panel element, the `panel_custom` registration, 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 delivery-shape decision (custom panel vs. custom view vs. panel-mode view) is a per-run dialogue the user approves before generation. - **Bounded, inline generation** — one panel element plus its ES-module wiring and the `panel_custom` config fit inline; no isolated agent context is needed. - Counter-dimension considered: the draft→validate loop could be an agent, but the delivery-shape advice and the `url_path`/registration decisions belong in the user's working context; skill wins. ## When this skill activates Use this skill to add **one** custom panel — a full-page custom element registered in the sidebar that takes over the whole content area — to an existing integration or frontend repo, when the need is a genuine full-page page (not a layout inside a dashboard). ## When NOT to activate - a single card → `ha-lovelace-card-scaffold` / `ha/lovelace-card-patterns` - a panel-mode view (a `type: panel` view holding one full-width card — dashboard YAML, not a scaffolded card) → `ha-panel-aut