Skip to main content

dsh-ui-web/packages/dsh-skins

34Stars2Forks0Issues0Watchers

An npm package with 9 built-in DSH Web GUI theme skins and skin center cards, supporting online preview and one-click switching without restart.

Evidence5/5methodologySourceInstallMaintenanceDSH versionSecurity scan
Machine-auditedInstall commandRepo verifieddsh-plugin topicLicenseREADMEAI wiki

ⓘ This plugin is a sub-package of the CAPTAIN1275/dsh-ui-web monorepo — stars and activity count the whole repository.

Language
TypeScript
License
Apache-2.0
Branch
main
dsh-plugindsh-plugin-marketdsh-plugins

Install

cmdweb profile
$ dsh plugin --profile web add @captain1275/dsh-skins

Run the command above in your terminal to install this plugin via the dsh CLI. You can switch Profile in the top-right corner. New to dsh? Read the beginner tutorial

Install via your agent

Install the DeepSeek Harness plugin CAPTAIN1275/dsh-ui-web/packages/dsh-skins for me: review the repository at https://github.com/CAPTAIN1275/dsh-ui-web first, then run the install command and verify the plugin loads successfully.

Paste this instruction to the DSH Web GUI assistant — it will install and verify for you.

At a Glance

A unified skin bundle for DSH Web GUI: After installation, a "Skin Center" card appears in "Plugin Config → Web UI Plugins", listing 9 built-in theme skins (THS, Windows XP, Blue Fantasy, Dragon Heir, Minecraft, Miku, Trading Terminal, Whale Song, Aurora), supporting online try-on and one-click switching.

Core Features

  • Insert a Skin Center card in "Plugin Config → Web UI Plugins", listing all official default and installed skin names, taglines, and accent colors, with the currently active skin marked as Active
  • Try on any skin online (non-persistent): instantly preview effects, light/dark theme toggle, exit to fully restore the current skin state
  • One-click apply skin: host /api/skin-center/apply uses in-process dsh-skin use ESM port, writes to ~/.dsh/cordis.patch.yml managed section, configuration listener hot-reloads within seconds without restart
  • Skins are mutually exclusive: only one skin can be active at a time, enforced by the dsh-skin managed section in the patch file
  • One npm package bundles all 9 skin assets (each skin is a set of skin.json + lib/client.js + lib/index.js + cordis.patch.yml), no separate npm package name needed for each skin
  • Try-on uses on-demand loading: skin bundle (~700KB base64 art resources) is loaded via same-origin script route only when clicking "Try on", not embedded in cold start

