fft canvas dynamic ops
- Repo stars 0
- Author repo nano-core
- Domain
- AI
- 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
- Plug-and-play
- 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
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# FFT Canvas Dynamic Ops
Use this skill for runtime multi-card canvas composition and deterministic staged dashboard patch operations.
## When to use this skill
- Use when the user asks for dynamic Agent Canvas card creation/editing.
- Use when the user asks to patch dashboard views/cards without replacing the whole file.
- Use when updating card layout order, card content, or canvas spec metadata.
## When not to use this skill
- Do not use for direct live dashboard edits outside the staging/apply flow.
- Do not use for non-dashboard farm control requests.
- Do not use outside main/admin chat for write operations.
## Guardrails
- Never run destructive git commands unless explicitly requested.
- Preserve unrelated worktree changes.
- Main/admin chat only for privileged write actions.
- Keep all writes inside `/workspace/dashboard/`.
- Validate before apply; do not auto-apply to live dashboards.
## Action Surface
Use these actions for dynamic dashboard/canvas work:
- `ha_dashboard_get`
- `ha_dashboard_validate`
- `ha_dashboard_patch`
- `ha_apply_dashboard`
- `ha_capture_screenshot`
- `ha_canvas_get_spec`
- `ha_canvas_set_spec`
- `ha_canvas_patch_spec`
## Workflow
1. Read current state with `ha_dashboard_get` or `ha_canvas_get_spec`.
2. Build minimal patch operations.
3. Run validation (`ha_dashboard_validate`) before apply.
4. Apply staged dashboard only when requested (`ha_apply_dashboard`).
5. Verify with screenshot (`ha_capture_screenshot`).
## References
- Spec: `references/canvas-spec.md`
- Patch patterns: `references/operation-recipes.md`
- Safety checklist: `references/safety.md`
Sections and files
Listed in source order.
sections -> When to use this skill → When not to use this skill → Guardrails → Action Surface → Workflow → References
terms -> Use this skill for runtime multi-card canvas composition and deterministic staged dashboard patch operations. · - Use when the user asks for dynamic Agent Canvas card creation/editing. · - Do not use for direct live dashboard edits outside the staging/apply flow. · - Never run destructive git commands unless explicitly requested. · 1. Read current state with hadashboardget or hacanvasgetspec.
files/cmd -> /workspace/dashboard/ · ha_dashboard_get · ha_dashboard_validate · ha_dashboard_patch · ha_apply_dashboard · ha_capture_screenshot · ha_canvas_get_spec · ha_canvas_set_spec
body sha256 -> f4e3bcce9923
When to use this skill
Use when the user asks for dynamic Agent Canvas card creation/editing. Use when the user asks to patch dashboard views/cards without replacing the whole file. Use when updating card layout order, card content, or canvas spec metadata.
When not to use this skill
Do not use for direct live dashboard edits outside the staging/apply flow. Do not use for non-dashboard farm control requests. Do not use outside main/admin chat for write operations.
Guardrails
Never run destructive git commands unless explicitly requested. Preserve unrelated worktree changes. Main/admin chat only for privileged write actions. Keep all writes inside
/workspace/dashboard/. Validate before apply; do not auto-apply to live dashboards.Action Surface
Use these actions for dynamic dashboard/canvas work:
ha_dashboard_getha_dashboard_validateha_dashboard_patchha_apply_dashboardWorkflow
Read current state with
ha_dashboard_getorha_canvas_get_spec. Build minimal patch operations. Run validation (ha_dashboard_validate) before apply. Apply staged dashboard only when requested (ha_apply_dashboard). Verify with screenshot (ha_capture_screenshot).