Open Settings → Prompt Presets to manage your library (create / edit / delete with confirmation / reorder), then click the Prompts button next to the model selector in the composer to pick a preset and insert it at the start of your draft — no auto-send, you stay in control.

Features · Screenshots · Compatibility · Install / Uninstall · How It Works · Data & Privacy · Development

Screenshots

Settings page	Composer menu

Features

Compatibility

Install / Uninstall

# From GitHub (recommended)
dsh plugin --profile web add github:zhangdong456/dsh-prompt-presets#main

# From npm
dsh plugin --profile web add dsh-prompt-presets

# From a local checkout
dsh plugin --profile web add file:./dsh-prompt-presets

After installing, restart DeepSeek Harness and press Ctrl+F5 once in the web page. lib/ artifacts are committed, so GitHub installs need no local build.

Your presets live in $DSH_HOME/settings.yaml under the prompt-presets: key and survive install, upgrade, and uninstall.

Quick Start

1. Install the plugin, restart DSH, press Ctrl+F5.
2. Open Settings → Prompt Presets → New Preset → fill in a title and the prompt content → Save.
3. In any conversation, click Prompts above the composer → pick a preset → Insert into composer.
4. Edit the injected text freely, then send as usual.

How It Works

lib/index.js    host half (ESM)      registers the `prompt-presets` settings namespace:
                                     schema validates/coerces every write (id, title ≤ 50,
                                     content ≤ 10 000, timestamps) and normalizes `order`
                                     (dedupe + append missing ids); registration is a fiber
                                     effect, so uninstalling cleans up after itself
lib/client.js   browser half         classic script registering a factory with
                                     window.__ModuleLoader__; React resolves against the
                                     shell's shared module table. Registers two slot rows:
                                       settings.section          → management page
                                       conversation.input.right  → Prompts trigger + menu
                                     Data flows through remote.settings.describe /
                                     .replace with optimistic-revision writes — no custom RPC
cordis.patch.yml                     bundle patch inserting the prompt-presets row

Injection semantics: draft === '' ? preset.content : preset.content + '\n\n' + draft.

Data & Privacy

• Presets are stored locally in $DSH_HOME/settings.yaml. Nothing leaves your machine; the plugin makes no network requests of its own.
• The namespace is plain YAML — you can back it up, sync it, or edit it by hand:

prompt-presets:
  presets:
    - id: p-example
      title: Code review assistant
      content: You are a senior code reviewer…
      createdAt: 1787322246076
      updatedAt: 1787322246076
  order:
    - p-example

• If the settings service is unavailable or the document is read-only, the UI disables editing and says so instead of failing silently.

Development

dsh-prompt-presets/
├── package.json        dsh.bundle manifest + client-half declaration
├── cordis.patch.yml    bundle patch (inserts the prompt-presets row)
├── lib/
│   ├── index.js        host half (ESM, no dependencies)
│   └── client.js       browser half (module-loader factory, plain JS)
└── assets/screenshots/ README images

No build step: both halves are hand-written plain JavaScript committed directly. Fork → edit → dsh plugin --profile web add file:./dsh-prompt-presets → restart DSH.

Contributing. Issues and PRs welcome — please include your DSH version and the exact error text.

License

MIT — see LICENSE.