lovelace-design

Included with Lifetime

$97 forever

Advanced Lovelace dashboard patterns for Home Assistant.

Design

What this skill does


# Lovelace Dashboard Design Skill

Advanced Lovelace dashboard patterns for Home Assistant.

## Activation Triggers

- Working with `ui-lovelace.yaml`
- Creating dashboard views
- Custom card configurations
- Theme development
- Responsive layouts

## Core Patterns

### Dashboard Structure

```yaml
# ui-lovelace.yaml structure
title: Home
views:
  - title: Overview
    path: overview
    icon: mdi:home
    badges: []
    cards: []

  - title: Rooms
    path: rooms
    icon: mdi:floor-plan
    panel: false
    cards: []

  - title: Settings
    path: settings
    icon: mdi:cog
    subview: true
    back_path: /lovelace/overview
    cards: []
```

### Card Types Reference

| Card | Use Case |
|------|----------|
| `entities` | List of entities |
| `glance` | Quick status view |
| `button` | Single action |
| `light` | Light control |
| `thermostat` | Climate control |
| `weather-forecast` | Weather display |
| `picture-glance` | Camera/image |
| `gauge` | Sensor display |
| `grid` | Card layout |
| `horizontal-stack` | Horizontal layout |
| `vertical-stack` | Vertical layout |

### Layout Cards

```yaml
# Grid layout
type: grid
columns: 3
square: false
cards:
  - type: entity
    entity: sensor.temp

# Horizontal stack
type: horizontal-stack
cards:
  - type: button
    entity: light.living

# Vertical stack
type: vertical-stack
cards:
  - type: entities
    entities: []
```

### Conditional Cards

```yaml
type: conditional
conditions:
  - condition: state
    entity: person.owner
    state: home
  - condition: numeric_state
    entity: sensor.temperature
    above: 70
card:
  type: entities
  entities:
    - climate.thermostat
```

### Custom Card Patterns

```yaml
# Mushroom card
type: custom:mushroom-entity-card
entity: light.living_room
icon_color: amber
fill_container: true
layout: horizontal

# Button card
type: custom:button-card
entity: light.living_room
name: Living Room
icon: mdi:lightbulb
color: auto
tap_action:
  action: toggle
styles:
  card:
    - border-radius: 20px

# Mini graph card
type: custom:mini-graph-card
entities:
  - sensor.temperature
hours_to_show: 24
points_per_hour: 2
show:
  labels: true
```

## Theme Variables

### Key CSS Variables

```yaml
# Colors
primary-color: "#03a9f4"
accent-color: "#ff9800"
primary-background-color: "#ffffff"
secondary-background-color: "#f5f5f5"
primary-text-color: "#212121"
secondary-text-color: "#727272"

# Cards
ha-card-background: "#ffffff"
ha-card-border-radius: "8px"
ha-card-box-shadow: "0 2px 4px rgba(0,0,0,0.1)"

# States
state-icon-active-color: "#ffc107"
state-icon-color: "#9e9e9e"
```

### Card-Mod Styling

```yaml
card_mod:
  style: |
    ha-card {
      background: transparent;
      box-shadow: none;
      border: 1px solid var(--divider-color);
    }
    .card-header {
      font-weight: bold;
      color: var(--primary-color);
    }
```

## Responsive Design

### Device Detection

```yaml
# Browser_mod popup
type: custom:state-switch
entity: browser_mod.browser_id
default: desktop
states:
  mobile:
    type: vertical-stack
    cards: []
  desktop:
    type: grid
    columns: 4
    cards: []
```

### View Visibility

```yaml
views:
  - title: Mobile Home
    path: mobile
    visible:
      - user: phone_user
    cards: []

  - title: Desktop Home
    path: desktop
    visible:
      - user: all
    cards: []
```

## HACS Card Dependencies

### Essential Cards
- `custom:button-card`
- `custom:mushroom-*`
- `custom:mini-graph-card`
- `custom:card-mod`
- `custom:layout-card`
- `custom:auto-entities`

### Installation
```bash
# Via HACS UI
1. Open HACS
2. Go to Frontend
3. Search for card name
4. Install and restart
```

## Best Practices

1. **Mobile First** - Design for smallest screen first
2. **Consistent Spacing** - Use grid for alignment
3. **Color Coding** - Use colors meaningfully
4. **Performance** - Limit cards per view
5. **Navigation** - Clear path structure

Files: 1

Size: 3.9 KB

Complexity: 6/100

Category: Design

Source: https://github.com/markus41/claude/tree/main/plugins/home-assistant-architect/skills/lovelace-design

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts