home-assistant

Home Assistant frontend Lit context and hass migration guidance. Use when adding or changing component state access, replacing hass reads, consuming entity or registry contexts, or reviewing rerender behavior.

Home Assistant frontend URL query param patterns. Use when keeping page state such as filters, search, sorting or grouping in the URL, adding or reading typed query params, using QueryParamsController or the data table's sync-url and column urlName, building…

Home Assistant frontend PR and review guidance, including implementation quality, existing review feedback, established design patterns, and the authority of UI/UX evidence. Use when reviewing frontend changes, preparing a PR, checking recurring review…

Home Assistant standalone demo structure, configurations, URL navigation, mocked APIs, shared demo stubs used by gallery, and verification. Use when changing files under demo/, changing gallery consumers of demo/src/stubs/, or running and validating the demo.

Home Assistant frontend gallery structure, pages, demos, content, and verification. Use when changing files under gallery/, including gallery markdown, TypeScript demos, sidebar entries, mock data, page generation, or gallery builds.

Home Assistant frontend testing and validation workflow. Use when adding or updating tests, running lint, TypeScript checks, Vitest, Playwright e2e suites, dev servers, or chart-data benchmarks.

Home Assistant frontend UI/UX readiness routing for new cards, badges, screens, and interaction patterns. Use it with `ha-frontend-review` to decide whether frontend review is enough or further UI/UX input is needed. Skip it for PRs already carrying Needs UX…

Home Assistant frontend Lit conventions. Use when working with reactive properties, internal state, DOM queries, lifecycle methods, or render-derived state.

The end-to-end change workflow, TestFlight feature gating, companion documentation PRs, and CI gates. Use when preparing a change for commit or a PR, understanding the order of lint/autocorrect/test steps, gating a feature behind TestFlight with…

Unit and snapshot testing conventions. Use when writing tests, mocking dependencies by overriding Current, running the Tests-Unit scheme, or adding snapshot tests for new SwiftUI views.

Swift code style, linting, logging, assets, and idioms for Home Assistant iOS. Use when writing or formatting Swift, declaring an enum that is Codable, Decodable, Encodable, or decoded from HAData, running SwiftFormat/SwiftLint, referencing SF Symbols or…

Home Assistant iOS project layout, build setup, and the "World" dependency-injection pattern. Use when starting work in the repo, deciding where code lives across targets (App, Shared, Watch, CarPlay, Extensions), accessing dependencies through the global…

SwiftUI and UIKit UI conventions for Home Assistant iOS. Use when building views, choosing SwiftUI vs UIKit, bridging with embeddedInHostingController(), building reusable components in the HADesignSystem package, or following the one-struct-per-file,…

Asynchronous code and server networking conventions. Use when writing async/await, Tasks, actors, or Combine, deciding whether to touch PromiseKit, annotating view models with @MainActor, or calling the Home Assistant server via HAKit.

Localization via SwiftGen-generated L10n accessors and the en.lproj .strings files. Use when adding or changing user-facing strings, working with the L10n/CoreStrings/FrontendStrings tables, or dealing with Lokalise-managed translations.

The cross-platform MagicItem action model shared by Widgets, Watch, CarPlay, and App Shortcuts. Use when adding or changing item types or action overrides, or touching anything that persists MagicItem via Codable.

Home Assistant Android module and layer architecture. Use when adding features, choosing where code lives, writing repositories or use cases, setting up Hilt injection, storing data securely, or calling Home Assistant APIs.

Home Assistant Android Kotlin style. Use when declaring constants, modeling data or logic types, working with time or dates, choosing visibility, naming, or writing KDoc and comments.

Home Assistant Android UI guidance. Use when building or reviewing Compose screens, ViewModels, screen state, navigation, dialogs, widgets, or anything using HATheme and the design system.

Home Assistant Android testing guidance. Use when writing or reviewing unit tests, Robolectric tests, Flow tests with Turbine, screenshot tests, fakes from testing-unit, or module-wide test rules.

