# Your own instructions for OpenCode

Rename this file to `AGENTS.local.md` (drop the `.example`) and OpenCode will read
it at the start of every session, alongside the add-on's own `AGENTS.md`.

- The add-on **never** writes to `AGENTS.local.md`. Add-on updates cannot overwrite it.
- Delete the file to stop loading it. There is no setting to toggle.
- `AGENTS.md` wins if the two ever conflict — safety rules and approval requirements
  stay in force regardless of what you put here.
- Everything in this file is sent to the model with **every** request, so keep it
  short and specific. A page of standing preferences is useful; a diary is not.
- Never put passwords, tokens, or API keys here. Reference them with `!secret` instead.

Delete the examples below and write your own.

---

## About my setup

- All Zigbee devices go through Zigbee2MQTT, not ZHA. Do not suggest ZHA workflows.
- The house has three floors: basement, main, upstairs. Areas are named after rooms.
- Presence detection is unreliable in the garage — treat those sensors with suspicion.

## How I want you to work

- New configuration goes in `packages/`, one file per feature. Do not grow
  `configuration.yaml`.
- Prefer template sensors over automations that write to `input_number` helpers.
- Name entities `<area>_<device>_<function>`, for example `kitchen_ceiling_brightness`.
- Always show me the diff before writing, even for one-line changes.

## Leave these alone

- Anything under `custom_components/` — those are managed through HACS.
- The `packages/energy.yaml` file. It is tuned and I do not want it reformatted.

## Useful context

- My electricity tariff changes at 07:00 and 22:00; automations that care about
  cost should use those boundaries.
- The Sonos speakers drop off the network occasionally. That is expected, not a
  configuration bug.