dsh-shortcuts-prompt

快捷指令 · Quick Prompts

A DeepSeek Harness (DSH) plugin that keeps a strip of reusable prompts directly

above the conversation composer.

• The strip starts empty: a single dashed pill reading 快捷指令.
• Click a chip to insert its prompt at the draft caret.
• Click the pill (or the 管理 control once chips exist) to expand the

management panel inline, between the strip and the composer — no dialog, no

scrim.

• The panel holds the list (name + summary + insert / edit / move up / move

down / delete) and the form. **Both the name and the prompt body are

required.** A successful add or save always collapses the panel; a failed

write keeps it open and shows the error, so the draft is not lost.

• The strip itself never edits: it only inserts and opens the manager.

Everything is stored per profile through the DSH storage domain, so the list

survives restarts. Nothing is pre-seeded.

Layout

| File | Role |

|---|---|

| lib/index.js | Host activation: resolves the Harness bases, mounts the service, registers one agent tool |

| lib/service.js | Durable list + the five Remote methods (list / create / update / delete / move) |

| lib/schema.js | zod schemas for records and wire payloads |

| client.js | Browser bundle: the strip, the inline panel, the draft insertion |

| cordis.patch.yml | Inserts the Host row |

| locale/{en,zh}.json | Plugin inventory title/description |

| icon.svg | Inventory artwork |

The model sees the same data through the quick_prompts tool, which calls the

same service methods as the UI.

Install

From npm:

dsh plugin --profile  add dsh-shortcuts-prompt

From this repository (source install; it is plain JavaScript, so no build step):

dsh plugin --profile  add github:smithtomge-alt/dsh-shortcuts-prompt

In the desktop app, install it from Plugins (Plugin Manager) instead of the

CLI: the desktop profile is managed by the application. Restart or reload the

page after installing so the browser half joins the Client module graph.

Publish

The package is a bundle: dsh.bundle points at cordis.patch.yml, and

dsh.client declares the browser artifact. It ships no runtime npm

dependencies — the Host resolves the Harness packages it needs at activation.

First publish (once, by hand)

npm requires an interactive two-factor challenge for publishing, so the first

version is released from a terminal:

npm adduser --auth-type=legacy --registry https://registry.npmjs.org
npm run check && npm test
npm publish --otp=   # publishConfig picks the registry

The OTP is required even when you are logged in: the token npm adduser writes

is a login token, and npm only accepts a bypass token (being retired) or an

interactive code for publish.

Automated releases (trusted publishing)

.github/workflows/publish.yml publishes on a GitHub Release (or a v* tag)

using npm trusted publishing: GitHub's OIDC identity is exchanged for a

short-lived registry token, so there is no NPM_TOKEN secret to leak or rotate.

Set it up once, after the first publish:

1. npmjs.com → the package → Settings → Trusted publishing.

2. Add a GitHub Actions publisher: repository

smithtomge-alt/dsh-shortcuts-prompt, workflow publish.yml, environment