homeassistant-dashboard-designer

Design and refactor Home Assistant Lovelace dashboards into constrained button-card-first YAML.

5.3k|503|Updated Oct 11, 2016
One-click install
npx skills add https://github.com/CCOSTAN/Home-AssistantConfig --skill homeassistant-dashboard-designer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: homeassistant-dashboard-designer
Source: https://github.com/CCOSTAN/Home-AssistantConfig/tree/main/codex_skills/homeassistant-dashboard-designer
Command: npx skills add https://github.com/CCOSTAN/Home-AssistantConfig --skill homeassistant-dashboard-designer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the creation and maintenance of Home Assistant Lovelace dashboards by enforcing a consistent, safe, and efficient design system, preventing common errors and ensuring maintainability.

Core Features & Use Cases

  • Constrained Design System: Enforces button-card-first structure, minimal card-mod, and strict layout rules for predictable dashboards.
  • Automated Refactoring: Safely updates and refactors existing dashboard YAML, ensuring adherence to design standards.
  • Use Case: Refactor a complex Home Assistant dashboard view to use the standardized button-card templates and grid layout, ensuring consistency across all your smart home interfaces.

Quick Start

Use the homeassistant-dashboard-designer skill to refactor the 'infrastructure' dashboard view.

Frequently Asked Questions about homeassistant-dashboard-designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I refactor Home Assistant Lovelace dashboard YAML safely?

Refactoring Home Assistant Lovelace dashboard YAML safely involves applying a constrained machine-safe design system that enforces button-card-first structure, strict layout rules, and centralized templates to ensure maintainability and prevent common configuration errors.

What is the best way to structure Home Assistant dashboard views for consistency?

The best way to structure Home Assistant dashboard views for consistency is using a button-card-first design system with minimal card-mod, strict layout grids, and centralized templates to translate design inspiration into safe Lovelace YAML.

Can I use button-card templates when updating existing Lovelace dashboards?

Yes, you can use button-card templates when updating existing Lovelace dashboards. The system safely refactors views and panels in `config/dashboards/**` paths to use standardized templates while applying config validation.

Why should I minimize card-mod in Home Assistant dashboard design?

Minimizing card-mod in Home Assistant dashboard design ensures a predictable and maintainable configuration. A constrained design system enforces minimal card-mod usage alongside strict layout rules to prevent complex, error-prone styling overrides.

Does Home Assistant dashboard refactoring require centralized templates?

Home Assistant dashboard refactoring requires centralized templates to enforce a consistent, machine-safe design system. This approach standardizes button-card structures and layout rules across all views, ensuring long-term maintainability.

How do I validate Lovelace YAML configuration when adding new dashboard panels?

Validating Lovelace YAML configuration when adding new dashboard panels is handled through automated config validation. This enforces strict layout rules and button-card-first structures to ensure safe, error-free updates.