ha-esphome-config-scaffoldlisted

Scaffolds one complete ESPHome device-config YAML file — substitutions-driven naming, shared blocks via packages, environment-variable-referenced wifi with AP fallback, natively encrypted api with a per-device key, password-protected ota, logger, and the first sensor/actuator platform blocks — conforming to spec/ha/esphome-config-patterns. Gathers device name, board family, shared-concern set, and initial platforms, runs a pre-flight (collision, credential inventory, device-config root), writes the new <device-name>.yaml, and reports which environment variables the operator must set. Activate on "scaffold an ESPHome device config", "new ESPHome device YAML", or equivalent German requests. Do not activate for extending an existing device file (ha-esphome-config-augment), for the repository layout and shared packages (ha-esphome-fleet-scaffold), for an ESPHome custom component in C++/Python (out of scope), for an HA Custom Integration (ha-integration-scaffold), or for compiling/flashing.
nolte/claude-home-assistant · ★ 1 · Data & Documents · score 68

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

# HA ESPHome Config Scaffold Spec: `spec/claude/ha-esphome-config-scaffold/en.md` (EN canonical) / `spec/claude/ha-esphome-config-scaffold/de.md` (DE translation). Grounding spec: `spec/ha/esphome-config-patterns/en.md`. Scaffolds exactly one new ESPHome device-config YAML per invocation, in the consumer repository's device-config root, conforming to every MUST in the grounding spec. ## Why this is a skill, not an agent - **Mid-flow approval is the contract (decisive):** device name, board family, shared-concern set, and the initial platform list are elicited and confirmed with the operator before any file exists; a fire-and-forget agent would guess where the spec demands answers. - **Quick, targeted change:** one new YAML file in the repository the conversation is scoped to — main-conversation territory per the change-scope dimension. - **Counter-dimension considered:** the boilerplate composition is template-like and self-contained (agent bias), but the scaffold is the first step of device work the conversation continues, so a report boundary would only add friction. ## When this skill activates The user asks for a new ESPHome device config — "scaffold an ESPHome config for a soil-moisture node", "neues ESPHome-Gerät anlegen" — in a repository that holds ESPHome device YAML (fixture layout: `src/*.yaml`). ## When NOT to activate - extending an existing device file (new sensor, bus, component) → `ha-esphome-config-augment` - the repository layout, the `common/` tree,