fft-canvas-dynamic-ops
- Repo stars 0
- Author updated Live
- Author repo nano-core
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- 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 special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: fft-canvas-dynamic-ops
description: Compose and edit dynamic multi-card Agent Canvas specs and staged dashboard patches through allo…
category: ai
runtime: no special runtime
---
# fft-canvas-dynamic-ops output preview
## PART A: Task fit
- Use case: Compose and edit dynamic multi-card Agent Canvas specs and staged dashboard patches through allowlisted farm actions. Use when the user asks for dynamic Agent Canvas card creation/editing. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to use this skill / When not to use this skill / Guardrails” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Compose and edit dynamic multi-card Agent Canvas specs and staged dashboard patches through allowlisted farm actions. Use when the user asks for dynamic Agent Canvas card creation/editing. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “When to use this skill / When not to use this skill / Guardrails” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/workspace`; use them first when your agent supports command triggers.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “When to use this skill / When not to use this skill / Guardrails”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: fft-canvas-dynamic-ops
description: Compose and edit dynamic multi-card Agent Canvas specs and staged dashboard patches through allo…
category: ai
source: 0-CYBERDYNE-SYSTEMS-0/nano-core
---
# fft-canvas-dynamic-ops
## When to use
- Compose and edit dynamic multi-card Agent Canvas specs and staged dashboard patches through allowlisted farm actions.…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to use this skill / When not to use this skill / Guardrails” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "fft-canvas-dynamic-ops" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to use this skill / When not to use this skill / Guardrails
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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_getha_dashboard_validateha_dashboard_patchha_apply_dashboardha_capture_screenshotha_canvas_get_specha_canvas_set_specha_canvas_patch_spec
Workflow
- 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).
References
- Spec:
references/canvas-spec.md - Patch patterns:
references/operation-recipes.md - Safety checklist:
references/safety.md
Decide Fit First
Design Intent
How To Use It
Boundaries And Review