Native DSH Web extension loading built-in and user skins from `$DSH_HOME/skins/`, hot-switching without reload, with extra themes from dsh-market.com.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-11-20
License
BSD-3-Clause
01What can it help you accomplish?
Personalize the DSH Web GUI with catalog skins and live try-on
Applied scoped CSS and backgrounds with a persisted skin or custom light/dark profile
DSH Web and Desktop users who want curated themes beyond the stock monochrome look
Install community skins from DSH Market without repackaging npm assets
Market and hand-dropped skin folders under the harness skins home, managed in one catalog
Users browsing Workshop skins on dsh-market.com who want one-click installs into the harness home
Tune accent, background, and contrast with an audited custom theme
Independent light/dark palette profiles whose CSS is limited to official token remaps
Teams wanting brand colors without editing raw `patches.css` or arbitrary selectors
02How to install into DeepSeek Harness
Prerequisites
- DSH Web profile (install command uses `--profile web`)
- For git-based install from the monorepo, pnpm ≥10 needs `allowBuilds` authorized per README
Installation steps
- 01
Run `dsh plugin --profile web add @linxin666/dsh-client-ui-skin-center`
$ dsh plugin --profile web add @linxin666/dsh-client-ui-skin-center
- 02
For local dev from a `dsh-web` clone, the README also documents `link:` installs and git dependency adds with an in-place `prepare` build
- 03
Install extra catalog skins from dsh-market.com into `$DSH_HOME/skins/`; community folders there need no separate command—reopen the card or reload the page
Verify the integration
- Open Settings → Web Extensions → Skins; the README acceptance checklist expects the skin-center section with no console errors
- Try-on should apply immediately; exiting try-on restores the committed skin
- Apply should switch without reload; a later reload should boot straight into the active skin (no FOUC)
03DSH integration and capability boundaries
Cordis package `@linxin666/dsh-client-ui-skin-center` (`ui-skin-center`) for the DSH Web GUI; add with `dsh plugin --profile web add`.
Atomic try-on and apply
A catalog skin id or custom theme profile from the Skin Center card→Scoped stylesheet and background media with a data-dsh-skin stamp, without rewriting `cordis.patch.yml`
Writes active selection via `POST /api/skin-center/v2/active`Runs CSS transforms in short-lived worker processes per stylesheet requestDual-source skin catalog
Built-in blue-fantasy assets plus folders under `$DSH_HOME/skins/`→Merged list with Active marker; duplicate ids in the user folder shadow built-ins
Reads skin assets from `$DSH_HOME/skins/` and package `skins/`Excludes skins whose `skin.json` fails validationAudited custom theme editor
Light/dark accent, background, foreground, and contrast sliders (0–100)→Token-only CSS from an allowlist; suppressed while a catalog skin is active
Persists profiles in the plugin Config `skin-custom-theme` sectionBackdrop scrim and blur controls
Background occlusion, conversation blur, composer frost, and bubble opacity sliders→Layered backdrop veil and frosted composer follower independent of skin switches
Persists background values to `$DSH_HOME/skin-center-active.json` via `/api/skin-center/v2/active`Anti-FOUC first paint
Active skin id at HTML serve time→`tapIndex` stamps data-dsh-skin and stylesheet links before first paint
Transforms every served `index.html` through the host `webServer.tapIndex` adapter
04Who is it for? When not to use it?
Good for
- DSH Web and Desktop users who want curated themes beyond the stock monochrome look
- Users browsing Workshop skins on dsh-market.com who want one-click installs into the harness home
- Teams wanting brand colors without editing raw `patches.css` or arbitrary selectors
Not for
- L3 `patches.css` and optional `hooks.mjs` can run with full page styling power; the README discloses they are not a security boundary.
- The browser client sends one anonymous daily install heartbeat to dsh-market.com (localStorage id plus package name only).
- Active skin, background sliders, and custom theme data persist under `$DSH_HOME` and plugin Config; API writes are same-origin only.
- Dynamic wallpapers are not bundled—README delegates rendering to the separate `dsh-plugin-wallpaper-engine` plugin, which pauses skin painting while active.
05Compatibility, maintenance and safety notes
- L3 `patches.css` and optional `hooks.mjs` can run with full page styling power; the README discloses they are not a security boundary.
- The browser client sends one anonymous daily install heartbeat to dsh-market.com (localStorage id plus package name only).
- Active skin, background sliders, and custom theme data persist under `$DSH_HOME` and plugin Config; API writes are same-origin only.
- Plugins without semantic DOM attributes only receive L1 token remaps; runtime inline styles need L3 `!important` patches to override.
- Dynamic wallpapers are not bundled—README delegates rendering to the separate `dsh-plugin-wallpaper-engine` plugin, which pauses skin painting while active.
BSD-3-Clause · last push 2026-11-17 · release v0.4.20
06Frequently asked questions
Which DSH profile does Skin Center target?
The documented install path is `dsh plugin --profile web add @linxin666/dsh-client-ui-skin-center`. The README places the Skins tab under Settings → Web Extensions in the DSH Web GUI (Desktop shares that GUI).
How do extra skins arrive on disk?
A fresh install seeds blue-fantasy; other Workshop items install on demand from dsh-market.com into `$DSH_HOME/skins/`. You can also drop community skin folders there—reopen the card or reload to pick them up without a host restart.
What happens when Wallpaper Engine is running?
Wallpaper support lives in another plugin. While a wallpaper renders, the skin center stands down its CSS, background art, and hooks; your selection is remembered and repaints when the wallpaper stops or you explicitly apply a skin again.
Does the plugin phone home?
The README says the browser half sends one anonymous install heartbeat per UTC day to dsh-market.com using a random localStorage id and this package name—no IP storage per that section.
When should I avoid skins with `patches.css` or `hooks.mjs`?
README classifies L3 `patches.css` as arbitrary CSS and `hooks.mjs` as trusted escape-hatch code served same-origin. If you only need palette tweaks, prefer catalog skins or the audited custom theme instead of high-sensitivity skin facets.
07Related DSH workflows
dsh-tui
by ccch1mneyyy
Claude Code 风格全屏终端 TUI:像素鲸鱼顶栏、双流光大字、实时工作状态行、思考流式展开、双击 Esc 时间回溯、上下文进度条 + TPS 仪表;接入 Agent preset(standard/code/minimal/cordis)、Skills、MCP、Goals、Todos、子代理,/ 命令注册表与随附技能(audit/bug/review/practice/pr_comments/release-notes/vuln-check);纯插件挂载零核心改动。
dsh-better-sidebar
by omdsh-dev
Full sidebar workbench with file rendering and editing, terminal, Git, and subagents; third-party plugins can register new tabs.
dsh-media-desk
by woniuniuniu
Capture ideas and generate scripts, titles, covers, images, storyboards, schedules, and review data in a sidebar media workspace.
dsh-drawai
by fourzkw
Create diagram artifacts and use Draw.io-oriented tools from a DSH profile.
08Data and sources
# dsh-skins · Skin Center for DeepSeek Harness (DSH)
skin-center is a self-contained bundle meeting the official DSH plugin standard (`dsh.bundle.patch` points to `cordis.pa…
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-20. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.
