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

GUIDE 01 · DECISION

Choose a Theme or a Full Skin

Start with the smallest package that can produce the intended result. This makes review clearer and reduces the runtime surface you must verify.

Last verified
Aug 15, 2026
Runtime
0.1.0-rc.8
Verified scope
  • Simple Theme V3 boundary
  • Full Skin V3 boundary
  • Installability versus concept status
On this page
  1. Choose by change surface
  2. Read evidence before aesthetics

Choose by change surface

A Simple Theme changes the complete fixed set of 13 semantic color tokens. A Full Skin includes those tokens and may also add controlled layout styling plus content-addressed WebP assets. A catalog item labeled as a concept can communicate an idea without providing an installable package.

TokenRoleCheck
Simple ThemeColor-only semantic overrideAll 13 light and dark token values are present
Full SkinTokens plus generated CSS and controlled WebP assetsFinal package and real runtime previews are verified
Concept SkinVisual direction without a release artifactTreat as inspiration, not an install target

Read evidence before aesthetics

  1. 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.

  2. 02

    Check light and dark together

    A release must work as a pair of modes; do not select it from one favorable screenshot.

  3. 03

    Confirm a published artifact exists

    Installability belongs to a specific published version, not to the catalog kind or artwork alone.

  4. 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

Gallery · ThemesFilter the unified Gallery to color Themes.Gallery · SkinsFilter the same Gallery to Full Skins and skin showcases.Review preview modesSwitch light and dark on each Gallery card using one review frame.

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; Installability versus concept status

What should I do first?

Start with the smallest package that can produce the intended result. This makes review clearer and reduces the runtime surface you must verify.

Which boundary matters most?

Check that the selected version exposes a controlled download, a complete artifact SHA-256, integrity, a V3 manifest, and every exact RC.8 compatibility and runtime-attestation fingerprint. Full Skins additionally need real light and dark evidence.

Continue learning

Previous guideDeepSeek Harness quick startNext guideInstall a Verified Release

Continue from the verified evidence

Compare published artifacts or return to the installation documentation.

ExploreDocs