Menu
Alias for $roder-design-mode. Use when the user asks to generate, edit, inspect, export, or orchestrate Roder Desktop Design Canvas work.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Draft release notes for Roder releases, new crates or packages, feature additions, behavior changes, and fixes. Use when writing release notes, changelog summaries, release announcements, or explaining what changed in a branch, PR, crate, SDK, or package release.
Use when editing TUI rendering code, adding new visible surfaces, or working on themes/CSS in Roder. Keeps class/id taxonomy, cascade order, and the supported CSS subset consistent across sessions.
Draft a changelog entry from the latest changes.
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.
Use when a PR changes any released package (crates/*, sdk/typescript, sdk/python, packages/edit-tools), when the changeset-gate CI check fails, when adding a new crate or package to the release config, or when working on knope versioning/release automation. For the step-by-step workflow to add a change file, use $create-changeset.
Use when a PR or branch changes any released package (crates/*, sdk/typescript, sdk/python, packages/edit-tools), when the changeset-gate CI check fails, or before pushing work that touches versioned package directories. Creates the required .changeset/*.md file for knope per-package versioning.
| name | design |
| description | Alias for $roder-design-mode. Use when the user asks to generate, edit, inspect, export, or orchestrate Roder Desktop Design Canvas work. |
This is a short alias for $roder-design-mode.
When this skill is invoked, immediately follow the full Roder Design Mode workflow:
design_get_editor_state or design_read.n1, n2, …) from tool results when referencing nodes.design_patch using a top-level operations array only; never use a top-level patch argument.design_set_variables for token-only changes.design_snapshot_layout and export/attach/review when requested.Do not inspect desktop implementation source unless the design tools are unavailable or the user asks for implementation work.