ha-esphome-fleet-scaffoldlisted

Scaffolds the repository layout of an ESPHome fleet per spec/ha/esphome-project-structure — the config root with flat device files, a common/ package tree grouped by consumer, include/ for C++ lambda headers, archive/ for retired devices, a keyed asset tree, the base package plus a first board package that pulls it in, the environment-variable documentation every credential needs, and the .gitignore entries keeping tool state and secrets out of version control. Works greenfield and on an existing flat collection, where it proposes the layout as a migration plan before touching anything. Activate on "set up an ESPHome repository", "restructure my ESPHome configs", or equivalent German requests. Do not activate to write or extend one device file (ha-esphome-config-scaffold / ha-esphome-config-augment), to cut a single package (ha-esphome-package-author), to wire CI validation (ha-esphome-ci-scaffold), or to audit a layout (ha-esphome-fleet-reviewer).
nolte/claude-home-assistant · ★ 1 · AI & Automation · score 68

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

# HA ESPHome Fleet Scaffold Spec: `spec/claude/ha-esphome-fleet-scaffold/en.md` (EN canonical) / `spec/claude/ha-esphome-fleet-scaffold/de.md` (DE translation). Grounding spec: `spec/ha/esphome-project-structure/en.md`; the device-file half is `spec/ha/esphome-config-patterns/en.md`. Establishes the repository structure an ESPHome fleet is built in — once, at the top — so every later device is one new file and every shared concern has exactly one home. ## Why this is a skill, not an agent - **Mid-flow approval is the contract (decisive):** the config root, the package cut, and — on an existing repository — which files move where are decisions the operator confirms before anything is written; a fire-and-forget agent would restructure a repository on guesses. - **Repository-shaping change in the current context:** the operator iterates on the proposed tree ("keep `src/`", "no `images/` yet") in conversation, which is main-thread territory per the change-scope dimension. - **Counter-dimension considered:** the inventory pass over an existing repository is read-heavy and self-contained (agent bias) — but the read volume is bounded by the fleet's YAML files, and the migration decision must stay visible; skill wins. The read-only conformance verdict on an existing layout is the agent case, and it is owned by `ha-esphome-fleet-reviewer`. ## When this skill activates The user is setting up or restructuring an ESPHome **repository** — "set up a repo for my ESPHome devices", "mei