← ClaudeAtlas

dsh-plugin-authorlisted

Develop a DeepSeek Harness (dsh) plugin that actually loads and activates in the Windows desktop app, and instrument it so any failure names its own root cause. Covers the full contract — the package.json declarations, the host half, the browser half, Cordis service injection, slot registration, store semantics — and eight failure modes that each cost a full reinstall-and-restart cycle to discover, with the exact error text each one produces. Use when the user wants to build, scaffold, debug, or publish a dsh plugin; when a plugin will not activate; when the app refuses to start after installing a plugin; when a plugin's UI renders empty; or when they ask how to add a panel, tool, sidebar entry, or settings row to the dsh desktop app.
renjie2026/dsh-skills · ★ 0 · API & Backend · score 70
Install: claude install-skill renjie2026/dsh-skills
# Authoring a dsh plugin that actually runs DeepSeek Harness is plugin-composed: the UI, the agent loop, the tools and the theme system are all plugins on the Cordis framework. A plugin is a package that declares itself in `package.json` and exports an `apply(ctx)` on each half. This skill exists because a working plugin and a plugin that *looks* right are very different things. Eight distinct failure modes were hit while building one real plugin, and **none of them were visible without a full reinstall-and-restart cycle**. Each one is documented here with its symptom and its fix, so the next author does not pay that cost. ## When to Activate - Building or scaffolding a dsh plugin - A plugin does not activate, or activates but renders nothing - `web boot: 1 entry did not activate` after installing a plugin - A panel, sidebar entry, settings row or tool needs adding to the dsh UI - `cannot get property "X" without inject`, `Cannot access 'X' before initialization` - **`X is not defined` in a plugin whose code looks correct** (§3.14 — scope reach) - **The renderer's memory climbs and the UI sticks, with no exception and no crash log** (§3.12 — a plugin that writes an event it also subscribes to; this is the expensive one) - **A retry / re-apply loop runs forever or the app repaints constantly** (§3.13, §3.15) - Writing tests or audits for a plugin whose bundle cannot be imported under Node - Preparing a plugin for GitHub / a skill store --- ## 1. Shape of a plugin ```