13-token calibration
- #F4F8FD
- #FFFFFF
- #E9F2FC
- #FFFFFF
- #D6E3F1
- #B7CCE2
- #1769E0
- #132D46
- #526C81
- #B93445
- #167656
- #9B5E07
- #E6F0FB
DEEPSEEK HARNESS LEARNING CENTER
Understand the system. Shape the interface.
Start with DeepSeek Harness itself, then follow the rc.6-verified workflow to choose, compare, create, install, verify, and roll back Themes and Full Skins.
13-token calibration
Verified against DeepSeek Harness 0.1.0-rc.6
Orientation
Learn how themes, installation, and rollback work
Choose a format, inspect its evidence, install a verified release, and keep a rollback path.
Choose the right format
Decide between a Theme and a Full Skin before you install.
Inspect the evidence
Read compatibility, package, and light/dark proof before acting.
Use the documented install workflow
Use the Agent-assisted or manual workflow without skipping checks.
Verify and keep a rollback
Confirm rc.6 behavior and preserve the previous artifact.
Beginner path
Choose → Inspect → Install → Verify
- 01Understand the workbenchLearn how plugins, profiles, workspaces, permissions, sessions, and the Web UI fit together.
- 02Choose the change surfaceDecide whether you need a 13-token color theme or a Full Skin with controlled imagery and generated CSS.
- 03Check both modesCompare verified light and dark evidence side by side before judging a release.
- 04Install with a way backVerify the whole artifact, preserve the previous exact release, and confirm one active web-profile theme.
Guide directory
Find the next guide
Search every guide or narrow the directory by learning path and level.
11 guides available
Understand and start
Build a plain-language model of the system, then choose the right package and keep the rollback path intact.
What is DeepSeek Harness?
A plain-language map of the local Agent workbench, its plugin tree, profiles, tools, sessions, and Web UI.
- Official README and architecture at source commit 47f9438
- Official Web UI guide
- Current rc.6 npm artifact boundary
What is DSH Themes?
Understand the independent catalog, evidence model, publishing boundary, and local installation workflow around the Harness Web UI.
- Official ThemeRuntime token surface
- DSH Themes V2 publishing contract
- Hosted versus external showcase boundary
How is DeepSeek Harness different?
Compare plugin-first DSH with SDK-first, graph-first, and finished Agent products without turning different tools into a simplistic ranking.
- Official DeepSeek Harness architecture
- Official OpenAI Agents SDK overview
- Official LangGraph overview
DeepSeek Harness quick start
Launch the official Web UI, configure a model, choose a disposable workspace, understand approvals, and run a first task.
- Official npm launch path
- Official Web UI guide
- Loopback and workspace safety boundary
Choose a Theme or a Full Skin
Match the package class to the visual surface you actually need to change.
- Simple Theme V2 boundary
- Full Skin V2 boundary
- Installability versus concept status
Install a Verified Release
Verify compatibility and the complete artifact before changing the DSH web profile.
- Exact rc.6 compatibility lane
- Whole-artifact SHA-256 verification
- Single direct web-profile theme
Switch and Roll Back Precisely
Change one web-profile theme at a time while preserving an exact, verified return path.
- Single active direct dependency
- Exact rollback artifact record
- CLI and real-runtime postflight checks
Evaluate and tune
Read light and dark evidence together, then inspect the exact semantic token surface.
Compare Light and Dark Modes
Evaluate a release as a two-mode system instead of choosing from one attractive frame.
- Verified catalog specimens
- Light and dark token pairs
- System-mode runtime boundary
Use the 13-Token Lab
Read the fixed semantic catalog and turn color differences into reviewable decisions.
- Exact rc.6 13-token catalog
- Verified sidecar specimens
- Light and dark declaration copying
Create and release
Build a declarative Full Skin draft and understand the evidence required before publication.
Create a Full Skin Draft
Use the Studio to produce a declarative draft without accepting author-supplied executable code.
- Studio image and token constraints
- Declarative FullSkinManifestV2 inputs
- Simulated-preview boundary
Publish with Verifiable Evidence
Move a declarative submission through provenance, runtime, compatibility, and deterministic-build gates.
- Full Skin publication gate
- Real rc.6 runtime screenshots
- Artifact and payload digest scopes
Common questions
Before you make a change
Answers about formats, compatibility, evidence, and rollback.
Can this website install a theme on my computer?
No. The website supports discovery, comparison, creation, submission, and controlled downloads. Profile changes happen locally through the DSH CLI or the public theme-manager Skill.
What compatibility baseline do current releases use?
The current installable lane targets @deepseek-ai/dsh 0.1.0-rc.6 and its recorded npm, frontend bundle, 13-token, and selector fingerprints. A version label alone is not sufficient evidence.
Why is there no rc.6 source commit in the manifest?
The rc.6 npm release has no verified corresponding source commit. Current V2 manifests omit that field instead of borrowing the historical rc.5 commit.
Is a Studio preview proof that a Full Skin works?
No. Studio previews are simulations for drafting. Publication requires controlled light and dark screenshots captured from the final artifact in a real isolated rc.6 DSH runtime.
Why keep only one @dsh-themes/* package active?
Direct theme packages can compete for the same token and skin surfaces. The supported web-profile workflow removes the previous direct package before adding the next one, then verifies the resulting configuration.
Next steps
Continue with a verified artifact
Explore published work, or start a Full Skin and submit it for review.