仪表板操作

工程开发 社区

技能解读

当前原文的自动摘译,尚未人工审校。

何时使用该技能

在创建或修改 Home Assistant Lovelace 仪表板时使用。通过暂存文件和屏幕截图检查应用仪表板更改时使用。在调整仪表板布局以适应实时农场状态时使用。

什么时候不应该使用这个技能

请勿在 Home Assistant 配置中用于直接实时 YAML 编辑。请勿用于非仪表板自动化或设备控制请求。不要使用外部主/管理聊天来进行仪表板应用操作。不要用于运行时多卡画布合成;移交给fft-canvas-dynamic-ops。

护栏

除非明确要求,否则切勿运行破坏性的 git 命令。保留不相关的工作树更改。仪表板应用操作仅限于主/管理聊天。始终使用暂存文件流;切勿直接修改实时 YAML。

模板来源

视图/卡片/主题模板:/workspace/dashboard-templates/ 可写仪表板配置安装:/workspace/dashboard/ 使用模板作为基线,然后使用/workspace/farm-state/devices.json的实时发现来调整实体引用。

洛夫莱斯结构规则

顶层结构应包括title和views。每个视图应该定义title、可选的path和cards。使用支持的自定义卡(如果可用): custom:mushroom-* custom:apexcharts-card

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
工程开发
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
88 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@0-CYBERDYNE-SYSTEMS-0 · 未声明许可证
上下文用量评级
低消耗
接入复杂程度
需简单配置
是否需要外部接口密钥
不需要
兼容的系统
未声明(默认跨平台)
运行环境要求
未检出明确要求
检测到的文件与系统行为
  • 只读
  • 允许写入 / 修改
  • 命令执行
网络行为
仅限本地
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

作者说明文件(原文) 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; 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.

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。