[Feature]: Saved snippets for frequently used prompts, with optional grouping

[Rhiz3K]

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

Add support for user-defined saved snippets in the composer.

Proposed solution

Values:

• name
• content
• optional group / category

Expected behavior:

• snippets are searchable from the composer
• selecting one inserts it into the current input
• it does not auto-send

Triggers:
"/s" command or dedicated button

Why this matters

This would speed up repetitive workflows and remove a lot of copy-pasting from external notes.

It’s especially useful for people who repeatedly run the same PR/review/CI prompts and want them to stay consistent.

Smallest useful scope

The smallest useful version is just:

• create, edit, and delete saved snippets
• search them from the composer
• insert them into the current input without auto-send

Alternatives considered

Current workaround is keeping these prompts in notes, a text file, or another app and pasting them in manually.

Risks or tradeoffs

Main tradeoffs are added composer complexity and avoiding overlap/confusion with skills, slash commands, or automations.

Examples or references

Termius snipets:

Example snippets:

• update the PR summary based on the current state
• review all PR comments, validate them, and implement the valid ones
• reply to PR comments and resolve them
• update the changelog with everything changed in this PR vs main
• wait for CI to finish, then inspect and fix all failed jobs

Contribution

• I would be open to helping implement this.

[Sypher760-gif]

This is something I'd use a lot. I'd like to save prompts I reuse and pick them from a list beside the message box, rather than keep retyping them.

I found Cult UI's Prompt Library, which is close to what I have in mind. You can search saved prompts, browse by category, and add or delete your own. Picking one puts it into the input without sending, so you can make changes first.

Would the T3 maintainers be open to this? I'd be happy to contribute an implementation once you approve the direction and initial scope. The link is just an example of the interaction, not a suggestion that T3 needs to use that component.