agentleFS
0-CYBERDYNE-SYSTEMS-00-CYBERDYNE-SYSTEMS-0/FFT_nano/skills/runtime/fft-dashboard-ops/SKILL.md

fft-dashboard-ops

Skill4 starsChanged 8 months agoMITView on GitHub

Build and apply Home Assistant Lovelace dashboards from templates using a staged workflow with screenshot verification and context-reactive themes.

The file

Show its rules and text

We split this skill into the rules it gives an agent

22 rules. About 0 are common, 15 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for generating, staging, applying, and validating farm dashboards.

    line 8
  2. Distinctive:

    Use when creating or revising Home Assistant Lovelace dashboards.

    line 12
  3. Distinctive:

    Use when applying dashboard changes through staged files and screenshot checks.

    line 13
  4. Distinctive:

    Use when adapting dashboard layout to live farm-state context.

    line 14
  5. Distinctive:

    Do not use for direct live YAML edits in Home Assistant config.

    line 18
  6. Distinctive:

    Do not use for non-dashboard automation or device control requests.

    line 19
  7. Distinctive:

    Do not use outside main/admin chat for dashboard apply operations.

    line 20
  8. Very specific:

    Do not use for runtime multi-card canvas composition.

    line 21
  9. Distinctive:

    Never run destructive git commands unless explicitly requested.

    line 25
  10. Distinctive:

    Always use the staging file flow.

    line 28
  11. Very specific:

    Use templates as a baseline, then adapt entity references using live discovery from /workspace/farm-state/devices.json.

    line 35
  12. Distinctive:

    Use supported custom cards when available:

    line 41
  13. Very specific:

    Prefer robust layouts (grid, vertical-stack, horizontal-stack) with clear labels.

    line 44
  14. Very specific:

    Read /workspace/farm-state/current.json and /workspace/farm-state/calendar.json for context.

    line 48
  15. Very specific:

    Use ha_dashboard_validate before apply.

    line 50
  16. Distinctive:

    Verify screenshot and iterate until readable and operational.

    line 53
  17. Distinctive:

    If the user asks for runtime canvas cards, card-level canvas edits, or spec-driven layout updates, explain that this skill only covers Home …

    line 57
  18. Very specific:

    If the user asks for full view composition, theme/view structure changes, or staged apply lifecycle management, stay in fft-dashboard-ops.

    line 58
  19. Very specific:

    Use current.json.context.suggestedTheme to choose theme variants (for example: dawn, midday, dusk, night, storm, frost, harvest).

    line 62
  20. Distinctive:

    Never bypass staging-to-live apply flow.

    line 70
  21. Distinctive:

    Never execute shell-level infrastructure changes from dashboard tasks.

    line 71
  22. Distinctive:

    Keep entity IDs explicit and avoid wildcard assumptions.

    line 72

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

FFT Dashboard Ops

Use this skill for generating, staging, applying, and validating farm dashboards.

When to use this skill

  • Use when creating or revising Home Assistant Lovelace dashboards.
  • Use when applying dashboard changes through staged files and screenshot checks.
  • Use when adapting dashboard layout to live farm-state context.

When not to use this skill

  • Do not use for direct live YAML edits in Home Assistant config.
  • Do not use for non-dashboard automation or device control requests.
  • Do not use outside main/admin chat for dashboard apply operations.
  • Do not use for runtime multi-card canvas composition; that capability is not bundled with FFT_nano yet.

Guardrails

  • Never run destructive git commands unless explicitly requested.
  • Preserve unrelated worktree changes.
  • Dashboard apply operations are main/admin chat only.
  • Always use the staging file flow; never modify live YAML directly.

Template Sources

  • View/card/theme templates: /workspace/dashboard-templates/
  • Writable dashboard config mount: /workspace/dashboard/

Use templates as a baseline, then adapt entity references using live discovery from /workspace/farm-state/devices.json.

Lovelace Structure Rules

  • Top-level structure should include title and views.
  • Each view should define title, optional path, and cards.
  • Use supported custom cards when available:
    • custom:mushroom-*
    • custom:apexcharts-card
  • Prefer robust layouts (grid, vertical-stack, horizontal-stack) with clear labels.

Workflow

  1. Read /workspace/farm-state/current.json and /workspace/farm-state/calendar.json for context.
  2. Draft dashboard YAML to /workspace/dashboard/ui-lovelace-staging.yaml.
  3. Use ha_dashboard_validate before apply.
  4. Request apply via ha_apply_dashboard with stagingFile set to the staging path.
  5. Request screenshot via ha_capture_screenshot for the relevant view.
  6. Verify screenshot and iterate until readable and operational.

Skill Routing

  • If the user asks for runtime canvas cards, card-level canvas edits, or spec-driven layout updates, explain that this skill only covers Home Assistant Lovelace dashboard work.
  • If the user asks for full view composition, theme/view structure changes, or staged apply lifecycle management, stay in fft-dashboard-ops.

Context-Reactive Theming

Use current.json.context.suggestedTheme to choose theme variants (for example: dawn, midday, dusk, night, storm, frost, harvest).

  • High alert level: emphasize warnings/errors and simplify visual noise.
  • Normal operations: prioritize trend visibility and quick actions.
  • Calendar-heavy periods: feature timeline/task cards in primary views.

Safety Expectations

  • Never bypass staging-to-live apply flow.
  • Never execute shell-level infrastructure changes from dashboard tasks.
  • Keep entity IDs explicit and avoid wildcard assumptions.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.