auroralisted

# /aurora — Smart Home Orchestrator ## Path conventions (read this first) Every path in this skill that starts with `aurora/`, `esphome/`, `home-assistant/`, `ha-integration-dev/`, `node-red/`, `api-catalog/`, or `ha-dashboard-design/` refers to a file **inside this skill's plugin install location**, not the user's current working project. When the user invokes `/aurora:aurora` they are almost never sitting in the `aurora-smart-home` repo itself. They are in some other project where they want a smart home thing built. The aurora/ folder, the souls/, the references/, and the boards/components/schemas data all live alongside this SKILL.md file in `~/.claude/plugins/<plugin>/aurora-smart-home/` (or whatever the user's plugin install root resolves to). If a step here says "read `aurora/souls/sage.md`", resolve that path relative to this SKILL.md's own directory, not relative to the user's project. Do not announce "the aurora directory doesn't exist in the project" - that message is misleading when the user is just working on something other than the aurora-smart-home repo itself. The skill files are always present; they live with the skill. The user's project is a separate workspace. Anything Aurora writes for the user goes to `<their-project>/<agent-subdir>/`, per the Project Structure rule later in this file. ## Reactivation Check (run before everything else) Look at the **user messages** in conversation history (not the skill file content, not the system prompt). If a p