Skip to content
DSH Themes
Back to Learn
02Decision6 min readBeginner

BEGINNER GUIDE · THE VISUAL LAYER

What is DSH Themes?

DSH Themes is an independent community project for discovering and reviewing visual work for the DeepSeek Harness Web UI. It is not DeepSeek AI and is not endorsed by DeepSeek.

Last verified
Aug 15, 2026
Runtime
0.1.0-rc.6
Verified scope
  • Official ThemeRuntime token surface
  • DSH Themes V2 publishing contract
  • Hosted versus external showcase boundary
On this page
  1. What the project actually does
  2. The website and your computer have different jobs
  3. Verified is an evidence state, not a style label

What the project actually does

The website separates discovery from authorization. You can inspect screenshots, compare light and dark modes, study semantic tokens, and read provenance in the browser. A release becomes installable only after a specific artifact and its compatibility evidence pass the publication gate.

TokenRoleCheck
Simple ThemeOverrides the fixed 13 semantic light and dark tokensDeclarative data and generated bundle only
Full SkinAdds controlled styling and content-addressed WebP assetsStricter rights, selector, package, and runtime proof
External showcaseIntroduces third-party visual work and its sourceNo hosted installer or verified badge without clearance

The website and your computer have different jobs

  1. 01

    Discover and compare on the website

    Browse released work, inspect its provenance, and compare exact light and dark evidence without changing your machine.

  2. 02

    Authorize one exact artifact

    A package name alone is not enough. The selected version, controlled download, complete artifact digest, and compatibility record must agree.

  3. 03

    Install through the local Agent workflow

    Profile mutation happens locally. The theme-manager path checks the runtime, preserves rollback state, and uses the official plugin lifecycle.

  4. 04

    Restart and verify the real Web UI

    Static plugin-set changes need a DSH restart. The resulting profile and browser appearance are checked after the restart.

Verified is an evidence state, not a style label

  • The release identity, manifest, package bytes, SHA-256, and integrity must agree.
  • The exact DSH artifact, dependency closure, frontend, token catalog, and selector record must match the tested baseline.
  • Full Skins require real isolated light and dark runtime captures from the final package.
  • Source, license, attribution, and media rights remain separate from technical compatibility.

Choose what you want to do next

Explore verified workBrowse Theme, Full Skin, concept, and external boundaries.Choose Theme or Full SkinMatch the package class to the intended visual change.Read the installation pathUnderstand the verified local workflow before changing a profile.

Continue learning

Previous guideWhat is DeepSeek Harness?Next guideHow is DeepSeek Harness different?

Continue from the verified evidence

Compare published artifacts or return to the installation documentation.

ExploreDocs