Technical Implementation

  • Language: TypeScript (skin center host/client) + Node.js (aggregator build script as ESM .mjs)
  • Key Dependencies: @deepseek-ai/dsh-host-webserver (host routing service), @deepseek-ai/dsh-settings (background occlusion config schema), @deepseek-ai/dsh-client-runtime / @deepseek-ai/dsh-client-ui-theme / @deepseek-ai/dsh-client-locale (client runtime/theme/i18n), schemastery (schema validation), react ^18.2.0 (skin center card UI)
  • Architecture Pattern: Cordis plugin host + client dual half; host half mounts native HTTP route /api/skin-center/* in ctx.effect, injected via dsh-client-runtime; the use command for skin switching writes patch file + manages profile node_modules symlinks via in-process src/skin-switch.ts (1:1 ESM port of dsh-skin CLI), no external CLI binary needed
  • Entry Files: Aggregator entry packages/dsh-skins/build.mjs (syncs assets from source packages/skins/<id> to packages/dsh-skins/skins/<id>); skin center host entry packages/skins/skin-center/src/index.ts; skin center client entry packages/skins/skin-center/src/client/index.ts

Use Cases

Ordinary users who want to change the style of DSH Web chat interface without fiddling with command lines: install one package to get 9 themes, from THS stock trading style, Windows XP Luna nostalgia, Minecraft block world to the popular Miku and Whale Song, all available for try-on / one-click switching in the Skin Center card.

Developers who like custom skins can also use it: the aggregator package fully bundles each skin's skin.json + lib/client.js, add your own skin following the packages/skins/aurora template, run pnpm --filter @captain1275/dsh-skins build and it will appear in the Skin Center.

Prerequisites & Compatibility

DependencyMinimum VersionNotes
DSH0.1.0-rc.6+@deepseek-ai/dsh-host-webserver, @deepseek-ai/dsh-client-runtime, etc. in skin center devDependencies are all ^0.1.0-rc.6 (packages/skins/skin-center/package.json:38-46)
NodeNot declaredNeither root nor package.json declares engines field
PlatformWeb / macOS / Windows / LinuxBundle declares dsh.client.platform: "web" (packages/skins/skin-center/package.json:23); host half automatically falls back to directory junction on Windows, no developer mode required (packages/skins/skin-center/src/skin-switch.ts:433,487-502)
Native modulesNoneOnly uses Node built-in fs/os/path, no third-party native modules; falls back to directory junction on Windows symlink failure

Installation

dsh plugin --profile web add github:CAPTAIN1275/dsh-ui-web/packages/dsh-skins

Configuration

ConfigTypeDescriptionDefault
backgroundOpacityNumber (0-100, step 5)Main interface background occlusion opacity; higher values darken the background image; only visible effect for skins with built-in backgrounds (e.g., blue-fantasy / whale-song) (packages/skins/skin-center/src/index.ts:34-47)0

FAQ

Q: What will I see in the DSH Web interface after installing this package?

A: A "Skin Center" card appears in "Settings → Plugin Config → Web UI Plugins", listing "Official Default" plus all installed built-in skins (THS ths, Windows XP luna, Blue Fantasy blue-fantasy, Dragon Heir dragon-heir, Minecraft minecraft, Miku miku, Trading Terminal trading, Whale Song whale-song, Aurora aurora), with the currently active skin marked as Active.

Q: Do I need to restart the dsh web service to switch skins?

A: No. After clicking "Apply / Restore Default", the skin center writes changes to the dsh-skin managed section of ~/.dsh/cordis.patch.yml via in-process dsh-skin use, the host configuration listener hot-reloads within seconds, and refreshing the browser shows the new skin.

Q: Can I enable two skins at the same time?

A: No. The skin center enforces only one active skin through the dsh-skin managed section in the patch file; other skins are written as disabled: true.

Q: Will "Try on" modify my current settings?

A: No. Try-on only temporarily mounts that skin's visuals on the current page (actually uses module loader, not eval), and on exit restores the current skin's body attributes, background inline styles, chrome child nodes, xp footer taskbar, etc., according to the recipe, without writing any files.

Q: After installation, the skin list is empty or missing some skins. What should I do?

A: Check if packages/dsh-skins/skins/<id> contains skin.json, lib/client.js, lib/index.js, and cordis.patch.yml simultaneously; missing any will be skipped by build.mjs; normal npm install will automatically complete the build.

Q: Getting "Permission denied" errors when switching on Windows?

A: The switching logic automatically falls back to directory junction (junction) when symlink fails, no developer mode required; if it still fails, run dsh as administrator, or manually place the skin package in profile's node_modules.

Q: How do I add my own skin?

A: Place skin.json (containing id, name, tagline, bodyAttr, wiring.id, package fields) + built lib/client.js / lib/index.js / cordis.patch.yml under packages/skins/<your-id>/, then run pnpm --filter @captain1275/dsh-skins build to repackage; reinstall the aggregator package to see it in the Skin Center.

Q: How do I remove a skin and switch back to official default?

A: The Skin Center card has an "Official Default" entry; click to apply with one click; to completely uninstall the plugin, use dsh plugin --profile web remove @captain1275/dsh-skins.

Difficulty Level

Beginner — After installation, the Skin Center card is directly visible in Web plugin config without any additional configuration; only need to look at build.mjs and skin.json fields when adding or adjusting skins.

Known Issues & Limitations

  • Skin Center only reads the wiring.bundleWired static field from each skin.json, not implementing runtime detection based on actual profile loading situation (TODO noted at packages/skins/skin-center/src/skin-switch.ts:245-248)
  • Creating profile symlinks on Windows may fail (no developer mode / insufficient permissions), automatic fallback to directory junction (junction) required to complete switching (packages/skins/skin-center/src/skin-switch.ts:433,487-502)
  • Bundle targets DSH Web GUI only (dsh.client.platform: "web"), browser half will not load in CLI mode (headless profile)
  • Skins only modify browser DOM (CSS, title bar, status bar, background image, etc.), do not affect any model requests

Read the usage guide →

Install steps, key points, FAQ and compatibility for this plugin — auto-derived from indexed fields.

Listing badge

Listed on deepseek-plugin.org
[![Listed on deepseek-plugin.org](https://img.shields.io/badge/listed_on-deepseek--plugin.org-007EC6)](https://deepseek-plugin.org/plugins/CAPTAIN1275/dsh-ui-web/packages/dsh-skins)

Paste this markdown into your GitHub README to link back to this listing. The badge only states the listing — not a security endorsement.

← Back to plugin directory