[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PRWDFZMBGYPAZB9D567H2":3,"skill-same:01M75PRWDFZMBGYPAZB9D567H2":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M75PRWDFZMBGYPAZB9D567H2","design-canvas",null,"Use when inspecting, editing, reviewing, exporting, or orchestrating agents on Roder Desktop Design Canvas `~\u002F.roder\u002Fdesign\u002F\u003Cproject-slug>-\u003Cproject-id>.roderdesign` documents. Covers the Pencil-like design workflow and required design\u002F* tool order.","RoderAI\u002Froder","RoderAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F284978122?v=4","01M75PQQ8DXA6WMHGMZXS7CTP5","Roder","01M75PQQ91JEF84WMNZG8GQH8Q",9,"MIT","https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fdesign-canvas\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: design-canvas\ndescription: Use when inspecting, editing, reviewing, exporting, or orchestrating agents on Roder Desktop Design Canvas `~\u002F.roder\u002Fdesign\u002F\u003Cproject-slug>-\u003Cproject-id>.roderdesign` documents. Covers the Pencil-like design workflow and required design\u002F* tool order.\nversion: \"1.0.0\"\n---\n\n# Design Canvas\n\nUse this skill whenever work touches Roder Desktop's structured Design Canvas or a `~\u002F.roder\u002Fdesign\u002F\u003Cproject-slug>-\u003Cproject-id>.roderdesign` file.\n\n## Core Rules\n\n1. Treat `.roderdesign` as a structured design document, not as arbitrary JSON to hand-edit.\n2. Inspect before mutating:\n   - Start with `design\u002Fget_editor_state` when available.\n   - Use one combined `design\u002Fbatch_get` for nodes, parent context, patterns, and read depth.\n   - Use `design\u002Fget_variables` before changing tokens.\n3. Mutate only through typed `design\u002Fpatch` operations:\n   - `insert_node`\n   - `update_node`\n   - `delete_node`\n   - `reorder_node`\n   - `set_variables`\n     For token-only edits, prefer the dedicated `design\u002Fset_variables` app-server\n     method or `design_set_variables` tool when available.\n   - In agent tool calls, the tool is `design_patch` and its top-level argument\n     is exactly `{ \"operations\": [...] }`. Do **not** pass a top-level `patch`;\n     `patch` is only a field inside an `update_node` operation.\n4. After structural edits, run `design\u002Fsnapshot_layout` and fix obvious layout diagnostics.\n5. Use `design\u002Fexport_nodes` for visual output and composer attachments; do not invent export paths.\n6. For scoped multi-agent work, use `design\u002Fspawn_agents` with frame\u002Fgroup\u002Fcomponent\u002Finstance scope node ids.\n7. Respect agent permissions and review requirements when a prompt or manifest includes them.\n\n## Design Workflow\n\n```text\ninspect editor state -> batch read relevant scopes -> plan typed patch operations -> patch -> snapshot layout -> export\u002Fattach if useful\n```\n\nPrefer one high-quality batched read over many tiny reads. Keep patches small, reversible, and explainable.\n\n## Node Semantics\n\n- Valid container scopes include `frame`, `group`, `component`, and `instance`.\n- Preserve unknown imported Pencil data under source metadata instead of dropping it.\n- Preserve reusable component identity and instance override metadata when duplicating or exporting.\n- For prompt nodes, include node bounds, selected context, parent\u002Fcontainer context, tokens, and permission rules in the request.\n\n## Desktop UI Expectations\n\nWhen reviewing or changing the Design Canvas panel, preserve these Pencil-like workflows:\n\n- floating tool rail with shortcuts,\n- layers, search, lock\u002Fvisibility, grouping, arrange, and child layer controls,\n- inspector tokens\u002Fcomponents\u002Ftemplates\u002Flibraries\u002Fimport\u002Fexport\u002Fhistory\u002Fdiagnostics,\n- prompt nodes and scoped agent launch plans,\n- mini-map, rulers, fit-to-selection\u002Fcanvas, and on-canvas quick actions,\n- attach\u002Freview selected SVG and attach all root frames to composer.\n\n## Validation\n\nFor desktop TypeScript\u002FUI changes, run the repository's focused formatter, lint, and TypeScript checks for touched files. For app-server\u002Ftool changes, run focused Cargo tests for the design module or method being changed.\n\n## Node aliases\n\n`design\u002Fget_editor_state`, `design\u002Fbatch_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\u002Ftools 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.\n","# Design Canvas\n\nUse this skill whenever work touches Roder Desktop's structured Design Canvas or a `~\u002F.roder\u002Fdesign\u002F\u003Cproject-slug>-\u003Cproject-id>.roderdesign` file.\n\n## Core Rules\n\n1. Treat `.roderdesign` as a structured design document, not as arbitrary JSON to hand-edit.\n2. Inspect before mutating:\n   - Start with `design\u002Fget_editor_state` when available.\n   - Use one combined `design\u002Fbatch_get` for nodes, parent context, patterns, and read depth.\n   - Use `design\u002Fget_variables` before changing tokens.\n3. Mutate only through typed `design\u002Fpatch` operations:\n   - `insert_node`\n   - `update_node`\n   - `delete_node`\n   - `reorder_node`\n   - `set_variables`\n     For token-only edits, prefer the dedicated `design\u002Fset_variables` app-server\n     method or `design_set_variables` tool when available.\n   - In agent tool calls, the tool is `design_patch` and its top-level argument\n     is exactly `{ \"operations\": [...] }`. Do **not** pass a top-level `patch`;\n     `patch` is only a field inside an `update_node` operation.\n4. After structural edits, run `design\u002Fsnapshot_layout` and fix obvious layout diagnostics.\n5. Use `design\u002Fexport_nodes` for visual output and composer attachments; do not invent export paths.\n6. For scoped multi-agent work, use `design\u002Fspawn_agents` with frame\u002Fgroup\u002Fcomponent\u002Finstance scope node ids.\n7. Respect agent permissions and review requirements when a prompt or manifest includes them.\n\n## Design Workflow\n\n```text\ninspect editor state -> batch read relevant scopes -> plan typed patch operations -> patch -> snapshot layout -> export\u002Fattach if useful\n```\n\nPrefer one high-quality batched read over many tiny reads. Keep patches small, reversible, and explainable.\n\n## Node Semantics\n\n- Valid container scopes include `frame`, `group`, `component`, and `instance`.\n- Preserve unknown imported Pencil data under source metadata instead of dropping it.\n- Preserve reusable component identity and instance override metadata when duplicating or exporting.\n- For prompt nodes, include node bounds, selected context, parent\u002Fcontainer context, tokens, and permission rules in the request.\n\n## Desktop UI Expectations\n\nWhen reviewing or changing the Design Canvas panel, preserve these Pencil-like workflows:\n\n- floating tool rail with shortcuts,\n- layers, search, lock\u002Fvisibility, grouping, arrange, and child layer controls,\n- inspector tokens\u002Fcomponents\u002Ftemplates\u002Flibraries\u002Fimport\u002Fexport\u002Fhistory\u002Fdiagnostics,\n- prompt nodes and scoped agent launch plans,\n- mini-map, rulers, fit-to-selection\u002Fcanvas, and on-canvas quick actions,\n- attach\u002Freview selected SVG and attach all root frames to composer.\n\n## Validation\n\nFor desktop TypeScript\u002FUI changes, run the repository's focused formatter, lint, and TypeScript checks for touched files. For app-server\u002Ftool changes, run focused Cargo tests for the design module or method being changed.\n\n## Node aliases\n\n`design\u002Fget_editor_state`, `design\u002Fbatch_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\u002Ftools 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.\n",{"name":5,"version":24,"description":7},"1.0.0","master","cc8a773a0aeb90b9a2c6d9496045d0086befa159",".agents\u002Fskills\u002Fdesign-canvas",1,"https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder","https:\u002F\u002Froder.sh","https:\u002F\u002Fgithub.com\u002FRoderAI","roder.sh","Roder maintain the last model harness the world will need","2026-11-13 16:46:55",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add RoderAI\u002Froder --skill design-canvas",{"tool":41,"command":42},"bunx","bunx skills add RoderAI\u002Froder --skill design-canvas",{"tool":44,"command":45},"pnpm","pnpm dlx skills add RoderAI\u002Froder --skill design-canvas","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Fdesign-canvas\u002FSKILL.md",true,[],[50,57,64,71,78,84],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M75PV4G2KGTM7SWT2CH1V4AF","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.","https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002Fexamples\u002Fpackages\u002Fdemo-roder-package\u002Fskills\u002Frepo-tour\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M75PV378N4WSCDFRD1BCDAPS","review","Review code changes.","https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002Fcrates\u002Froder-skills\u002Ftests\u002Ffixtures\u002Fmodel\u002Fworkspace-review\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M75PV216EXMRD1ZXTWZ94CZD","vcs-snapshot","Create a scoped version-control snapshot.","https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002Fcrates\u002Froder-skills\u002Ftests\u002Ffixtures\u002Fmodel\u002Fbuiltin-vcs-snapshot\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M75PTW4RMS1K8FTKGSXBC895","webwright","Drive a local Playwright browser through a Roder-owned Webwright workspace with plan, final script, screenshots, logs, and verification evidence.","https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002Fcrates\u002Froder-skills\u002Fbuiltin\u002Fwebwright\u002FSKILL.md",[],[],{"skillNo":79,"name":66,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M75PTRBG4VZVNJY9D7C8J7RK","Create scoped VCS snapshots from the current workspace state.","https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002Fcrates\u002Froder-skills\u002Fbuiltin\u002Fvcs-snapshot\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M75PTNTG14BJ27N6S5QBVGNA","roder-config","Configure and live-reload Roder from pasted config snippets, especially MCP server JSON, without leaking secrets or enabling executable integrations without approval.","https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002Fcrates\u002Froder-skills\u002Fbuiltin\u002Froder-config\u002FSKILL.md",[],[]]