ha-panel-authorlisted

Develops a described full-page or dashboard-surface need end-to-end to production grade, conforming to the full relevant spec set. First decides the delivery shape (custom sidebar panel vs. panel-mode view vs. custom view as layout container) per spec/ha/lovelace-views-panels and spec/ha/lovelace-layout-antipatterns, then builds it — dispatching ha-panel-add for the base scaffold, wiring hass data access (spec/ha/frontend-data-api) and any WebSocket backend (via ha-websocket-command-add), and enforcing responsive layout, performance, shadow-DOM theming, and naming discipline. Activate on "build a proper custom panel for …", "develop a full-page HA panel that shows …", or equivalent German requests. Do not activate for the minimal one-panel scaffold only (ha-panel-add), a single card (ha-lovelace-card-scaffold), a multi-artifact frontend solution (ha-lovelace-solution), a dashboard strategy (ha-strategy-add), the Python backend (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 Author Spec: `spec/claude/ha-panel-author/en.md` (EN canonical) / `spec/claude/ha-panel-author/de.md` (DE translation). This skill is the **senior panel-developer** of the Lovelace/frontend family. Where `ha-panel-add` mechanically scaffolds one custom panel against a single spec, this skill develops a panel **end-to-end to production grade**: it picks the right delivery shape, wires the data channel, honours layout/responsive/performance/theming discipline, and holds the result to the whole relevant spec set — then reuses `ha-panel-add` for the base scaffold rather than reinventing it. ## Why this is a skill, not an agent - **Human-visible senior surface** — the user describes a need and reads back the delivery-shape decision, the build plan, the generated code, and a multi-spec conformance report; a skill keeps that judgement on the visible command surface, like the sibling `ha-lovelace-solution`. - **Mid-flow interactivity** — the delivery-shape decision (custom panel vs. panel-mode view vs. custom view), the data-source/backend decision, and plan approval are per-run dialogues the user must see and approve before generation. - **Orchestrator-leaning** — it dispatches `ha-panel-add` (base scaffold) and, when a backend endpoint is needed, `ha-websocket-command-add`; the skill-orchestrates-skill default keeps the entry point in skill form. - Counter-dimension considered: the develop→validate→iterate loop could be an agent, but the shape decision, the backend c