ha-lovelace-solutionlisted

Plans and orchestrates a complete Home Assistant Lovelace/frontend solution from a result-oriented requirement, so the user never picks individual frontend skills. Decomposes the requirement into the minimal combination of artifacts across the Lovelace skill family (cards, editors, features, badges, strategies, panels, WebSocket backends), presents a dependency-ordered artifact plan for approval, then dispatches the owning skills — resolved from the live inventory at runtime — threading the card tag, file path, module resource, and domain between steps, surfacing a WebSocket backend's Python-integration dependency in the plan. Activate on "build a custom card with an editor and a feature", "create a dashboard strategy plus a badge", "set up a custom panel with a WebSocket backend", or equivalent German requests. Do not activate for a single clear frontend artifact (the owning skill), the Python integration backend (ha-integration-solution), or deploying to a live HA instance. Supports resume on re-invocation.
nolte/claude-home-assistant · ★ 1 · AI & Automation · score 68

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

# HA Lovelace Solution Spec: `spec/claude/ha-lovelace-solution/en.md` (EN canonical) / `spec/claude/ha-lovelace-solution/de.md` (DE translation). This skill is the **front door** to the Lovelace/frontend skill family. It does not generate any artifact itself — it decomposes the requirement, plans the combination, and dispatches the owning skills, each of which owns its generation and spec conformance. ## Why this is a skill, not an agent - **Plan-before-generate gate** — the artifact plan must be presented and explicitly approved before any generation; that human-visible gate is core to the contract and an agent's fire-and-forget shape would lose it. - **Mid-flow interactivity** — clarifying questions (JS vs. Lit/TS, tag name, target entity, backend need), plan confirmation, and the "this needs a Python integration backend" decision are per-run dialogues. - **Orchestrator that dispatches other skills** — the skill-orchestrates-skill default (see `skill-vs-agent`) keeps the entry point in skill form, like `ha-automation-solution` dispatching the automation authoring skills. - Counter-dimension considered: the per-artifact generation could run as parallel agents, but the plan approval and the identity threading (card tag → editor/feature, card → command) must stay visible in the user's context; skill wins. ## When this skill activates Use this skill when the user describes a **frontend result** that likely needs more than one artifact, and should not have to know which fr