Choose by change surface
A Simple Theme changes the fixed set of 13 interface color roles. A Full Skin includes those colors and can add artwork and visual styling. Submission drafts may show a design idea before a package is ready; they are not published catalog releases.
| Token | Role | Check |
|---|---|---|
| Simple Theme | Color-only semantic override | All 13 light and dark token values are present |
| Full Skin | Tokens plus generated CSS and controlled WebP assets | Final package and real runtime previews are verified |
| Submission draft | A design idea awaiting review and packaging | Submit for review before it becomes a published release |
Read evidence before aesthetics
- 01
Name the desired change
If the goal is palette and contrast, start with a Theme. If imagery, surfaces, or controlled selector styling are essential, evaluate a Full Skin.
- 02
Check light and dark together
Compare both previews and read the supported appearance modes. Some community skins intentionally keep a fixed dark appearance.
- 03
Confirm a published artifact exists
Installability belongs to a specific published version, not to the catalog kind or artwork alone.
- 04
Plan the operational cost
Adding, removing, or switching a package requires a DSH restart. Appearance changes inside an installed skin do not require replacing the package.
Continue the decision
Choose by the amount of visual change
Compare one Theme and one Full Skin in both modes. A color-focused Theme is a smaller visual change; a Full Skin can change the surrounding illustration, materials, and atmosphere.
Compare these two catalog items for long coding sessions. Explain the visual changes, preview both modes, and check the current Harness compatibility before installing my choice.Common questions
Before you make a change
Answers about formats, compatibility, evidence, and rollback.
What does this guide verify?
This guide covers: Simple Theme V3 boundary; Full Skin V3 boundary; Published packages versus submission drafts
What should I do first?
Start with what you want to change: colors, backgrounds, or the overall appearance. Compare the previews and supported modes, then copy the installation task for your chosen item.
Which boundary matters most?
This guide targets DeepSeek Harness 0.1.3-alpha.1 at source commit d347e703908d0406b7a7ef80e3a0e594d86b2215. The Alpha installation uses a build from that exact source revision. Check the selected item’s current package, profile, and test results separately; older receipts and screenshots do not establish compatibility with this Alpha.
Can the preview prove current compatibility?
No. Artwork and historical screenshots show appearance. Current compatibility comes from the item’s package and actual runtime checks.
Continue learning
Continue from the verified evidence
Compare published artifacts or return to the installation documentation.