Use when adding, auditing, pruning, archiving, restoring, or reviewing Agent Notes in deepseek-harness; checks every new note for superseded active records, classifies implemented notes by future decision value, deletes rejected notes that no longer prevent a tempting fallacy, and applies the frozen archived/{kind}…
Use when reviewing a pull request in the deepseek-harness repo — orients the reviewer to this codebase's standards (AGENTS.md conventions, defensive patterns, ADRs, quality gates) and the review-specific checks that code alone can't show.
Use when publishing, updating, moving, or removing DeepSeek Harness documentation website pages; editing website/docs.ts mappings or navigation; diagnosing a page missing from the VitePress site; fixing projected documentation links; or running the docs:dev, docs:check, and doc-sync workflow after website-content…
Use when writing, moving, reviewing, or auditing documentation in the deepseek-harness repo — choosing hierarchy and detail, separating tutorials from references, checking tutorial progression, trimming doc slop, responding to a verify-doc-budgets failure, or requests like "improve the docs", "audit the docs", "where…
Use when working in the deepseek-harness repo to find non-obvious simplification candidates, write proposed Agent Notes or inline TODO/FIXME/XXX notes, audit or coalesce superseded Agent Notes, or fold worthwhile simplification ideas from another PR; especially for dead, duplicated, speculative, over-built…
Use when landing a stack of dependent GitHub PRs (A ← B ← C, where each bases on the one below) onto master, merging a PR whose base is another open PR's branch, or whenever a request mentions "stacked PRs", "PR stack", "dependent PRs", or merging several related PRs in sequence. Requires every same-repository…
Use before pushing, force-pushing, marking ready for review, or claiming checks pass on a deepseek-harness branch, and immediately after gh stack sync publishes rewritten branches, to select the smallest tests and checks that cover the outgoing or just-published diff without reflexively running the full repository…
Use when writing, reviewing, restoring, trimming, or auditing prose in the deepseek-harness repo, including deciding where documentation or comments are required across Markdown, JSDoc, code and test comments, prompts, descriptions, diagnostics, and CLI or UI strings.
Manually run the extended DeepSeek Harness bilingual-document workflow, including generated briefings, delegated prose translation, whole-document translation, and scoped pairing verification.
Use when auditing or fixing prose that reads like a leaked reasoning transcript — dead design-session citations such as (decision N), audit item codes, or §N of uncommitted drafts; change narration such as "used to", "no longer", "this cut"; stack or review vantage ("a later PR in this stack", "rejected in review")…
Record browser or Web UI interaction demos as optimized GIFs using the available built-in browser, state-based frame capture, and deterministic encoding, then publish to a dedicated assets branch when the task includes attaching the GIF to a pull request. Use when asked to make, record, or generate a GIF that…
Create, modify, debug, or extend dynamic Cordis Plugins, including Host Services and Events, Client Slot and theme UI, Package-private Client-to-Host calls, dynamic Tools, version updates, approval failures, and runtime diagnostics. Use this Skill to route a user request to the correct platform and Inspect Provider…
Use when creating, changing, or validating a Cordis composition for this harness — writing or editing an agent preset, adding or removing a plugin row, deciding whether something belongs to the host composition or to one session, checking whether a preset you authored actually mounts, or diagnosing a row that mounted…
A production guide for creating skins, or visual themes, for the DSH launcher and its main interface. It covers design variables, tokens, templates, background placeholders, and the skinstudio tool.
Mental model of DeepSeek Harness (dsh) internals — Cordis plugin system, profiles/bundles/patches, the turn flow, session log, capability seams, and the extension-point map. Use this whenever the user asks how dsh works, why something is designed a certain way, where a feature lives, which event/service to use, or…
Set up, upgrade, build, and troubleshoot the DeepSeek Harness (dsh) development environment, especially on Windows — Node/pnpm/corepack versions, the build pipeline, git hooks, and known failure modes. Use this whenever the user hits a build/install/startup error in the deepseek-harness repo, wants to update the repo…
Modify the DeepSeek Harness (dsh) Web UI — client plugin packages under packages/client/, the slot system, conversation Chat nodes, stores, styling, and apps/web. Use this whenever the user wants to change anything visible in the dsh browser GUI — add a panel, settings card, tool card, conversation row, sidebar item…
Operate and tune DeepSeek Harness (dsh) as a power user — run modes (web/headless/ACP/SDK), model & API key configuration, reasoning-effort and cache/cost tuning, profile patching, and the community plugin ecosystem. Use this whenever the user wants to run dsh, configure models or keys, make sessions faster or…
Write plugins for DeepSeek Harness (dsh) — model-facing tools, hook/policy plugins, LLM adapters, protocol drivers, and new workspace packages in the deepseek-harness repo. Use this whenever the user wants to add a tool, intercept tool execution, add a permission gate, register a command, add a model provider, create…
Design and run tests for DeepSeek Harness (dsh) changes — choosing the right tier (unit/coverage/e2e/snapshot/web), writing real-composition and smoke tests, snapshot record/refresh workflow, and coverage-gate rules in the deepseek-harness repo. Use this whenever the user adds or changes tests, asks which checks to…
★not rated 10 19d agoA121 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: