roder

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.

Runs and extends the Gode/Roder Rust workspace using mise, lld, Cargo incremental builds, and Makefile test targets. Use when adding crates or dependencies, running Rust tests, building roder-cli, or configuring local Rust tooling in this repo.

Configure and live-reload Roder from pasted config snippets, especially MCP server JSON, without leaking secrets or enabling executable integrations without approval.

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.

Alias for $roder-design-mode. Use when the user asks to generate, edit, inspect, export, or orchestrate Roder Desktop Design Canvas work.

Use when the user asks to generate, modify, review, export, import, or orchestrate agent work in Roder Desktop Design Mode / Design Canvas. Guides agents through using the Pencil-like design canvas features, design/* tools, prompt nodes, scoped agents, tokens, components, templates, screenshots, and SVG handoffs.

Drive the user's logged-in Chrome through the Roder browser extension to inspect tabs, read DOM/console/network, and interact with pages.

Create scoped VCS snapshots from the current workspace state.

Create a scoped version-control snapshot.

Drive a local Playwright browser through a Roder-owned Webwright workspace with plan, final script, screenshots, logs, and verification evidence.

Review code changes.

Maintain detailed API-integrator-level documentation for the Roder app-server API. Use when creating, updating, auditing, or reviewing docs for roder-app-server endpoints, JSON-RPC methods, session/thread APIs, provider/model APIs, auth/config behavior, streaming events, error shapes, or client integration guidance under docs/app-server/.

Use when changing Roder Rust features, tools, sessions, permissions, MCP support, CLI entrypoints, model/config behavior, app-server behavior, or docs in ways that could affect the Agent Client Protocol implementation, advertised ACP capabilities, or ACP client compatibility.

Keep Roder/gode TUI visuals readable, compact, and consistent. Use when changing roder-tui timeline, transcript, composer, tool rows, dialogs, footer/status, phase messages, or terminal colors.

Use when an agent needs to run the local roder TUI in tmux, send text or keys into the session, inspect panes, and capture pane output as timestamped .txt and .png artifacts.

Architecture, event-loop, and rendering patterns for ratatui TUIs. Use when building or extending `roder-tui` or any other Rust ratatui application — adding components, popups, async event handling, layout, focus, or message passing.

Use when running or fixing Rust clippy checks in the Gode workspace, including cargo clippy warnings, automatic fixes, and follow-up Rust tests.

Use when creating, updating, validating, or executing delegable roadmap plans under a repo's roadmap directory, especially for Gode feature phases and document-first planning workflows.