[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AB5G6DR1KGAPRT7JHDCD2Y":3,"skill-same:01M7AB5G6DR1KGAPRT7JHDCD2Y":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7AB5G6DR1KGAPRT7JHDCD2Y","ha-translations",null,"Add or fix user-facing strings for this Home Assistant custom integration — translations\u002Fen.json and other languages, icons.json, entity names and states, config flow labels and errors, service action descriptions, exception messages, and repair issue text. Use when asked to \"update translations\", \"add a translation key\", \"translate\", \"fix the entity name\", \"add strings for the new sensor\u002Faction\u002Foption\", \"add icons\", or when hassfest reports a missing or unused translation key. Covers the key structure, which keys each feature needs, placeholders, the icons.json contract, and the project's strict rule about only touching en.json. SYMPTOMS — load this if you are about to: write user-facing English into Python; edit a language file other than `en.json`; add an entity without its `entity.\u003Cplatform>.\u003Ckey>.name` key; skip `data_description` on a config flow field; or set `icon=` instead of using `icons.json`.","amg0\u002Fha_ksenia","amg0","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F16444411?v=4","01M7AAZDRNF8BXHM6GAN9QWJ41","01M7AAZDSEHKPEWK6PKK22S2NN",0,"MIT","https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-translations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ha-translations\ndescription: >-\n  Add or fix user-facing strings for this Home Assistant custom integration — translations\u002Fen.json and other\n  languages, icons.json, entity names and states, config flow labels and errors, service action descriptions,\n  exception messages, and repair issue text. Use when asked to \"update translations\", \"add a translation key\",\n  \"translate\", \"fix the entity name\", \"add strings for the new sensor\u002Faction\u002Foption\", \"add icons\", or when\n  hassfest reports a missing or unused translation key. Covers the key structure, which keys each feature needs,\n  placeholders, the icons.json contract, and the project's strict rule about only touching en.json. SYMPTOMS —\n  load this if you are about to: write user-facing English into Python; edit a language file other than `en.json`;\n  add an entity without its `entity.\u003Cplatform>.\u003Ckey>.name` key; skip `data_description` on a config flow field; or\n  set `icon=` instead of using `icons.json`.\n---\n\n# Translations and icons\n\n`translations\u002Fen.json` is the source of truth for every string a user sees. Home Assistant falls back to the raw key\nwhen a string is missing, so a missing key is a visible bug, not a cosmetic one.\n\n**Read [`blueprint.translations.instructions.md`](..\u002F..\u002Finstructions\u002Fblueprint.translations.instructions.md)\nfirst** — it holds the rules: placeholder syntax and the single-quote trap that breaks hassfest, why `[%key:…%]` and\n`strings.json` must never appear here, what hassfest rejects in a string, entity translation requirements, which fields\naccept Markdown, proper nouns, the form of address per language, cross-language structure, and the UI text style.\nThis skill is which keys a given change needs, and how to write them.\n\n## The project rule on languages\n\n- Update **`en.json` only**. Never edit or create other language files on your own initiative — translations are\n  contributed through the project's translation workflow, and machine-translating them creates churn no maintainer\n  asked for.\n- If the developer explicitly asks for another language, confirm which files before starting.\n- During feature work, business logic comes first. Use the translation key in code immediately, and fill in `en.json`\n  either when asked or when the feature is complete.\n\n## Key structure\n\n```jsonc\n{\n  \"config\": {\n    \"step\": {\n      \"user\": {\n        \"title\": \"…\",\n        \"description\": \"…\",\n        \"data\": { \"host\": \"Host\" },\n        \"data_description\": { \"host\": \"The hostname or IP address of the device.\" }\n      }\n    },\n    \"error\": { \"cannot_connect\": \"…\", \"invalid_auth\": \"…\", \"unknown\": \"…\" },\n    \"abort\": { \"already_configured\": \"…\" }\n  },\n  \"options\": { \"step\": { \"init\": { \"data\": {}, \"data_description\": {} } } },\n  \"entity\": { \"sensor\": { \"pm25\": { \"name\": \"PM2.5\", \"state\": {} } } },\n  \"services\": { \"set_target_value\": { \"name\": \"…\", \"description\": \"…\", \"fields\": {} } },\n  \"exceptions\": { \"set_target_value_failed\": { \"message\": \"…\" } },\n  \"issues\": { \"deprecated_api_endpoint\": { \"title\": \"…\", \"description\": \"…\" } },\n  \"selector\": { \"mode\": { \"options\": { \"auto\": \"Automatic\" }, \"unit_of_measurement\": \"seconds\" } },\n  \"config_subentries\": { \"device\": { \"step\": { \"user\": { \"data\": {} } } } },\n  \"device\": { \"gateway\": { \"name\": \"…\" } },\n  \"system_health\": { \"info\": { \"api_endpoint\": \"…\" } }\n}\n```\n\n`config` also takes `flow_title`, `progress` and `create_entry` alongside `step`. Subentry strings live under\n`config_subentries.\u003Ctype>`, never under `config`.\n\n## Which keys does my change need?\n\n| You added…                         | Keys required                                                                                   |\n| ---------------------------------- | ----------------------------------------------------------------------------------------------- |\n| An entity with a `translation_key` | `entity.\u003Cplatform>.\u003Ctranslation_key>.name`                                                      |\n| An enum sensor or a `select`       | …plus `entity.\u003Cplatform>.\u003Ckey>.state.\u003Cvalue>` for **every** possible value                      |\n| An entity attribute                | `entity.\u003Cplatform>.\u003Ckey>.state_attributes.\u003Cattr>.name` (and `.state` for enum attributes)       |\n| A config flow field                | `config.step.\u003Cstep>.data.\u003Cfield>` **and** `config.step.\u003Cstep>.data_description.\u003Cfield>`         |\n| A new `errors[\"base\"] = \"x\"`       | `config.error.x`                                                                                |\n| A new `async_abort(reason=\"x\")`    | `config.abort.x`                                                                                |\n| An options flow field              | `options.step.init.data.\u003Cfield>` and `options.step.init.data_description.\u003Cfield>`               |\n| A service action                   | `services.\u003Caction>.name`, `.description`, `.fields.\u003Cfield>.name`, `.fields.\u003Cfield>.description` |\n| A raised `HomeAssistantError`      | `exceptions.\u003Ctranslation_key>.message`                                                          |\n| A repair issue                     | `issues.\u003Cissue_id>.title`, plus **either** `.description` **or** `.fix_flow.*` — never both     |\n| A config subentry flow             | `config_subentries.\u003Ctype>.step.\u003Cstep>.…`, mirroring the `config` shape                          |\n| A config subentry type             | …plus `config_subentries.\u003Ctype>.entry_type` and `.initiate_flow.user` (both required)           |\n| A form section                     | `step.\u003Cstep>.sections.\u003Csection>.name` and `.description`; its fields in the section's `data`    |\n| A menu step                        | `step.\u003Cstep>.menu_options.\u003Coption>`                                                             |\n| A custom submit button label       | `step.\u003Cstep>.submit`                                                                            |\n| A unit that is a word (\"steps\")    | `entity.\u003Cplatform>.\u003Ckey>.unit_of_measurement` — and **no** `native_unit_of_measurement`         |\n| A trigger or condition             | `triggers.\u003Cid>` \u002F `conditions.\u003Cid>`: `.name`, `.description`, `.fields.\u003Cfield>.name`            |\n| A `system_health` value            | `system_health.info.\u003Ckey>`                                                                      |\n\nA repair issue may also carry an optional `short_title`. How to name triggers and conditions:\n[`triggers-conditions.md`](..\u002Fha-service-action\u002Freferences\u002Ftriggers-conditions.md).\n\nTwo rules that catch most mistakes:\n\n- **`name` vs. `data`.** Entity names live under `entity.*.name`; form field labels live under `step.*.data.*`. They are\n  not interchangeable.\n- **`data_description` is not optional in practice.** It is the small helper text under a field, and its absence is what\n  makes a setup form feel unfinished.\n\n## Abort reasons Home Assistant translates itself\n\nThese carry their own text, so they need no `config.abort` key — but only when Home Assistant raises them. A flow that\ncalls `async_abort(reason=…)` with one of them itself passes `translation_domain=\"homeassistant\"` or keeps its own key.\n\n| Reason                                        | Raised by                                                                               |\n| --------------------------------------------- | --------------------------------------------------------------------------------------- |\n| `reauth_successful`, `reconfigure_successful` | `async_update_reload_and_abort()` \u002F `async_update_and_abort()` when `reason` is omitted |\n| `already_in_progress`                         | `async_set_unique_id()`                                                                 |\n| `single_instance_allowed`                     | the `single_config_entry` manifest check                                                |\n| `no_devices_found`                            | the `DiscoveryFlowHandler` helper in `config_entry_flow`                                |\n\n`AbstractOAuth2FlowHandler` adds `authorize_url_timeout`, `missing_credentials`, `no_url_available`, `oauth_error`,\n`oauth_failed`, `oauth_implementation_unavailable`, `oauth_timeout`, `oauth_unauthorized` and\n`user_rejected_authorize` — for any `async_abort` on it without a `translation_domain`, including your own.\n\n`already_configured` is not one of them — it needs a key. Neither is the OAuth2 handler's `missing_configuration`.\n\n## Raising a translated exception\n\nThe pattern that ties Python to the JSON — every `{placeholder}` in the string must be supplied at the call site, and\nvice versa (hassfest checks both):\n\n```json\n{ \"exceptions\": { \"set_target_value_failed\": { \"message\": \"Could not set the value: {error}\" } } }\n```\n\n```python\nraise HomeAssistantError(\n    translation_domain=DOMAIN,\n    translation_key=\"set_target_value_failed\",\n    translation_placeholders={\"error\": str(err)},\n)\n```\n\n## Writing the strings\n\n- The style rules — sentence case, \"you\", the glossary's terms and the retired names to avoid — are in the\n  [instructions file](..\u002F..\u002Finstructions\u002Fblueprint.translations.instructions.md#ui-text-style). Proper nouns and capitalised abbreviations keep their casing.\n- **Keys** are `snake_case` — including translated state values and state attributes. Only the values are prose.\n- No trailing period on `name` and `data` labels; full sentences with a period for `description` and `data_description`.\n- Do not repeat the device or integration name in an entity name — `_attr_has_entity_name = True` means Home Assistant\n  prefixes it already. \"Temperature\", not \"Blueprint device temperature\".\n- Error messages say what happened and what to do, and never leak credentials, tokens, or raw stack traces.\n- Match the wording Home Assistant uses for the same situation rather than inventing a variant —\n  [Core's shared strings](..\u002F..\u002Finstructions\u002Fblueprint.translations.instructions.md#cores-shared-strings).\n- Use the word the project already settled on. If `docs\u002Fdevelopment\u002FGLOSSARY.md` exists it decides the wording here,\n  because renaming an entity later is a breaking change ([`ha-grill`](..\u002Fha-grill\u002FSKILL.md) is where those terms are\n  agreed).\n\n## icons.json\n\nEntity icons belong in `custom_components\u002F\u003Cdomain>\u002Ficons.json`, not in `EntityDescription(icon=...)`.\n\n**Do not give an entity an icon its device class already provides.** A PM2.5 sensor, a temperature sensor, a battery\nsensor are all iconed correctly by Home Assistant; overriding them makes the integration look inconsistent with every\nother one. Add an icon where there is no device class, or where the context genuinely differs from it.\n\nBeyond a plain icon, a key can carry:\n\n- `range` — pick by value: `{\"0\": \"mdi:battery-outline\", \"10\": \"mdi:battery-10\", …}`, ascending, and the icon chosen\n  is the highest bound less than or equal to the current value. `default` covers unavailable or unparseable states.\n  If a key defines both `state` and `range`, **`state` wins**.\n- `state_attributes` — icons per attribute value, for things like a climate preset or a fan mode. Only attributes,\n  not arbitrary keys.\n\n```json\n{\n  \"entity\": {\n    \"sensor\": {\n      \"pm25\": { \"default\": \"mdi:air-filter\" },\n      \"mode\": { \"default\": \"mdi:cog\", \"state\": { \"auto\": \"mdi:autorenew\", \"off\": \"mdi:power-off\" } }\n    }\n  },\n  \"services\": {\n    \"set_target_value\": { \"service\": \"mdi:target\" }\n  }\n}\n```\n\nNote the nesting: a service icon is `{\"service\": \"mdi:…\"}`, not a bare string. Sections get their own icons under\n`\"sections\"`.\n\nPrefer a `device_class` over an icon whenever one fits — device classes give correct icons, unit conversion, and\nassistant behaviour for free.\n\n## Validate\n\n```bash\nscript\u002Fhassfest        # the authoritative check: missing keys, unused keys, bad placeholders\nscript\u002Flint            # Prettier formats the JSON (2 spaces, no trailing commas)\n```\n\nThen restart Home Assistant and look at the actual UI — hassfest verifies structure, not whether the text reads well.\n\n## Do not\n\n- Do not add keys \"for later\" — hassfest flags unused keys.\n- Do not reformat the whole file while adding one key; keep the diff small and the ordering as it is.\n- Do not translate `key` values, entity IDs, or anything that ends up in an automation.\n\nThe remaining rules are in\n[`blueprint.translations.instructions.md`](..\u002F..\u002Finstructions\u002Fblueprint.translations.instructions.md).\n","# Translations and icons\n\n`translations\u002Fen.json` is the source of truth for every string a user sees. Home Assistant falls back to the raw key\nwhen a string is missing, so a missing key is a visible bug, not a cosmetic one.\n\n**Read [`blueprint.translations.instructions.md`](..\u002F..\u002Finstructions\u002Fblueprint.translations.instructions.md)\nfirst** — it holds the rules: placeholder syntax and the single-quote trap that breaks hassfest, why `[%key:…%]` and\n`strings.json` must never appear here, what hassfest rejects in a string, entity translation requirements, which fields\naccept Markdown, proper nouns, the form of address per language, cross-language structure, and the UI text style.\nThis skill is which keys a given change needs, and how to write them.\n\n## The project rule on languages\n\n- Update **`en.json` only**. Never edit or create other language files on your own initiative — translations are\n  contributed through the project's translation workflow, and machine-translating them creates churn no maintainer\n  asked for.\n- If the developer explicitly asks for another language, confirm which files before starting.\n- During feature work, business logic comes first. Use the translation key in code immediately, and fill in `en.json`\n  either when asked or when the feature is complete.\n\n## Key structure\n\n```jsonc\n{\n  \"config\": {\n    \"step\": {\n      \"user\": {\n        \"title\": \"…\",\n        \"description\": \"…\",\n        \"data\": { \"host\": \"Host\" },\n        \"data_description\": { \"host\": \"The hostname or IP address of the device.\" }\n      }\n    },\n    \"error\": { \"cannot_connect\": \"…\", \"invalid_auth\": \"…\", \"unknown\": \"…\" },\n    \"abort\": { \"already_configured\": \"…\" }\n  },\n  \"options\": { \"step\": { \"init\": { \"data\": {}, \"data_description\": {} } } },\n  \"entity\": { \"sensor\": { \"pm25\": { \"name\": \"PM2.5\", \"state\": {} } } },\n  \"services\": { \"set_target_value\": { \"name\": \"…\", \"description\": \"…\", \"fields\": {} } },\n  \"exceptions\": { \"set_target_value_failed\": { \"message\": \"…\" } },\n  \"issues\": { \"deprecated_api_endpoint\": { \"title\": \"…\", \"description\": \"…\" } },\n  \"selector\": { \"mode\": { \"options\": { \"auto\": \"Automatic\" }, \"unit_of_measurement\": \"seconds\" } },\n  \"config_subentries\": { \"device\": { \"step\": { \"user\": { \"data\": {} } } } },\n  \"device\": { \"gateway\": { \"name\": \"…\" } },\n  \"system_health\": { \"info\": { \"api_endpoint\": \"…\" } }\n}\n```\n\n`config` also takes `flow_title`, `progress` and `create_entry` alongside `step`. Subentry strings live under\n`config_subentries.\u003Ctype>`, never under `config`.\n\n## Which keys does my change need?\n\n| You added…                         | Keys required                                                                                   |\n| ---------------------------------- | ----------------------------------------------------------------------------------------------- |\n| An entity with a `translation_key` | `entity.\u003Cplatform>.\u003Ctranslation_key>.name`                                                      |\n| An enum sensor or a `select`       | …plus `entity.\u003Cplatform>.\u003Ckey>.state.\u003Cvalue>` for **every** possible value                      |\n| An entity attribute                | `entity.\u003Cplatform>.\u003Ckey>.state_attributes.\u003Cattr>.name` (and `.state` for enum attributes)       |\n| A config flow field                | `config.step.\u003Cstep>.data.\u003Cfield>` **and** `config.step.\u003Cstep>.data_description.\u003Cfield>`         |\n| A new `errors[\"base\"] = \"x\"`       | `config.error.x`                                                                                |\n| A new `async_abort(reason=\"x\")`    | `config.abort.x`                                                                                |\n| An options flow field              | `options.step.init.data.\u003Cfield>` and `options.step.init.data_description.\u003Cfield>`               |\n| A service action                   | `services.\u003Caction>.name`, `.description`, `.fields.\u003Cfield>.name`, `.fields.\u003Cfield>.description` |\n| A raised `HomeAssistantError`      | `exceptions.\u003Ctranslation_key>.message`                                                          |\n| A repair issue                     | `issues.\u003Cissue_id>.title`, plus **either** `.description` **or** `.fix_flow.*` — never both     |\n| A config subentry flow             | `config_subentries.\u003Ctype>.step.\u003Cstep>.…`, mirroring the `config` shape                          |\n| A config subentry type             | …plus `config_subentries.\u003Ctype>.entry_type` and `.initiate_flow.user` (both required)           |\n| A form section                     | `step.\u003Cstep>.sections.\u003Csection>.name` and `.description`; its fields in the section's `data`    |\n| A menu step                        | `step.\u003Cstep>.menu_options.\u003Coption>`                                                             |\n| A custom submit button label       | `step.\u003Cstep>.submit`                                                                            |\n| A unit that is a word (\"steps\")    | `entity.\u003Cplatform>.\u003Ckey>.unit_of_measurement` — and **no** `native_unit_of_measurement`         |\n| A trigger or condition             | `triggers.\u003Cid>` \u002F `conditions.\u003Cid>`: `.name`, `.description`, `.fields.\u003Cfield>.name`            |\n| A `system_health` value            | `system_health.info.\u003Ckey>`                                                                      |\n\nA repair issue may also carry an optional `short_title`. How to name triggers and conditions:\n[`triggers-conditions.md`](..\u002Fha-service-action\u002Freferences\u002Ftriggers-conditions.md).\n\nTwo rules that catch most mistakes:\n\n- **`name` vs. `data`.** Entity names live under `entity.*.name`; form field labels live under `step.*.data.*`. They are\n  not interchangeable.\n- **`data_description` is not optional in practice.** It is the small helper text under a field, and its absence is what\n  makes a setup form feel unfinished.\n\n## Abort reasons Home Assistant translates itself\n\nThese carry their own text, so they need no `config.abort` key — but only when Home Assistant raises them. A flow that\ncalls `async_abort(reason=…)` with one of them itself passes `translation_domain=\"homeassistant\"` or keeps its own key.\n\n| Reason                                        | Raised by                                                                               |\n| --------------------------------------------- | --------------------------------------------------------------------------------------- |\n| `reauth_successful`, `reconfigure_successful` | `async_update_reload_and_abort()` \u002F `async_update_and_abort()` when `reason` is omitted |\n| `already_in_progress`                         | `async_set_unique_id()`                                                                 |\n| `single_instance_allowed`                     | the `single_config_entry` manifest check                                                |\n| `no_devices_found`                            | the `DiscoveryFlowHandler` helper in `config_entry_flow`                                |\n\n`AbstractOAuth2FlowHandler` adds `authorize_url_timeout`, `missing_credentials`, `no_url_available`, `oauth_error`,\n`oauth_failed`, `oauth_implementation_unavailable`, `oauth_timeout`, `oauth_unauthorized` and\n`user_rejected_authorize` — for any `async_abort` on it without a `translation_domain`, including your own.\n\n`already_configured` is not one of them — it needs a key. Neither is the OAuth2 handler's `missing_configuration`.\n\n## Raising a translated exception\n\nThe pattern that ties Python to the JSON — every `{placeholder}` in the string must be supplied at the call site, and\nvice versa (hassfest checks both):\n\n```json\n{ \"exceptions\": { \"set_target_value_failed\": { \"message\": \"Could not set the value: {error}\" } } }\n```\n\n```python\nraise HomeAssistantError(\n    translation_domain=DOMAIN,\n    translation_key=\"set_target_value_failed\",\n    translation_placeholders={\"error\": str(err)},\n)\n```\n\n## Writing the strings\n\n- The style rules — sentence case, \"you\", the glossary's terms and the retired names to avoid — are in the\n  [instructions file](..\u002F..\u002Finstructions\u002Fblueprint.translations.instructions.md#ui-text-style). Proper nouns and capitalised abbreviations keep their casing.\n- **Keys** are `snake_case` — including translated state values and state attributes. Only the values are prose.\n- No trailing period on `name` and `data` labels; full sentences with a period for `description` and `data_description`.\n- Do not repeat the device or integration name in an entity name — `_attr_has_entity_name = True` means Home Assistant\n  prefixes it already. \"Temperature\", not \"Blueprint device temperature\".\n- Error messages say what happened and what to do, and never leak credentials, tokens, or raw stack traces.\n- Match the wording Home Assistant uses for the same situation rather than inventing a variant —\n  [Core's shared strings](..\u002F..\u002Finstructions\u002Fblueprint.translations.instructions.md#cores-shared-strings).\n- Use the word the project already settled on. If `docs\u002Fdevelopment\u002FGLOSSARY.md` exists it decides the wording here,\n  because renaming an entity later is a breaking change ([`ha-grill`](..\u002Fha-grill\u002FSKILL.md) is where those terms are\n  agreed).\n\n## icons.json\n\nEntity icons belong in `custom_components\u002F\u003Cdomain>\u002Ficons.json`, not in `EntityDescription(icon=...)`.\n\n**Do not give an entity an icon its device class already provides.** A PM2.5 sensor, a temperature sensor, a battery\nsensor are all iconed correctly by Home Assistant; overriding them makes the integration look inconsistent with every\nother one. Add an icon where there is no device class, or where the context genuinely differs from it.\n\nBeyond a plain icon, a key can carry:\n\n- `range` — pick by value: `{\"0\": \"mdi:battery-outline\", \"10\": \"mdi:battery-10\", …}`, ascending, and the icon chosen\n  is the highest bound less than or equal to the current value. `default` covers unavailable or unparseable states.\n  If a key defines both `state` and `range`, **`state` wins**.\n- `state_attributes` — icons per attribute value, for things like a climate preset or a fan mode. Only attributes,\n  not arbitrary keys.\n\n```json\n{\n  \"entity\": {\n    \"sensor\": {\n      \"pm25\": { \"default\": \"mdi:air-filter\" },\n      \"mode\": { \"default\": \"mdi:cog\", \"state\": { \"auto\": \"mdi:autorenew\", \"off\": \"mdi:power-off\" } }\n    }\n  },\n  \"services\": {\n    \"set_target_value\": { \"service\": \"mdi:target\" }\n  }\n}\n```\n\nNote the nesting: a service icon is `{\"service\": \"mdi:…\"}`, not a bare string. Sections get their own icons under\n`\"sections\"`.\n\nPrefer a `device_class` over an icon whenever one fits — device classes give correct icons, unit conversion, and\nassistant behaviour for free.\n\n## Validate\n\n```bash\nscript\u002Fhassfest        # the authoritative check: missing keys, unused keys, bad placeholders\nscript\u002Flint            # Prettier formats the JSON (2 spaces, no trailing commas)\n```\n\nThen restart Home Assistant and look at the actual UI — hassfest verifies structure, not whether the text reads well.\n\n## Do not\n\n- Do not add keys \"for later\" — hassfest flags unused keys.\n- Do not reformat the whole file while adding one key; keep the diff small and the ordering as it is.\n- Do not translate `key` values, entity IDs, or anything that ends up in an automation.\n\nThe remaining rules are in\n[`blueprint.translations.instructions.md`](..\u002F..\u002Finstructions\u002Fblueprint.translations.instructions.md).\n",{"name":5,"description":7},"main","3a408474735fec0ac5d62b86fc842420a899e090",".agents\u002Fskills\u002Fha-translations","https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia","https:\u002F\u002Fgithub.com\u002Famg0","2026-11-15 01:01:02",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add amg0\u002Fha_ksenia --skill ha-translations",{"tool":35,"command":36},"bunx","bunx skills add amg0\u002Fha_ksenia --skill ha-translations",{"tool":38,"command":39},"pnpm","pnpm dlx skills add amg0\u002Fha_ksenia --skill ha-translations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-translations\u002FSKILL.md",true,[],[44,51,58,65,72,79],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M7AB5RYA92GRR64CP6VMWV6Z","issues","Triage\u002Ffix the GitHub issue backlog via branch + PR, with auto-merge on green CI for this session.","https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fissues\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M7AB56JBRMF19W4N2NG9Y5GW","ha-testing","Write, fix, or extend automated tests for this Home Assistant custom integration using pytest and pytest-homeassistant-custom-component. Use when asked to \"add tests\", \"write a test\", \"the tests fail\", \"improve coverage\", \"add a regression test\", \"test the config flow\", \"update snapshots\", or when a behavioural change needs verification before it can be called done. Covers the tests\u002F layout, the conftest.py fixtures this project needs, mocking the API client, config flow and entity test patterns, registry assertions, syrupy snapshots, freezing time, and the script\u002Ftest commands. SYMPTOMS — load this if you are about to: instantiate an entity class directly instead of asserting on `hass.states`; write a test without `enable_custom_integrations`; use `time.sleep` instead of `async_fire_time_changed`; silence a DeprecationWarning to make the suite pass; or commit a snapshot you have not read.","https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-testing\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7AB4V9XKDYRDCRHEA68GRZ5","ha-service-action","Add, change, or remove a Home Assistant service action (also called a \"service\" or \"action\") in this custom integration. Use when asked to \"add a service\", \"add an action\", \"expose X as a service call\", \"add a service that returns data\", \"make this callable from an automation\", or when editing services.yaml, the service_actions\u002F package, service schemas, service response data, or the async_setup() registration. Covers the services.yaml contract, probatio schemas, selectors, entity\u002Fdevice targeting, response data, translated error messages, and the Bronze quality-scale rule that actions must be registered in async_setup(). SYMPTOMS — load this if you are about to: register an action in `async_setup_entry()`; add a `services.yaml` field without a selector; add an `entity_id` field where `target:` belongs; raise a plain English `HomeAssistantError`; or swallow an action failure into a log line.","https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-service-action\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7AB4J65REZ9T9VS9MQH73CC","ha-release","Cut a release of this Home Assistant custom integration, or prepare the commits that feed it. Use when asked to \"release\", \"cut a version\", \"bump the version\", \"prepare release notes\", \"what will the next version be\", \"write a commit message\", \"why didn't release-please pick this up\", or when reviewing whether a change is user-facing. Covers the Conventional Commits rules commitlint enforces here, how release-please derives the version and changelog, the pre-1.0 bump rules, script\u002Fversion and script\u002Frelease-notes, skipping a commit from the notes, and the commit rules this project enforces for agents. SYMPTOMS — load this if you are about to: commit without an explicit request; offer to `git push`; label a user-facing fix as `chore` (chore, like every hidden type, never reaches the changelog and never triggers a release); write a commit subject over 100 characters or in sentence case; or edit the version in `manifest.json` by hand.","https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-release\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7AB48WMPGDK2REBC3WS8T32","ha-quality-review","Perform a structured quality review of this Home Assistant custom integration, either as a full audit or scoped to a diff. Use when asked to \"review the integration\", \"audit the code\", \"check quality scale\", \"are we bronze\u002Fsilver\u002Fgold\", \"is this ready to release\", \"review my changes\", \"what's missing before publishing\", or before opening a pull request that touches integration code. Covers running the automated gates first, then auditing architecture, the Integration Quality Scale rules, error handling, security, performance, user experience, and documentation — and reporting findings ranked by severity with concrete fixes. SYMPTOMS — load this if you are about to: report a review that only restates linter output; claim real-device testing that did not happen; give a finding without a file path and a fix; or judge quality without running `script\u002Fhassfest` and the test suite first.","https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-quality-review\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7AB3Z99XZ5PN9Z59PJG52BW","ha-planning","Plan a large change to this Home Assistant custom integration before writing code, or record an architectural decision. Use when asked to \"create a plan\", \"plan this feature\", \"how should we approach\", \"propose an architecture\", \"write an ADR\", \"document this decision\", \"should we use library X or write our own client\", or whenever a change would touch more than about ten files or alter the integration's structure. Covers when a plan is mandatory, the phased plan format, where plans live, when a decision is worth recording, and the DECISIONS.md entry format used by this project. SYMPTOMS — load this if you are about to: start a refactor spanning more than ten files without confirmation; write a plan whose phases name no files; write one in prose nobody will finish reading; create a planning markdown file outside `.agents\u002Fscratch\u002F`; or make a hard-to-reverse architectural choice without recording why.","https:\u002F\u002Fgithub.com\u002Famg0\u002Fha_ksenia\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fha-planning\u002FSKILL.md",[],[]]