ha-card-sizing-determinelisted

Determines the optimal size declaration for an existing custom Lovelace card or panel — getGridOptions() (sections) and getCardSize() (masonry/panel/stacks) — so it renders correctly across devices in view and edit mode, then hands the result to an implementation step patching both callbacks. Classifies as content-dependent (rows:"auto" + min_columns) or deterministic (numeric rows + min_rows:rows), verifies the rows:"auto" CSS preconditions, and treats edit-mode overlay overlap as a sizing defect, per spec/ha/card-panel-sizing. Activate on "size this card correctly", "fix the edit-mode overlay overlap", "determine getGridOptions/getCardSize", or equivalent German requests. Do not activate for scaffolding a new card (ha-lovelace-card-scaffold), a full frontend solution (ha-lovelace-solution), panels/UX (ha-panel-add/-author/-ux-audit), feature rows (ha-card-features-add), or live-instance deploy/verify (ha-integration-deployer/-verify).
nolte/claude-home-assistant · ★ 1 · AI & Automation · score 68

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

# HA Card Sizing Determine Spec: `spec/ha/card-panel-sizing/en.md` (EN canonical) / `spec/ha/card-panel-sizing/de.md` (DE translation). This skill operationalises that decision procedure; it does not restate it — read the spec for the field reference, the `.fit-rows` mechanics, the source citations, and the canonical card examples. ## Why this is a skill, not an agent - **Mid-flow interactivity** — the content-shape classification (content-dependent vs. deterministic) and the determined declaration are approved by the user *before* the card is patched; that approval gate is the load-bearing dimension and belongs on the visible command surface. - **Output flows back to the main conversation** — the determined `getGridOptions`/`getCardSize` values and the patch are read back inline, without a structured report boundary; the caller keeps working in the same context. - **Bounded inline generation with a hand-off** — determination plus patching two small callbacks fits inline; where a specialist edit is warranted the skill orchestrates it (skill-orchestrates, agent-executes) rather than doing isolated heavy work itself. - Counter-dimension considered: the source-grounded analysis could suggest an isolated agent (context-window protection), but the analysis reads one card file against a spec that is already loaded, so isolation buys nothing and the approval gate wins — skill. ## When this skill activates Use this skill when an **existing** custom Lovelace card or panel needs i