[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PSPP0NT7PV1Y2F0C68684":3,"skill-same:01M75PSPP0NT7PV1Y2F0C68684":48},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M75PSPP0NT7PV1Y2F0C68684","roder-theming",null,"Use when editing TUI rendering code, adding new visible surfaces, or working on themes\u002FCSS in Roder. Keeps class\u002Fid taxonomy, cascade order, and the supported CSS subset consistent across sessions.","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\u002Froder-theming\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: roder-theming\ndescription: Use when editing TUI rendering code, adding new visible surfaces, or working on themes\u002FCSS in Roder. Keeps class\u002Fid taxonomy, cascade order, and the supported CSS subset consistent across sessions.\n---\n\n# Roder TUI theming — alignment rules\n\nThe TUI styling pipeline is a small CSS engine (`roder-theme`) plus a thin TUI integration (`roder-tui\u002Fsrc\u002Ftheme\u002F`). The rules below keep every contributor — human or model — pointed at the same contract.\n\n## 1. Taxonomy: every visible surface registers a token\n\nSingle-instance surfaces use an **id**. Repeating surfaces use a **class** (or two: a base class plus a variant).\n\n- Naming: `kebab-case` for both, e.g. `#status-line`, `.timeline-tool`, `.tool-status-error`.\n- Variants use a `-variant` suffix on the base class: `.diff-line-add`, `.diff-line-del`.\n- Data attributes carry runtime state: `[data-status=\"error\"]`, `[data-mode=\"plan\"]`, `[data-tool=\"bash\"]`.\n- The closed list of supported ids\u002Fclasses is documented in the RFC (`rfc\u002F0001-tui-css-theming.md` §\"Class\u002FID Registry\") and enforced at the renderer call sites.\n- Hidable classes (those whose `display: none` is honored today) are in `crates\u002Froder-tui\u002Fsrc\u002Ftheme\u002Foverrides.rs` `HIDABLE_CLASSES`. Adding a new entry means teaching the renderer that owns it to consult the flag.\n\nWhen you introduce a new surface, register its token at the call site — do not invent one and forget to add it to the registry.\n\n## 2. Render through the engine, not through inline colors\n\nEvery span SHOULD eventually flow through `StyleMap::resolve(&node)` (or, for the v1 proof, `Theme::for_terminal_themed()` and the conventional `:root` variables in `crates\u002Froder-tui\u002Fsrc\u002Ftheme\u002Foverrides.rs::KNOWN_VARS`). Do not reach back to `Style::default().fg(some_hardcoded_color)` for new code.\n\nBefore \u002F after pattern (see `crates\u002Froder-tui\u002Fsrc\u002Fapp.rs` around line 1737 for current `theme.accent()` style):\n\n```rust\n\u002F\u002F Wrong — inline color, untheme-able:\nlet span = Span::styled(\" roder\", Style::default().fg(Color::Rgb(0xff, 0xaa, 0x00)));\n\n\u002F\u002F Right — pulls from the cascade via the Theme helpers:\nlet span = Span::styled(\" roder\", self.theme.accent());\n```\n\nThe Theme struct's helpers (`accent`, `error`, `tool`, ...) are the bridge between the engine and ratatui. New helpers should always derive their fg\u002Fbg from `Theme` fields that the cascade already patches.\n\n## 3. Cascade order (lowest → highest priority)\n\n1. **Built-in defaults** — `Theme::for_terminal()` (hard-coded baseline).\n2. **Extension contributions** — `ProvidedService::ThemeContribution` (RFC §Extension Contributors; not yet wired).\n3. **Active user theme** — first `.css` matched from `~\u002F.roder\u002Fthemes\u002F`, then `.roder\u002Fthemes\u002F`, then repo `themes\u002F` (later wins by basename dedup).\n4. **Overlays** — extra stylesheets in `[tui.theme].overlays` (not yet wired).\n5. **Inline** — `[tui.theme].inline` block (not yet wired).\n\nTie-break inside a layer is standard CSS specificity `(id, class+attr+pseudo, type)` then author order then `!important`.\n\n**Policy bypass is forbidden.** `display: none` on a permission dialog hides the *render* only; the canonical approval channel still fires (§15 of the whitepaper). Any new \"hide a thing\" mechanism must respect this — never gate a side effect on a render flag.\n\n## 4. Supported CSS subset (today, v1 proof)\n\nSource of truth: `crates\u002Froder-theme\u002Fsrc\u002Fparser.rs`, `crates\u002Froder-theme\u002Fsrc\u002Fproperties.rs`, `crates\u002Froder-theme\u002Fsrc\u002Fcascade.rs`.\n\n### Selectors that match\n- `#id`, `.class`, `[data-foo]`, `[data-foo=\"bar\"]`\n- Comma groups: `.a, .b { ... }`\n- Descendant combinator: `#a .b`\n- Child combinator: `#a > .b`\n- `:root { --var: value; }` for variables, `var(--name)` to reference\n- Specificity + `!important`\n\n### Properties that actually do something\n- `color`, `background-color`, `background` (alias for `background-color`)\n- `border-style` (`none`\u002F`solid`\u002F`plain`\u002F`single`\u002F`rounded`\u002F`double`\u002F`thick`), `border-radius` (integer; 0 = Plain, >0 = Rounded), `border` shorthand, `border-color`\n- `font-weight: normal | bold`\n- `font-style: normal | italic`\n- `text-decoration: none | underline | line-through`\n- `display: block | inline | none` (only `none` has a runtime effect today, and only on `HIDABLE_CLASSES`)\n- `padding` (1–4 cell-unit values)\n\n### Values\n- Colors: `#rgb`, `#rrggbb`, `rgb(r,g,b)`, `ansi(0..=255)`, named colors (small table — see `properties::named_color`), `reset`, `transparent` (alias of `reset` — only meaningful on a background)\n- Lengths: integer cells only\n\n### Terminal background (`:root` \u002F `#body`)\n\nA theme can paint the whole frame with one of three equivalent forms — all collapse to `ThemeOverrides::background` via `resolve_body_background` in `crates\u002Froder-tui\u002Fsrc\u002Ftheme\u002Foverrides.rs`:\n\n- `:root { background: \u003Ccolor>; }` — preferred shorthand.\n- `:root { --background: \u003Ccolor>; }` — variable form; composes with `var()`.\n- `#body { background-color: \u003Ccolor>; }` — \"DOM\" form. Wins over the `:root` forms.\n\n`transparent` \u002F `reset` resolve to `None`, which means *do not paint* (terminal native background bleeds through). That is the documented default — `themes\u002Fdefault.css` carries `:root { background: transparent; }` explicitly so the intent is visible. The renderer skips the fill widget entirely when `Theme::body_background` is `None`, so transparent terminals stay truly transparent.\n\n### Popup\u002Fdialog surface is always the body\n\n`Theme::apply_overrides` (in `crates\u002Froder-tui\u002Fsrc\u002Fapp.rs`) unconditionally sets `dialog_bg = body_background.unwrap_or(Color::Reset)` and `dialog_shadow = body_background.unwrap_or(Color::Reset)`. Themes **cannot** elevate the popup interior above the body — the design intent is that popups read as a framed cutout of the body, not as an elevated card. `--dialog-bg` and `--dialog-shadow` declarations in a stylesheet are deliberately ignored. Only `--dialog` (border color) and `--dialog-key-bg` (hotkey chips on confirm dialogs) are themable.\n\nIf you find yourself wanting popup elevation, push back on the design before adding it — the \"always flush with body\" rule fixed two separate visual artifacts (mismatched corners on dark themes, dark popup on light terminals).\n\n### Border shape (`:root` \u002F `#body`)\n\n`:root` \u002F `#body` declarations of `border-style`, `border-radius`, `border` shorthand, and `border-color` resolve via `resolve_border_shape` in `crates\u002Froder-tui\u002Fsrc\u002Ftheme\u002Foverrides.rs` into `ThemeOverrides::border_shape: Option\u003Croder_theme::BorderShape>`. `Theme::apply_overrides` maps that to:\n\n- `Theme::border_type: ratatui::widgets::BorderType` (default `Rounded`).\n- `Theme::borders_visible: bool` (false only for `border-style: none`).\n\nEvery framed widget reads both fields (`Block::default().borders(borders).border_type(theme.border_type)`). To add per-widget overrides later, the renderer must move from `theme.border_type` to `style_map.computed(node).border` — wire it through one widget at a time, don't try to refactor the whole TUI at once.\n\n### Parsed but inert (do not rely on these — they silently no-op)\n- `:hover`, `:focus`, `:selected`, `:first-child`, `:last-child`, `:nth-child`, `:not(...)` — the parser accepts them but matching is incomplete.\n- `margin`, `visibility`, `opacity`, `text-transform`, `white-space`, `::before` \u002F `::after`, `+` (adjacent sibling).\n- Anything not in the list above.\n\nIf you need one of these, **extend the parser and the cascade in lockstep** — don't ship a theme that depends on a property the engine drops.\n\n## 5. Adding a new theme\n\n1. Create `themes\u002F\u003Cname>.css`. Set every variable you want to differ from baseline (see `themes\u002Fdefault.css` for the full list).\n2. Target at least one class or id beyond `:root` so the cascade is exercised (e.g. `.error { color: ...; }` or `#status-line { ... }`).\n3. Register the basename in `crates\u002Froder-tui\u002Ftests\u002Ftheme_e2e.rs::ALL_THEMES`. The `all_checked_in_themes_parse` and `repo_themes_directory_has_ten_or_more_files` tests will fail if you forget.\n4. Add a one-line assertion test in the same file that proves the theme changes a specific color or hides a specific class.\n\nThe user-facing theme picker discovers any `*.css` under `~\u002F.roder\u002Fthemes\u002F`, `.roder\u002Fthemes\u002F`, or the repo `themes\u002F` directory; the basename becomes the picker id. Selection persists to `~\u002F.roder\u002Fstate.toml` (`[tui].active_theme`).\n\n## 6. What NOT to do\n\n- Don't add inline `Color::Rgb(...)` calls in renderers. Add a `Theme` field, patch it from a conventional `:root` variable (extend `KNOWN_VARS` if needed), and pull it through a `Theme` helper.\n- Don't introduce a new CSS property keyword without extending both `crates\u002Froder-theme\u002Fsrc\u002Fparser.rs` (lexer) and `crates\u002Froder-theme\u002Fsrc\u002Fcascade.rs::apply_declaration` (interpreter). A keyword without an interpreter is a silent footgun.\n- Don't ship a theme that depends on `:hover`, `border`, `margin`, `opacity`, or pseudo-elements — they are parsed-but-inert (see §4).\n- Don't gate any policy or approval behavior on a render flag like `Theme::hide_thinking`. Render flags are presentation only.\n- Don't add a `themes\u002F\u003Cname>.css` without also extending the `ALL_THEMES` test list.\n\n## 7. Pointers\n\n- RFC: `rfc\u002F0001-tui-css-theming.md`\n- Engine crate: `crates\u002Froder-theme\u002Fsrc\u002F{parser,cascade,properties,style_map,node,ast}.rs`\n- TUI integration: `crates\u002Froder-tui\u002Fsrc\u002Ftheme\u002F{mod,discovery,overrides,state,node_tree}.rs`\n- Theme baseline \u002F palette glue: `crates\u002Froder-tui\u002Fsrc\u002Fapp.rs` `impl Theme` (around lines 110–330)\n- Palette source: `crates\u002Froder-tui\u002Fsrc\u002Fpalette\u002Fsources.rs::theme_source` + `PaletteAction::SetTheme`\n- Tests: `crates\u002Froder-tui\u002Ftests\u002Ftheme_e2e.rs`, `crates\u002Froder-tui\u002Ftests\u002Ftheme_palette.rs`, `crates\u002Froder-theme\u002Fsrc\u002Fcascade.rs` (unit tests)\n- Bundled themes (10 today; `default`, `midnight`, `solarized`, `minimal`, `high-contrast`, `gruvbox`, `dracula`, `tokyo-night`, `light`, `focus`) live in `themes\u002F` — keep the on-disk set and `ALL_THEMES` in `tests\u002Ftheme_e2e.rs` in sync.\n","# Roder TUI theming — alignment rules\n\nThe TUI styling pipeline is a small CSS engine (`roder-theme`) plus a thin TUI integration (`roder-tui\u002Fsrc\u002Ftheme\u002F`). The rules below keep every contributor — human or model — pointed at the same contract.\n\n## 1. Taxonomy: every visible surface registers a token\n\nSingle-instance surfaces use an **id**. Repeating surfaces use a **class** (or two: a base class plus a variant).\n\n- Naming: `kebab-case` for both, e.g. `#status-line`, `.timeline-tool`, `.tool-status-error`.\n- Variants use a `-variant` suffix on the base class: `.diff-line-add`, `.diff-line-del`.\n- Data attributes carry runtime state: `[data-status=\"error\"]`, `[data-mode=\"plan\"]`, `[data-tool=\"bash\"]`.\n- The closed list of supported ids\u002Fclasses is documented in the RFC (`rfc\u002F0001-tui-css-theming.md` §\"Class\u002FID Registry\") and enforced at the renderer call sites.\n- Hidable classes (those whose `display: none` is honored today) are in `crates\u002Froder-tui\u002Fsrc\u002Ftheme\u002Foverrides.rs` `HIDABLE_CLASSES`. Adding a new entry means teaching the renderer that owns it to consult the flag.\n\nWhen you introduce a new surface, register its token at the call site — do not invent one and forget to add it to the registry.\n\n## 2. Render through the engine, not through inline colors\n\nEvery span SHOULD eventually flow through `StyleMap::resolve(&node)` (or, for the v1 proof, `Theme::for_terminal_themed()` and the conventional `:root` variables in `crates\u002Froder-tui\u002Fsrc\u002Ftheme\u002Foverrides.rs::KNOWN_VARS`). Do not reach back to `Style::default().fg(some_hardcoded_color)` for new code.\n\nBefore \u002F after pattern (see `crates\u002Froder-tui\u002Fsrc\u002Fapp.rs` around line 1737 for current `theme.accent()` style):\n\n```rust\n\u002F\u002F Wrong — inline color, untheme-able:\nlet span = Span::styled(\" roder\", Style::default().fg(Color::Rgb(0xff, 0xaa, 0x00)));\n\n\u002F\u002F Right — pulls from the cascade via the Theme helpers:\nlet span = Span::styled(\" roder\", self.theme.accent());\n```\n\nThe Theme struct's helpers (`accent`, `error`, `tool`, ...) are the bridge between the engine and ratatui. New helpers should always derive their fg\u002Fbg from `Theme` fields that the cascade already patches.\n\n## 3. Cascade order (lowest → highest priority)\n\n1. **Built-in defaults** — `Theme::for_terminal()` (hard-coded baseline).\n2. **Extension contributions** — `ProvidedService::ThemeContribution` (RFC §Extension Contributors; not yet wired).\n3. **Active user theme** — first `.css` matched from `~\u002F.roder\u002Fthemes\u002F`, then `.roder\u002Fthemes\u002F`, then repo `themes\u002F` (later wins by basename dedup).\n4. **Overlays** — extra stylesheets in `[tui.theme].overlays` (not yet wired).\n5. **Inline** — `[tui.theme].inline` block (not yet wired).\n\nTie-break inside a layer is standard CSS specificity `(id, class+attr+pseudo, type)` then author order then `!important`.\n\n**Policy bypass is forbidden.** `display: none` on a permission dialog hides the *render* only; the canonical approval channel still fires (§15 of the whitepaper). Any new \"hide a thing\" mechanism must respect this — never gate a side effect on a render flag.\n\n## 4. Supported CSS subset (today, v1 proof)\n\nSource of truth: `crates\u002Froder-theme\u002Fsrc\u002Fparser.rs`, `crates\u002Froder-theme\u002Fsrc\u002Fproperties.rs`, `crates\u002Froder-theme\u002Fsrc\u002Fcascade.rs`.\n\n### Selectors that match\n- `#id`, `.class`, `[data-foo]`, `[data-foo=\"bar\"]`\n- Comma groups: `.a, .b { ... }`\n- Descendant combinator: `#a .b`\n- Child combinator: `#a > .b`\n- `:root { --var: value; }` for variables, `var(--name)` to reference\n- Specificity + `!important`\n\n### Properties that actually do something\n- `color`, `background-color`, `background` (alias for `background-color`)\n- `border-style` (`none`\u002F`solid`\u002F`plain`\u002F`single`\u002F`rounded`\u002F`double`\u002F`thick`), `border-radius` (integer; 0 = Plain, >0 = Rounded), `border` shorthand, `border-color`\n- `font-weight: normal | bold`\n- `font-style: normal | italic`\n- `text-decoration: none | underline | line-through`\n- `display: block | inline | none` (only `none` has a runtime effect today, and only on `HIDABLE_CLASSES`)\n- `padding` (1–4 cell-unit values)\n\n### Values\n- Colors: `#rgb`, `#rrggbb`, `rgb(r,g,b)`, `ansi(0..=255)`, named colors (small table — see `properties::named_color`), `reset`, `transparent` (alias of `reset` — only meaningful on a background)\n- Lengths: integer cells only\n\n### Terminal background (`:root` \u002F `#body`)\n\nA theme can paint the whole frame with one of three equivalent forms — all collapse to `ThemeOverrides::background` via `resolve_body_background` in `crates\u002Froder-tui\u002Fsrc\u002Ftheme\u002Foverrides.rs`:\n\n- `:root { background: \u003Ccolor>; }` — preferred shorthand.\n- `:root { --background: \u003Ccolor>; }` — variable form; composes with `var()`.\n- `#body { background-color: \u003Ccolor>; }` — \"DOM\" form. Wins over the `:root` forms.\n\n`transparent` \u002F `reset` resolve to `None`, which means *do not paint* (terminal native background bleeds through). That is the documented default — `themes\u002Fdefault.css` carries `:root { background: transparent; }` explicitly so the intent is visible. The renderer skips the fill widget entirely when `Theme::body_background` is `None`, so transparent terminals stay truly transparent.\n\n### Popup\u002Fdialog surface is always the body\n\n`Theme::apply_overrides` (in `crates\u002Froder-tui\u002Fsrc\u002Fapp.rs`) unconditionally sets `dialog_bg = body_background.unwrap_or(Color::Reset)` and `dialog_shadow = body_background.unwrap_or(Color::Reset)`. Themes **cannot** elevate the popup interior above the body — the design intent is that popups read as a framed cutout of the body, not as an elevated card. `--dialog-bg` and `--dialog-shadow` declarations in a stylesheet are deliberately ignored. Only `--dialog` (border color) and `--dialog-key-bg` (hotkey chips on confirm dialogs) are themable.\n\nIf you find yourself wanting popup elevation, push back on the design before adding it — the \"always flush with body\" rule fixed two separate visual artifacts (mismatched corners on dark themes, dark popup on light terminals).\n\n### Border shape (`:root` \u002F `#body`)\n\n`:root` \u002F `#body` declarations of `border-style`, `border-radius`, `border` shorthand, and `border-color` resolve via `resolve_border_shape` in `crates\u002Froder-tui\u002Fsrc\u002Ftheme\u002Foverrides.rs` into `ThemeOverrides::border_shape: Option\u003Croder_theme::BorderShape>`. `Theme::apply_overrides` maps that to:\n\n- `Theme::border_type: ratatui::widgets::BorderType` (default `Rounded`).\n- `Theme::borders_visible: bool` (false only for `border-style: none`).\n\nEvery framed widget reads both fields (`Block::default().borders(borders).border_type(theme.border_type)`). To add per-widget overrides later, the renderer must move from `theme.border_type` to `style_map.computed(node).border` — wire it through one widget at a time, don't try to refactor the whole TUI at once.\n\n### Parsed but inert (do not rely on these — they silently no-op)\n- `:hover`, `:focus`, `:selected`, `:first-child`, `:last-child`, `:nth-child`, `:not(...)` — the parser accepts them but matching is incomplete.\n- `margin`, `visibility`, `opacity`, `text-transform`, `white-space`, `::before` \u002F `::after`, `+` (adjacent sibling).\n- Anything not in the list above.\n\nIf you need one of these, **extend the parser and the cascade in lockstep** — don't ship a theme that depends on a property the engine drops.\n\n## 5. Adding a new theme\n\n1. Create `themes\u002F\u003Cname>.css`. Set every variable you want to differ from baseline (see `themes\u002Fdefault.css` for the full list).\n2. Target at least one class or id beyond `:root` so the cascade is exercised (e.g. `.error { color: ...; }` or `#status-line { ... }`).\n3. Register the basename in `crates\u002Froder-tui\u002Ftests\u002Ftheme_e2e.rs::ALL_THEMES`. The `all_checked_in_themes_parse` and `repo_themes_directory_has_ten_or_more_files` tests will fail if you forget.\n4. Add a one-line assertion test in the same file that proves the theme changes a specific color or hides a specific class.\n\nThe user-facing theme picker discovers any `*.css` under `~\u002F.roder\u002Fthemes\u002F`, `.roder\u002Fthemes\u002F`, or the repo `themes\u002F` directory; the basename becomes the picker id. Selection persists to `~\u002F.roder\u002Fstate.toml` (`[tui].active_theme`).\n\n## 6. What NOT to do\n\n- Don't add inline `Color::Rgb(...)` calls in renderers. Add a `Theme` field, patch it from a conventional `:root` variable (extend `KNOWN_VARS` if needed), and pull it through a `Theme` helper.\n- Don't introduce a new CSS property keyword without extending both `crates\u002Froder-theme\u002Fsrc\u002Fparser.rs` (lexer) and `crates\u002Froder-theme\u002Fsrc\u002Fcascade.rs::apply_declaration` (interpreter). A keyword without an interpreter is a silent footgun.\n- Don't ship a theme that depends on `:hover`, `border`, `margin`, `opacity`, or pseudo-elements — they are parsed-but-inert (see §4).\n- Don't gate any policy or approval behavior on a render flag like `Theme::hide_thinking`. Render flags are presentation only.\n- Don't add a `themes\u002F\u003Cname>.css` without also extending the `ALL_THEMES` test list.\n\n## 7. Pointers\n\n- RFC: `rfc\u002F0001-tui-css-theming.md`\n- Engine crate: `crates\u002Froder-theme\u002Fsrc\u002F{parser,cascade,properties,style_map,node,ast}.rs`\n- TUI integration: `crates\u002Froder-tui\u002Fsrc\u002Ftheme\u002F{mod,discovery,overrides,state,node_tree}.rs`\n- Theme baseline \u002F palette glue: `crates\u002Froder-tui\u002Fsrc\u002Fapp.rs` `impl Theme` (around lines 110–330)\n- Palette source: `crates\u002Froder-tui\u002Fsrc\u002Fpalette\u002Fsources.rs::theme_source` + `PaletteAction::SetTheme`\n- Tests: `crates\u002Froder-tui\u002Ftests\u002Ftheme_e2e.rs`, `crates\u002Froder-tui\u002Ftests\u002Ftheme_palette.rs`, `crates\u002Froder-theme\u002Fsrc\u002Fcascade.rs` (unit tests)\n- Bundled themes (10 today; `default`, `midnight`, `solarized`, `minimal`, `high-contrast`, `gruvbox`, `dracula`, `tokyo-night`, `light`, `focus`) live in `themes\u002F` — keep the on-disk set and `ALL_THEMES` in `tests\u002Ftheme_e2e.rs` in sync.\n",{"name":5,"description":7},"master","cc8a773a0aeb90b9a2c6d9496045d0086befa159",".agents\u002Fskills\u002Froder-theming",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add RoderAI\u002Froder --skill roder-theming",{"tool":40,"command":41},"bunx","bunx skills add RoderAI\u002Froder --skill roder-theming",{"tool":43,"command":44},"pnpm","pnpm dlx skills add RoderAI\u002Froder --skill roder-theming","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Froder-theming\u002FSKILL.md",true,[],[49,56,63,70,77,83],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"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":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":65,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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",[],[]]