ha-integration-dev_skill

This skill helps you develop a Python Home Assistant custom integration using DataUpdateCoordinator patterns and secure async practices.
  • Python

21

GitHub Stars

6

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill tonylofgren/aurora-smart-home --skill ha-integration-dev

  • CHEATSHEET.md10.6 KB
  • INSTALLATION.md3.5 KB
  • PROMPT-IDEAS.md11.2 KB
  • README.md3.1 KB
  • SKILL.md15.5 KB
  • USAGE-GUIDE.md31.1 KB

Overview

This skill helps you design and generate Home Assistant custom integrations in Python, including config flows, DataUpdateCoordinator patterns, and HACS packaging. It is intended only when you explicitly request a custom integration, Python development, HACS support, or config_flow guidance. I will guide you through required architecture, security, and async best practices so the integration runs reliably inside Home Assistant.

How this skill works

I clarify the integration type (cloud vs local, polling vs push), authentication method, entity types, and whether you want HACS-ready files. Based on that, I select an appropriate template (polling, push, oauth, multi-device, etc.), generate Python files with the required docstring header, and provide a pre-completion checklist that enforces the Iron Law: timezone-safe timestamps, JSON-serializable attributes, and non-blocking async HTTP. I can output files for saving to custom_components/ or display code for copy-paste.

When to use it

  • You explicitly request a custom integration, custom component, or Python code for Home Assistant
  • You need config_flow (UI config entries), OAuth2, or DataUpdateCoordinator guidance
  • You want a HACS-ready repository or packaging advice for distribution
  • You require architecture patterns for multi-device hubs, websockets, or typed coordinators
  • You need secure integration design: HTTPS, input validation, redaction, and rate limiting

Best practices

  • Always use dt_util.now() or dt_util.utcnow() for timestamps; never datetime.now()
  • Return only JSON-serializable values in entity attributes; convert datetimes to ISO strings
  • Use aiohttp or async_get_clientsession() for HTTP and avoid blocking I/O in async code
  • Implement DataUpdateCoordinator for centralized polling, backoff, and error handling
  • Assign unique_id to entities so they are customizable and register DeviceInfo when applicable

Example use cases

  • Create a cloud API polling integration that exposes multiple sensors and a switch
  • Build a local websocket push integration that forwards events to entities in HA
  • Add an OAuth2 flow and HACS packaging for public distribution
  • Generate a multi-device hub integration with separate coordinators per device
  • Produce minimal starter files for manual installation to custom_components/

FAQ

No. Use the home-assistant skill for YAML automations and the node-red skill for Node-RED flows; this skill is only for Python custom integrations.

Can you make the integration HACS-ready?

Yes. If requested, I generate hacs.json, HACS-enhanced manifest.json, README, LICENSE, and GitHub Actions validate workflow.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational