DEEPSEEK HARNESS LEARNING CENTER
DEEPSEEK HARNESS LEARNING CENTER
Understand the system. Shape the interface.
Start with DeepSeek Harness itself, then follow the RC.8 V3 verified workflow to choose, compare, create, install, verify, and roll back Themes and Full Skins.
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 behavior against the current catalog evidence 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 modesOpen the Gallery, filter to Themes, and switch each verified card between light and dark 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.
0 guides available
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.8 and binds separate official-source, npm registry, Web asset-set, ui-theme bundle, 13-token, selector, and final runtime-attestation evidence. A version label alone is not sufficient.
Why are RC.8 source and npm provenance separate?
The official RC.8 tag maps to a source commit, while npm exposes fixed registry digests without a gitHead or build attestation. V3 records both facts without claiming the tarball was reproduced from that commit.
Is a Studio preview proof that a Full Skin works?
No. Studio previews are simulations for drafting. Publication requires controlled light and dark evidence from the final artifact in a real isolated RC.8 runtime and a managed cold-restart check.
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.