DeepSeek Harness UI skins

A well-behaved appearance plugin should limit itself to colors, typography, background, and layout density of the local Web UI (commonly http://127.0.0.1:3080/). It should not silently register shell tools, rewrite credentials, or exfiltrate session logs.

Read the README for: Cordis services it patches, whether it needs network, and how to unload it. If unload is undocumented, treat it as higher risk than a CSS tweak.

Skins that bundle “one-click marketplaces” are still community UIs on top of GitHub/npm — the plugin guide safety list still applies.

1. Get a working CLI from Install.
2. Copy dsh plugin add github:owner/repo from the plugin README (not from an unverified screenshot).
3. Reload the web profile and confirm only visual changes.
4. If the UI breaks, remove the plugin the way the README states, or start a clean profile.

Port conflicts and blank pages are usually not the skin — see Troubleshoot. Preview builds change; a theme built for rc.N may fail on rc.N+1.

Reference directories list hundreds of “界面与皮肤” entries. Mirroring them here would create thin, duplicate pages and a false store. We keep a curated set on Community Plugins (category UI & skins) and point the rest to GitHub topic dsh-plugin.

Examples already on the curated list include Web UI managers, generative chat cards, and appearance packs — always re-read licenses. This independent site does not “verify” themes and does not ship binaries in the browser.

Architecture recap: plugin ecosystem. Authoring: plugin guide. If you built a skin, the contribute page explains how discovery works. For day-to-day coding, pick a mode first — Creative is a better lab than Standard when you are injecting UI plugins.