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.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-telegramSkill
- add-telegram-swarmSkill
- agent-browserSkill
- agent-harness-engineerSkill
- autoresearch-createSkill
- autoresearch-finalizeSkill
- fft-coder-opsSkill
- fft-debugSkill
- fft-farm-bootstrapSkill
- fft-farm-onboardingSkill
- fft-farm-opsSkill
- fft-host-ipcSkill
- fft-setupSkill
- fft-telegram-opsSkill
- loopsSkill
- rapid-researchSkill
- skill-mechanicSkill
- web-searchSkill
- customizeSkill
- debugSkill
- setupSkill
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
- Distinctive: line 8
Use this skill for generating, staging, applying, and validating farm dashboards.
- Distinctive: line 12
Use when creating or revising Home Assistant Lovelace dashboards.
- Distinctive: line 13
Use when applying dashboard changes through staged files and screenshot checks.
- Distinctive: line 14
Use when adapting dashboard layout to live farm-state context.
- Distinctive: line 18
Do not use for direct live YAML edits in Home Assistant config.
- Distinctive: line 19
Do not use for non-dashboard automation or device control requests.
- Distinctive: line 20
Do not use outside main/admin chat for dashboard apply operations.
- Very specific: line 21
Do not use for runtime multi-card canvas composition.
- Distinctive: line 25
Never run destructive git commands unless explicitly requested.
- Distinctive: line 28
Always use the staging file flow.
- Very specific: line 35
Use templates as a baseline, then adapt entity references using live discovery from /workspace/farm-state/devices.json.
- Distinctive: line 41
Use supported custom cards when available:
- Very specific: line 44
Prefer robust layouts (grid, vertical-stack, horizontal-stack) with clear labels.
- Very specific: line 48
Read /workspace/farm-state/current.json and /workspace/farm-state/calendar.json for context.
- Very specific: line 50
Use ha_dashboard_validate before apply.
- Distinctive: line 53
Verify screenshot and iterate until readable and operational.
- Distinctive: line 57
If the user asks for runtime canvas cards, card-level canvas edits, or spec-driven layout updates, explain that this skill only covers Home …
- Very specific: line 58
If the user asks for full view composition, theme/view structure changes, or staged apply lifecycle management, stay in fft-dashboard-ops.
- Very specific: line 62
Use current.json.context.suggestedTheme to choose theme variants (for example: dawn, midday, dusk, night, storm, frost, harvest).
- Distinctive: line 70
Never bypass staging-to-live apply flow.
- Distinctive: line 71
Never execute shell-level infrastructure changes from dashboard tasks.
- Distinctive: line 72
Keep entity IDs explicit and avoid wildcard assumptions.
≈ “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.
Files
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
titleandviews. - Each view should define
title, optionalpath, andcards. - Use supported custom cards when available:
custom:mushroom-*custom:apexcharts-card
- Prefer robust layouts (
grid,vertical-stack,horizontal-stack) with clear labels.
Workflow
- Read
/workspace/farm-state/current.jsonand/workspace/farm-state/calendar.jsonfor context. - Draft dashboard YAML to
/workspace/dashboard/ui-lovelace-staging.yaml. - Use
ha_dashboard_validatebefore apply. - Request apply via
ha_apply_dashboardwithstagingFileset to the staging path. - Request screenshot via
ha_capture_screenshotfor the relevant view. - 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.
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
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.

