Skip to content
Skills Library
Programming · Building & coding

ha-integration-dev

/ha-integration-dev

Develops Home Assistant custom integrations in Python around a device or cloud API client: manifest, config flow, DataUpdateCoordinator, quality scale, pytest tests and HACS publishing. Use for "custom integration", "custom component", "HACS integration", "config flow".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Develops Home Assistant custom integrations in Python around a device or cloud API client: manifest, config flow, DataUpdateCoordinator, quality scale, pytest tests and HACS publishing. Use for "custom integration", "custom component", "HACS integration", "config flow".

Triggers from the description

custom integrationcustom componentHACS integrationconfig flow
Original author description

Develops Home Assistant custom integrations in Python around a device or cloud API client: manifest, config flow, DataUpdateCoordinator, quality scale, pytest tests and HACS publishing. Use for "custom integration", "custom component", "HACS integration", "config flow".

How it works

  1. Layout
  2. Rules
  3. Quality scale
  4. Tests
  5. Publish (HACS)
Original SKILL.md headings · 40 lines, 431 words
SKILL.md preview
---
name: ha-integration-dev
version: 1.0.0
description: 'Develops Home Assistant custom integrations in Python around a device or cloud API client: manifest, config flow, DataUpdateCoordinator, quality scale, pytest tests and HACS publishing. Use for "custom integration", "custom component", "HACS integration", "config flow".'
metadata:
  category: engineering
---

# HA Integration Development

Builds a custom integration the way Home Assistant core builds its own. Developer docs moved to contributors.home-assistant.io; read the current page before using an API you are unsure of. Write a failing test first for every behaviour and bug fix, then the code; get an independent review (another agent or a person) before release.

## Layout

```text
custom_components/<domain>/
  __init__.py        # async_setup_entry / async_unload_entry
  manifest.json
  config_flow.py
  coordinator.py
  sensor.py ...      # one module per platform
  strings.json, translations/en.json
tests/               # pytest-homeassistant-custom-component
```

## Rules

1. **manifest.json** for custom integrations needs `domain`, `name`, `version`, `codeowners`, `documentation`, `iot_class`; add `issue_tracker`, `integration_type`, `config_flow: true` and pinned `requirements` (exact versions of a published library that does the device protocol; no protocol code in the integration).
2. **Config flow** only (no YAML setup for new integrations): `async_step_user`; `await self.async_set_unique_id(<stable device or account ID>)` then `self._abort_if_unique_id_configured()`. Never an IP address or host name as unique ID. Discovery steps confirm with the user before creating an entry; support `reauth` and `reconfigure`.
3. **Data fetching** through one `DataUpdateCoordinator` per config entry: pass `config_entry`, set a sensible `update_interval` (do not poll faster than the device or API allows), raise `UpdateFailed` on errors, call `await coordinator.async_config_entry_first_refresh()` in setup, and store it as `entry.runtime_data` with a typed alias `type MyConfigEntry = ConfigEntry[MyCoordinator]`.
4. **Entities:** `CoordinatorEntity`, `_attr_has_entity_name = True`, stable `unique_id`, `device_info`, translated names, correct `device_class`, `state_class` and units; mark diagnostic and config entities with `entity_category`.
5. **Async only:** no blocking I/O in the event loop; use the library's async client or `hass.async_add_executor_job`.
6. **Secrets:** credentials live in the config entry, never in logs (redact them in diagnostics with `async_redact_data`).

## Quality scale

Home Assistant's integration quality scale (Bronze, Silver, Gold, Platinum) is a good checklist for custom integrations too: Bronze covers config flow, unique IDs, tests of the config flow and documented setup; Silver adds high test coverage, error handling and reauthentication; Gold adds diagnostics, discovery and translations; Platinum strict typing and async dependencies. Track it in `quality_scale.yaml` and mark each rule `done`, `todo` or `exempt` with a reason; never claim a rule is met without checking it.

## Tests

- `pytest-homeassistant-custom-component` provides the `hass` fixture and `MockConfigEntry`; mock the device library at its boundary, never a real device or cloud account.
- Test the config flow (success, cannot connect, invalid auth, already configured), setup and unload, coordinator failure (`UpdateFailed` → entities unavailable) and each platform's states.

## Publish (HACS)

One integration per repository under `custom_components/<domain>/`, a `hacs.json`, brand icon, GitHub releases with the version in `manifest.json`; the README documents setup through the UI and the data the integration sends anywhere.
Files in this package (2)
  • SKILL.md 4 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named ha-integration-dev.

Database snapshot: 13.11.2026 · package version 0cb9331c2d7f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100marketplace-integration
    Create, build and review Home Assistant custom integrations published through the Home Assistant Marketplace (formerly HACS), and prepare them for the Marketplace catalog (the hacs/default repository, also known as the HACS default store). Use when the user wants to scaffold a…
  • 100ha-hacs
    HACS metadata requirements for a Home Assistant integration — hacs.json, manifest.json fields, and repository structure. Use when preparing or validating HACS metadata files.
  • 100ha-documentation
    Generate documentation for Home Assistant integrations. Creates README.md, Home Assistant docs pages, and HACS info pages. Use when asked about documentation, README, docs, or making documentation for an integration.
  • 100custom-integration-sources
    Use a local copy of the latest code of every HACS default custom integration to measure how a core change (deprecation, removal, rename, signature change) affects custom integrations. Use when the user asks which or how many custom integrations use something, wants to check…
  • 90hacs
    Use when browsing, installing, version-pinning or downgrading, redownloading, or removing HACS packages, adding custom HACS repositories, or migrating to a custom integration through HA NOVA Relay.
  • 100ha-lovelace-taste
    Build Home Assistant Lovelace custom cards, card editors, badges, card features, dialogs and other frontend components that look and behave like native Home Assistant UI, built on its design system tokens (colors, fonts, radii, spacing), its card API (setConfig, hass,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.