Home Assistant Android end-to-end (Maestro) failure triage. Use when the E2E workflow fails, when reading its artifacts (Maestro report, logcat, Home Assistant logs), or when deciding whether a failure comes from the app, from Home Assistant, or from…

Home Assistant Android change finalization. Use when finishing a change, preparing to commit, updating the changelog, naming a branch, or opening a pull request.

Home Assistant Android coroutine and threading guidance. Use when launching coroutines, choosing dispatchers, sharing mutable state across threads, exposing Flows, or reviewing for blocking calls and race conditions.

Home Assistant Android logging and error handling. Use when writing catch blocks, logging with Timber, handling exceptions or fallbacks, using FailFast, or reviewing for silent failures and leaked user data.

Use this to add or update a component page in the Design area of the Home Assistant contributors website, with specs from the frontend CSS and tokens, accessibility from the code, and live demos.

Use this to rebuild the live frontend component demos of the Home Assistant contributors website from a newer frontend, to add a component to the demos, or to fix the build when a frontend change breaks it.

Use this to add a term to the glossary of the Home Assistant contributors website, or to change one, including its autolink words and a check for wrong matches across the site.

Use this if the user wants to convert a blog post draft, such as a Google Docs Markdown export, into a blog post for the Home Assistant contributors website.

Use this to verify a page or a whole area of the Home Assistant contributors website against the source repositories, and to fix or remove what does not hold.

Use this to bring a change merged on developers.home-assistant.io over to the Home Assistant contributors website, while the old site still receives changes. Finds what changed, maps it to the page here, and ports it rewritten in this site's style, verified…

Use this to review a pull request, a set of pages, or site code of the Home Assistant contributors website in depth. Verifies claims against the source repositories, checks examples and steps, and reports findings with evidence and a severity.

Use this if the user wants to update the agent instructions for the Home Assistant contributors website, or sync the writing guidelines shared with home-assistant.io.

Everything you need to know to build, test and review Home Assistant Integrations. If you're looking at an integration, you must use this as your primary reference.

Verifies that a Home Assistant integration follows a specific quality scale rule, checking whether it implements the required patterns, configurations, or code structures defined by the quality scale system. Use when asked to check a rule (e.g. "check if the…

Reviews Home Assistant code changes and provides constructive feedback. Should be used when a review is requested to provide a consistent review behavior and output format. This skill can be used for code reviews in general, not just for GitHub pull requests.

Finds open Home Assistant pull requests that are genuinely ready to merge, checking CI, the merge-gate statuses, code-owner approval, merge conflicts, requested changes and unresolved review threads. Use when looking for PRs to merge, doing merge-queue…

Bumps a Python package dependency across Home Assistant Core integrations, regenerates core requirement files, runs verification tests and prek lint, and prepares a pull request with proper release/compare links.

Reviews Home Assistant GitHub pull requests and provides feedback comments. This is the top skill to use for reviewing Pull Requests from GitHub.

Audits the review comment threads on a Home Assistant GitHub pull request, flagging unaddressed comments and requests for clarification. Use when checking whether PR feedback has been handled, either standalone or as part of a full PR review.

Document Home Assistant integrations in the current split-page format.

Use this when writing or editing Home Assistant documentation, website pages, integration pages, blog prose, UI instructions, or other user-facing prose.

Use this if the user wants to update the agent instructions for the Home Assistant website.

Use this when editing Home Assistant Markdown, Liquid, internal links, images, videos, glossary terms, My links, text boxes, or other website syntax.

Use this whenever the user asks to create, port, remake, rebuild, or componentize any piece of the website UI for the Astro build (astro/src/components) — the header, footer, alert boxes, buttons, cards, navigation, or any other visual element — even if they…

Use this if the user wants to convert a blog post from Google Docs markdown to the format used in the Home Assistant website, or wants to publish an externally linked (crosspost) blog post that redirects to an article hosted on another site.

Use this when editing Home Assistant YAML examples, automation examples, script examples, service action calls, templates, or configuration snippets.

Rules for writing and reviewing companion app documentation pages in this repository, based on recurring pull request review feedback. Use when reviewing a pull request or when adding or changing pages under docs/.