dsh-theme-studio
自定义 dsh UI 主题：12 种强调色预设、支持深色模式并带对比度保护的强调色、密度、字体系列、动画开关，以及原始设计令牌覆盖。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:hj01857655/dsh-theme-studio#bd11f1d179d61f87e5fb991e83ae36fb23ae5c7fTheme Studio 以 dsh-theme-studio 发布，当前版本为 0.6.3。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A dsh plugin that customizes the UI theme: accent presets, a custom accent color, content density, font family, an animation toggle, and raw design-token overrides.
This plugin only writes design tokens that actually exist in dsh, verified by reading the shipped stylesheets (@deepseek-ai/dsh-client-ui-theme/lib/client.js). Every token it writes is listed in src/tokens.ts and enforced by tests/tokens.test.mjs.
Changes go through ctx.theme.overrideTokens() — dsh's own theme service — not direct DOM writes. See Mechanism for what that buys.
That constraint has two visible consequences:
border-radius per component — including 50% circles and corner-shape: round — and ships no radius token. There is no faithful way to offer this, so it is not offered.0.001ms rather than 0s — a zero duration can stop transitionend / animationend from firing and hang components that wait on them. The sheet is owned by this plugin's effect scope, so unloading removes it.ctx.theme.setFontSize(), so it agrees with the official
Appearance control instead of shadowing it--dsw-* or --dsh-* tokendensity field; it is ignored on import, since the font size
is host state nowdsh plugin add dsh-theme-studio
From source:
git clone https://github.com/hj01857655/dsh-theme-studio.git
cd dsh-theme-studio
npm install && npm run build
dsh plugin add link:.
The plugin registers a settings.section slot (order 47). Preferences persist in localStorage.
Every theme change goes through dsh's theme service:
export const inject = ['slots', 'locale', 'theme']
…
ctx.theme.overrideTokens('dsh-theme-studio', overrides)
overrideTokens stacks a partial token layer over the active theme. The service handles the rest:
{ light, dark } pair. A single value would go illegible on the other color scheme, so the API rejects one. src/apply.ts builds the pairs; tests/apply.test.mjs asserts the shape of every value it can emit.The layer is keyed by source (dsh-theme-studio), and re-publishing replaces it wholesale, so a shrinking override set can never leave a stale token behind.
An earlier version wrote custom properties straight onto document.body with style.setProperty. That happened to work — dsh's presenter only retracts variables it wrote itself — but it bypassed the stacking order, the paired values and the dispose story, and made every reset the plugin's own responsibility.
--dsh-content-font-size is the axis the official Appearance row owns, and an
override layer sits on top of the theme snapshot. Overriding that token
therefore does not change the setting — it hides it, leaving the official stepper
displaying a number the UI no longer rendered.
So Density does not use an override at all. It calls
ctx.theme.setFontSize(), the same entry point the official control uses, and
reads back through getTheme().fontSize:
--dsh-content-font-size never appears in this plugin's override layer. The
custom-CSS box can still set it, because that is you asking, not the plugin
deciding.An earlier version treated the size as this plugin's own state, which produced a control that silently disabled the official one on install (0.5.0) and then, once the default was made inert, one that still shadowed it whenever it was used (0.5.1).
It renders with the same variable names the application uses, so a wrong token looks wrong in the preview too, rather than being masked by a hardcoded fallback color.
Preferences arrive three ways — localStorage, an imported JSON file, and a
hand-edited version of either. All three pass through normalizePreferences(),
which is the only place that validates: unknown enum values fall back to the
inert default, a density: "comfortable" written by 0.5.0 migrates to
"default", malformed colors become null, and non-string/non-boolean fields
drop back to defaults. parseTheme intentionally keeps no whitelist of its own,
so the two entry points cannot drift apart.
MIT