fft dashboard ops
- Repo stars 3
- Author repo FFT_nano
- Domain
- Engineering
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @0-CYBERDYNE-SYSTEMS-0 · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# 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; hand off to `fft-canvas-dynamic-ops`.
## 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, use `fft-canvas-dynamic-ops`.
- 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.
Sections and files
Listed in source order.
sections -> When to use this skill → When not to use this skill → Guardrails → Template Sources → Lovelace Structure Rules → Workflow
terms -> Use this skill for generating, staging, applying, and validating farm dashboards. · - Use when creating or revising Home Assistant Lovelace dashboards. · - Do not use for direct live YAML edits in Home Assistant config. · - Never run destructive git commands unless explicitly requested. · Use templates as a baseline, then adapt entity references using live discovery from /workspace/farm-state/devices.json. · - Top-level structure should include title and views. · 1. Read /workspace/farm-state/current.json and /workspace/farm-state/calendar.json for context. · - If the user asks for runtime canvas cards, card-level canvas edits, or spec-driven layout updates, use fft-canvas-dynamic-ops.
files/cmd -> fft-canvas-dynamic-ops · /workspace/dashboard-templates/ · /workspace/dashboard/ · /workspace/farm-state/devices.json · title · views · path · cards
body sha256 -> 80c5670ecf7b
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; hand off to
fft-canvas-dynamic-ops.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 definetitle, optionalpath, andcards. Use supported custom cards when available:custom:mushroom-*custom:apexcharts-card