design-canvas
Use when inspecting, editing, reviewing, exporting, or orchestrating agents on Roder Desktop Design Canvas `~/.roder/design/<project-slug>-<project-id>.roderdesign` documents. Covers the Pencil-like design workflow and required design/* tool order.
- License 许可
- MIT
- 所属仓库
- RoderAI/roder
- 最近更新
- 2026-11-13
- Stars
- ★ 9
- Forks
- 1
01 前言 Front Matter
- name
- design-canvas
- version
- 1.0.0
- description
- Use when inspecting, editing, reviewing, exporting, or orchestrating agents on Roder Desktop Design Canvas `~/.roder/design/<project-slug>-<project-id>.roderdesign` documents. Covers the Pencil-like design workflow and required design/* tool order.
03 SKILL.md 正文
Design Canvas
Use this skill whenever work touches Roder Desktop's structured Design Canvas or a ~/.roder/design/<project-slug>-<project-id>.roderdesign file.
Core Rules
- Treat
.roderdesignas a structured design document, not as arbitrary JSON to hand-edit. - Inspect before mutating:
- Start with
design/get_editor_statewhen available. - Use one combined
design/batch_getfor nodes, parent context, patterns, and read depth. - Use
design/get_variablesbefore changing tokens.
- Start with
- Mutate only through typed
design/patchoperations:insert_nodeupdate_nodedelete_nodereorder_nodeset_variablesFor token-only edits, prefer the dedicateddesign/set_variablesapp-server method ordesign_set_variablestool when available.- In agent tool calls, the tool is
design_patchand its top-level argument is exactly{ "operations": [...] }. Do not pass a top-levelpatch;patchis only a field inside anupdate_nodeoperation.
- After structural edits, run
design/snapshot_layoutand fix obvious layout diagnostics. - Use
design/export_nodesfor visual output and composer attachments; do not invent export paths. - For scoped multi-agent work, use
design/spawn_agentswith frame/group/component/instance scope node ids. - Respect agent permissions and review requirements when a prompt or manifest includes them.
Design Workflow
inspect editor state -> batch read relevant scopes -> plan typed patch operations -> patch -> snapshot layout -> export/attach if useful
Prefer one high-quality batched read over many tiny reads. Keep patches small, reversible, and explainable.
Node Semantics
- Valid container scopes include
frame,group,component, andinstance. - Preserve unknown imported Pencil data under source metadata instead of dropping it.
- Preserve reusable component identity and instance override metadata when duplicating or exporting.
- For prompt nodes, include node bounds, selected context, parent/container context, tokens, and permission rules in the request.
Desktop UI Expectations
When reviewing or changing the Design Canvas panel, preserve these Pencil-like workflows:
- floating tool rail with shortcuts,
- layers, search, lock/visibility, grouping, arrange, and child layer controls,
- inspector tokens/components/templates/libraries/import/export/history/diagnostics,
- prompt nodes and scoped agent launch plans,
- mini-map, rulers, fit-to-selection/canvas, and on-canvas quick actions,
- attach/review selected SVG and attach all root frames to composer.
Validation
For desktop TypeScript/UI changes, run the repository's focused formatter, lint, and TypeScript checks for touched files. For app-server/tool changes, run focused Cargo tests for the design module or method being changed.
Node aliases
design/get_editor_state, design/batch_get, design_read, and design_batch_get expose nodeAliases such as n1, n2, and n3. Use these short aliases when reasoning and when calling design tools; the app-server/tools resolve aliases to canonical node ids for reads, patches, exports, screenshots, selections, and scoped-agent plans. Mention both alias and name when explaining changes to the user.
04 同仓库更多 Skills
repo-tour
Use when a user asks for an orientation tour of an unfamiliar repository. Produces a structured tour of entry points, key modules, and how to run tests.
review
Review code changes.
vcs-snapshot
Create a scoped version-control snapshot.
webwright
Drive a local Playwright browser through a Roder-owned Webwright workspace with plan, final script, screenshots, logs, and verification evidence.
vcs-snapshot
Create scoped VCS snapshots from the current workspace state.
roder-config
Configure and live-reload Roder from pasted config snippets, especially MCP server JSON, without leaking secrets or enabling executable integrations without approval.