What the project actually does
The 97 published records use three mutually exclusive lanes: 32 hosted artifacts use the Theme Manager, 11 fixed community skins use the separate Community Skin Installer, and 54 external-source records link to their upstream projects. You can inspect every preview, compare light and dark modes, study semantic tokens, and read provenance in the browser.
| Token | Role | Check |
|---|---|---|
| Simple Theme | Overrides the fixed 13 semantic light and dark tokens | Declarative data and generated bundle only |
| Full Skin | Adds controlled styling and content-addressed WebP assets | Stricter rights, selector, package, and runtime proof |
| Community Skin | Uses a fixed third-party package or reviewed adaptation | Only 11 allowlisted items with rc.8 receipts, disclosures, consent, and the separate installer |
| External showcase | Introduces third-party visual work and its source | 54 external-source records: open the pinned upstream project and its available setup path |
The website and your computer have different jobs
- 01
Discover and compare on the website
Browse released work, inspect its provenance, and compare exact light and dark evidence without changing your machine.
- 02
Authorize one exact lane and item
A hosted release needs a controlled download, complete artifact digest, and V3 compatibility record. A community skin instead needs an exact allowlist entry, package or adaptation identity, item-level rc.8 receipt, required disclosures, and consent.
- 03
Use the eligible local Agent Skill
Profile mutation happens locally. Hosted artifacts use theme-manager; the 11 fixed community skins use the separate community-skin-installer. External-source records open their pinned upstream project and only use an eligible setup path when one is available.
- 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
Common questions
Before you make a change
Answers about formats, compatibility, evidence, and rollback.
What does this guide verify?
This guide covers: Official ThemeRuntime token surface; DSH Themes rc.8 V3 publishing contract; Hosted, community-runtime, and external-source lanes
What should I do first?
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.
Which boundary matters most?
DSH Themes is not affiliated with or endorsed by DeepSeek AI. DeepSeek and DeepSeek Harness names identify the upstream project and compatibility target; they do not turn this website into an official service.
Continue learning
Continue from the verified evidence
Compare published artifacts or return to the installation documentation.