[Feature]: Add one-click buttons for frequently used skills and insults

[Defmon3]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/web

Problem or use case

Users repeatedly invoke the same small set of skills and short prompts while directing agents. Today they must reopen the skill picker or retype the same text each time, even when those actions are used throughout a project.

Proposed solution

Add a project-specific row of customizable quick slot buttons above the composer. Users can add, remove, and reorder slots. Selecting a slot immediately submits its stored skill invocation or text through the same path as a manually entered message.

Why this matters

Quick slots reduce repetitive typing and picker friction while keeping frequently used, project-specific actions within one click.

Smallest useful scope

Support persistent quick slots in the web composer for the current project. Each slot needs a label and submitted value, plus add, remove, and reorder controls. Selecting a slot should immediately send its value through the active provider.

Alternatives considered

Issue #1547 proposes searchable saved prompt snippets that are inserted into the draft without sending. That helps with reusable text, but it does not provide persistent one-click actions for a project's most frequently used skills and prompts.

Risks or tradeoffs

Immediate submission makes accidental activation possible, so quick slots must be visually distinct from ordinary composer text and remain easy to remove or reorder. The row should also avoid taking excessive composer space.

Examples or references

Contribution

• I would be open to helping implement this.

[CPaxman]

+1 from me. Below is a concrete spec, written so this can be picked up with little or no extra design work. Prior art: the Paseo quick-prompts plugin, which I use daily. File paths below are from a read of main, so please sanity-check them.

Why mobile matters most

Long-running agent loops often need nothing more than "continue" between turns. On a phone that means opening the keyboard, typing and sending, every time. With a quick prompt pill it becomes two taps: tap the pill, tap "Continue". No keyboard.

Behaviour

• One "Prompts" pill in the composer footer, left of the model picker (ComposerFooterControls.tsx on web, ComposerToolbar.tsx / ThreadComposer.tsx on mobile). It opens a menu listing saved prompts by label, with a one-line preview on desktop, and ends with a separator and Manage prompts (opens settings).
• Display mode setting: menu (default, a single pill and best on mobile) or pills (one pill per prompt in a horizontally scrollable row above the composer, which is what this discussion originally proposed).
• Selecting a prompt sends it immediately as a normal user message through the same path as the send button. Same queueing rules apply: if a turn is running, it follows whatever the composer does today for a send during a turn (queue or steer).
• Edit before sending: Shift+click (desktop) or long-press (mobile) inserts the prompt text into the composer instead of sending. If the composer already has text, append on a new line rather than replace.
• Guard against double sends: while a send from a given prompt is in flight, ignore repeat presses of that prompt (Paseo keys this on agent + prompt id).
• Empty state: with no prompts saved, the pill reads "Add quick prompt" and opens settings.
• Hidden in the new-thread composer for v1 (Paseo does the same), or shown. Either is fine; just pick one.

Data model

Store in server settings so desktop, web and mobile share one list, with a per-project override. In packages/contracts/src/settings.ts:

export const QuickPrompt = Schema.Struct({
  id: TrimmedNonEmptyString,            // generated client side
  label: TrimmedString,                 // 1 to 40 chars
  text: TrimmedString,                  // 1 to 10,000 chars
});

export const QuickPromptDisplay = Schema.Literals(["menu", "pills"]);

// in ServerSettings
quickPrompts: Schema.Array(QuickPrompt).pipe(/* max 20, unique ids */),  // default []
quickPromptDisplay: QuickPromptDisplay,                                  // default "menu"

// in ProjectSettingsOverrides
quickPrompts: Schema.optionalKey(Schema.Array(QuickPrompt)),

Resolution: if the project override is set, use it; otherwise use the global list. Unknown quickPromptDisplay values should fall back to "menu" so older clients don't break.

Suggested defaults (useful straight away, and they show people what the feature is for):

Label	Prompt
Continue	Continue with the next step. If you're blocked or need a decision from me, stop and say exactly what you need.
Status	Give me a short status: what's done, what's in progress, what's next, and any blockers or risks.
Review diff	Review your current diff for bugs, regressions, missing tests and leftover debug code. Fix what you find, then summarise what changed.
Commit + PR	Commit your work with focused, descriptive messages, push the branch, and open a PR with a summary and verification notes. Do not merge.

Settings UI

A "Quick prompts" section (web: new panel under apps/web/src/components/settings/; mobile: a SettingsQuickPromptsRouteScreen.tsx next to the others in apps/mobile/src/features/settings/):

• One row per prompt: label input, multiline prompt input (grows to about 5 lines, then scrolls), move up, move down, delete.
• Last row is blank, with an Add button.
• "Show prompts as": Single menu pill / Separate pills.
• On a project's settings page: "Use custom quick prompts for this project" toggle, which copies the global list as a starting point.
• Inline validation (label 1 to 40, prompt 1 to 10,000, max 20). Save on blur and on reorder/delete, matching how other settings save.
• Nice extra from Paseo: Export / Import as JSON for moving lists between machines.

Keyboard (desktop)

• A keybinding to open the Prompts menu (e.g. mod+shift+p or whatever is free in the keybindings config); arrow keys plus Enter to send, Shift+Enter to insert.
• Optional: mod+1 to mod+9 send the first nine prompts when the composer is focused.

Accessibility

• The pill is a menu button (aria-haspopup="menu"); items are menuitems with the full prompt text as the accessible description.
• Mobile menu rows need at least 44 pt tap targets.

Out of scope for v1, worth considering later

• Prompts that invoke a skill or slash command (the original ask mentions skills). Since the text goes through the normal send path, /skill-name args may already just work.
• An optional "auto-continue N times" with a visible stop button for unattended loops.

Mockups

A few rough mockups of how this could look. The dashed orange outline only marks where the feature sits; it isn't proposed styling.

Desktop: a single Prompts pill next to the model picker, opening a menu of saved prompts.

Mobile: the same pill with larger tap targets. Two taps to tell a long-running agent to keep going, with no keyboard.

Settings: add, edit and reorder prompts, choose between one menu pill or separate pills, and set the list globally or per project.