@stmol/dsh-prompt-lib

Usage

1. Open Settings → Prompts. It is its own page, after Agent presets. Write a title and an instruction, then save.
   • The title is a label for you. The list, the search field and the composer picker use it to keep prompts findable. It is never sent to the model, only the instruction text is.
   • The instruction is stored in the plugin's config, so it survives restarts and is there in every session.
   • Enable in every new chat marks the prompt as a default. It is off unless you turn it on.
2. In a chat, open the Prompts control in the composer tool row, right of the permissions dropdown. Tick what you want. The button shows the count.
3. The ticks apply from the next model step. No restart and no new session needed. Tick again, or press Clear, to take them out.

Prompts are matched by an id generated behind the scenes, not by title, so renaming a prompt keeps every session pointed at it.

Defaults for new chats

A prompt can be set to start enabled. Every session that has never been ticked by hand opens with those defaults already on, and the picker shows them ticked, so the count on a fresh chat matches what that chat will use.

The first hand edit to a session, whether that is ticking, unticking or Clear, becomes that session's own choice and takes over from then on. Unticking the last default prompt records "none here" instead of falling back to the defaults you just removed.

Subagents

A session that has ticks of its own uses exactly those, and an empty list counts as a choice. A session with no choice at all takes the choice of the nearest ancestor session, so a subagent inherits from the chat that started it. Only a whole line with no choice anywhere falls back to the defaults for new chats.