How do I install the Ha Frontend UX Readiness skill?

Run npx skillmds@latest add home-assistant/ha-frontend-ux-readiness in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ha Frontend UX Readiness safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ha Frontend UX Readiness?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ha Frontend UX Readiness free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ha Frontend UX Readiness?

home-assistant (@home-assistant) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ha Frontend UX Readiness by home-assistant

Name: Ha Frontend UX Readiness
Author: home-assistant

Ha Frontend UX Readiness

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 and for fixes or technical details that preserve an established experience.

File contents

HA Frontend UI/UX Readiness

Use the design context and evidence gathered through ha-frontend-review to decide whether a change's UI/UX direction is settled and whether further UI/UX review should be recommended or is explicitly required. This skill routes the result; it does not repeat or replace implementation, accessibility, or frontend quality review.

Early Exit

If the PR already carries the Needs UX label, reviewers have already decided to ask designers or UX reviewers for guidance. Do not use this skill to make that recommendation again.

Triage

Apply ha-frontend-review and record its UI/UX evidence.
- Include the applicable gallery specification, production or approved designs, shared ha-* components, task requirements, historical feedback, and direct instructions.
- Keep the implementation review separate from this readiness decision.
Classify the user-facing decision.
- Existing-feature fixes and technical details normally remain with frontend review when they preserve the established experience.
- New cards, badges, screens, and interaction patterns normally need this readiness check.
Decide whether the evidence gathered during frontend review settles the direction.
- Frontend maintainer guidance, explicit UI/UX approval, current guidance, an established pattern, or a task that settles the material visual and interaction choices can settle the direction.
- Insufficient or conflicting evidence leaves the direction unresolved.
Select exactly one route below and state which frontend-review evidence supports it.

Routes

Frontend review sufficient: The change preserves the established experience, or the evidence settles the material visual and interaction choices. Cite that evidence and continue with ha-frontend-review.
UI/UX review recommended: A new user experience has material design choices that remain unresolved. Identify the decision that needs input and recommend UI/UX review.
UI/UX review required: A workflow rule or direct human instruction explicitly requires UI/UX review. Cite that evidence. A new design, task link, or lack of evidence is not enough on its own.

Frontend maintainer guidance, explicit UI/UX approval, established patterns, and task requirements inform the route. A task can settle requirements without settling the UI/UX. Recommend UI/UX review when important design choices remain unresolved.

Reporting

Keep the result concise and use this structure:

Route: Frontend review sufficient, UI/UX review recommended, or UI/UX review required
Established patterns: relevant gallery specifications, production designs, and shared ha-* components for the next reviewer to compare
Supporting evidence: approval, guidance, established patterns, task requirements, direct instructions, or the evidence gap or conflict
Next action: the review action implied by the route

Separate whether the UI/UX direction is settled from whether the implementation is correct.

---name: ha-frontend-ux-readinessdescription: 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 and for fixes or technical details that preserve an established experience.---# HA Frontend UI/UX ReadinessUse the design context and evidence gathered through `ha-frontend-review` to decide whether a change's UI/UX direction is settled and whether further UI/UX review should be recommended or is explicitly required. This skill routes the result; it does not repeat or replace implementation, accessibility, or frontend quality review.## Early ExitIf the PR already carries the **Needs UX** label, reviewers have already decided to ask designers or UX reviewers for guidance. Do not use this skill to make that recommendation again.## Triage1. Apply `ha-frontend-review` and record its UI/UX evidence. - Include the applicable gallery specification, production or approved designs, shared `ha-*` components, task requirements, historical feedback, and direct instructions. - Keep the implementation review separate from this readiness decision.2. Classify the user-facing decision. - Existing-feature fixes and technical details normally remain with frontend review when they preserve the established experience. - New cards, badges, screens, and interaction patterns normally need this readiness check.3. Decide whether the evidence gathered during frontend review settles the direction. - Frontend maintainer guidance, explicit UI/UX approval, current guidance, an established pattern, or a task that settles the material visual and interaction choices can settle the direction. - Insufficient or conflicting evidence leaves the direction unresolved.4. Select exactly one route below and state which frontend-review evidence supports it.## Routes- **Frontend review sufficient:** The change preserves the established experience, or the evidence settles the material visual and interaction choices. Cite that evidence and continue with `ha-frontend-review`.- **UI/UX review recommended:** A new user experience has material design choices that remain unresolved. Identify the decision that needs input and recommend UI/UX review.- **UI/UX review required:** A workflow rule or direct human instruction explicitly requires UI/UX review. Cite that evidence. A new design, task link, or lack of evidence is not enough on its own.Frontend maintainer guidance, explicit UI/UX approval, established patterns, and task requirements inform the route. A task can settle requirements without settling the UI/UX. Recommend UI/UX review when important design choices remain unresolved.## ReportingKeep the result concise and use this structure:- **Route:** Frontend review sufficient, UI/UX review recommended, or UI/UX review required- **Established patterns:** relevant gallery specifications, production designs, and shared `ha-*` components for the next reviewer to compare- **Supporting evidence:** approval, guidance, established patterns, task requirements, direct instructions, or the evidence gap or conflict- **Next action:** the review action implied by the routeSeparate whether the UI/UX direction is settled from whether the implementation is correct.

Frequently asked questions