ha-integration-scaffoldlisted

Scaffolds a complete Home Assistant Custom Integration skeleton — manifest, lifecycle, config flow, coordinator, entity, platforms, translations, icons, diagnostics, plus pytest harness — in one go, conformant to every MUST pattern in spec/ha/*. Activate on phrasings like "scaffold a new HA Custom Integration", "create a Home Assistant integration", "neue HA-Integration scaffolden", "skeleton einer HA Custom Integration anlegen", "bootstrap a new HACS-compatible integration". Do not activate when the user only edits an existing integration, scaffolds a Lovelace card, scaffolds an ESPHome component, scaffolds a blueprint, or asks for a YAML-to-config-flow migration — those have their own skills.
nolte/claude-home-assistant · ★ 1 · AI & Automation · score 68

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

# HA Integration Scaffold Spec: `spec/claude/ha-integration-scaffold/en.md` (EN canonical) / `spec/claude/ha-integration-scaffold/de.md` (DE translation). ## Why this is a skill, not an agent - **One step in a larger human-driven workflow (decisive):** the greenfield scaffold is the opening move of integration development; domain, platforms, discovery, and harness choices are elicited and approved mid-flow. - **Context access:** the scaffold lands in the repository the conversation is scoped to and its decisions feed directly into the follow-on `ha-*` skills. - **Counter-dimension considered:** a complete skeleton is a large self-contained unit (agent bias), but every structural decision inside it is operator-facing; a fire-and-forget agent would guess where the spec demands a confirmed answer. ## When this skill activates Use this skill when the user wants to: - bootstrap a brand-new HA Custom Integration in an empty consumer repo - get a runnable, lint-clean, test-passing skeleton without having to read every `spec/ha/*` spec first - start an integration that targets HACS distribution ## When NOT to activate - editing an existing `custom_components/<domain>/` → route to the owning augment skill (`ha-config-flow-augment`, `ha-coordinator-add`, `ha-entity-platform-add`, …) or let `ha-integration-solution` plan the combination - scaffolding a Lovelace card → separate skill `ha-lovelace-card-scaffold` - scaffolding an ESPHome device config (YAML) → `ha-esphome-config-sc