# Canned Prompts - Quick QoL feature

**URL:** <https://forum.cursor.com/t/canned-prompts-quick-qol-feature/16590>\
**Category:** Feature Requests\
**Created:** [September 13, 2024, 5:45pm UTC](https://forum.cursor.com/t/canned-prompts-quick-qol-feature/16590 "2024-09-13T17:45:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dev-mico](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/dev-mico/32/4738_2.png) [@dev-mico](https://forum.cursor.com/u/dev-mico)\
**Post date:** [September 13, 2024, 5:45pm UTC](https://forum.cursor.com/t/canned-prompts-quick-qol-feature/16590/1 "2024-09-13T17:45:33Z")

</div>

Continuing the discussion from [Context Groups: Defining collections of files as a single context for prompting](https://forum.cursor.com/t/context-groups-defining-collections-of-files-as-a-single-context-for-prompting/7405):

The idea for “canned prompts” here is awesome. tl;dr, the idea is to add an ability to create repeatable prompts to the LLM, possibly with a keybind, a mention (like the @ or # mentions), or a dropdown of some sort.

To expand on this idea, I think the key benefit of having this be a function rather than having the LLM read from another file is that, if the LLM is reading through another file, it won’t retrieve other specific files that we need.

Having a repeatable prompt that allows you to reference the same files repeatedly and prompt the chat would be a huge quality-of-life feature. Tons of repeated operations (e.g., refactor, adding logging, etc) can be done quickly through a single prompt that supplies sufficient context.

---

<div class="post-metadata">

**Author:** ![connor](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/connor/32/8104_2.png) [@connor](https://forum.cursor.com/u/connor)\
**Post date:** [October 11, 2024, 2:06pm UTC](https://forum.cursor.com/t/canned-prompts-quick-qol-feature/16590/2 "2024-10-11T14:06:31Z")

</div>

voicing support for this

---

<div class="post-metadata">

**Author:** ![BryanM](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/bryanm/32/8111_2.png) [@BryanM](https://forum.cursor.com/u/BryanM)\
**Post date:** [October 11, 2024, 3:55pm UTC](https://forum.cursor.com/t/canned-prompts-quick-qol-feature/16590/3 "2024-10-11T15:55:48Z")

</div>

Actually when I first heard about the composer feature in cursor, I thought it was this.

GPTs and Claude Projects are annoying to maintain because the file context you give them isn’t updated automatically.

Our team’s workflow for user stories is to always add a ChatGPT conversation or claude project to the story so that we can always go back to it and make a quick fix or adjustment because the chat already has all the proper context.

The workflow cursor should support is building a saved and organized list of these projects so that you can start working on a particular feature or fix easily without having to regather and resupply context to the chat.

---

<div class="post-metadata">

**Author:** ![litecode](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/litecode/32/2966_2.png) [@litecode](https://forum.cursor.com/u/litecode)\
**Post date:** [October 11, 2024, 4:37pm UTC](https://forum.cursor.com/t/canned-prompts-quick-qol-feature/16590/4 "2024-10-11T16:37:10Z")

</div>

Hi @dev-mico ,

I really enjoyed that thread.

Out of interest, could you explain further why you think this example approach would not do the job?

> [@Context Groups: Defining collections of files as a single context for prompting](https://forum.cursor.com/t/context-groups-defining-collections-of-files-as-a-single-context-for-prompting/7405/12):
>
> @connor, So as an immediate solution you could either: Create 1 file for each canned prompt: canned\_prompt\_1 canned\_prompt\_2 canned\_prompt\_3 Create 1 file that had all the canned prompts within it canned\_prompts And then you could just @ either: the specific canned\_prompt file the single canned\_prompts file (and reference the relevant entry) Example canned prompt files below. Multiple Canned Prompts File # Canned Prompts This file contains canned prompts designed to …

I think you mentioned that you didn’t think `@` ’ing ‘canned prompt’ files would be as good as a UI feature linked to a behind-the-scenes function because the canned prompt files couldn’t reference other required context? Is that a correct understanding of what you were saying?

Have you tried creating `perform_magic.md`, putting some prompts in it, and including some references to other folders or files to see if it can incorporate that context when you ’@perform\_magic.md` in a chat prompt?

I am away from computer but will try tomorrow.

**Edit** :

Some other related posts:

> [@Workaround for lack of memory between chats](https://forum.cursor.com/t/workaround-for-lack-of-memory-between-chats/7605):
>
> I guess this is a combo of showcase, workaround & feature request. I’ve been hoping for project memory to eventually be retained between chats, especially as chat length increases and subsequently degrades the quality of responses. Basically I’ve just created a projectContext.md file top-level in my codebase that describes the project / codebase and any current tasks being worked on. Essentially it just contains any information I would want to be persisted between chats. So I can just @project…

> [@Use @Prompts in Chat for Custom Prompts](https://forum.cursor.com/t/use-prompts-in-chat-for-custom-prompts/357):
>
> Hi Cursor Team, Great job on building an amazing product so far! Since GPT-4 is very steerable, I would love the ability to save and edit custom prompts in Cursor to be able to reuse common instructions and include it in the chat using @Prompts or something similar (just like @Docs for example). I guess this is already possible by maybe creating text files of instructions and using @Files but a dedicated @Prompts tag + add/edit/delete functionality would be much better UX for creating reusabl…

> [@Custom Commands just like in Cody](https://forum.cursor.com/t/custom-commands-just-like-in-cody/17627):
>
> Hey, I would really like to have this feature I use pretty much 95% over entering manual prompts in Cody every day: These are essentially prompts to do repetitive things like cleanup, certain refactoring, optimizations, etc.

> [@Favorite Files - Anyone else use the same @mention files over and over again?](https://forum.cursor.com/t/favorite-files-anyone-else-use-the-same-mention-files-over-and-over-again/15507):
>
> My Usecase: I have a .cursor directory with metaproject scripts and analysis and information, and inside of there I keep track a description.md a roadmap.md and a plan\_of\_action.md that I find myself using over and over and over again. Even if i weren’t doing that specifically, I also have a folder of .md files that I reference so often, I would love to favorite that folder that contains them so that it would bubble up to the top of the drop-down recommendation list and be even easier to click…

> [@Please add an option to branch of from an earlier stage in Composer](https://forum.cursor.com/t/please-add-an-option-to-branch-of-from-an-earlier-stage-in-composer/12679):
>
> Currently in Chat we can go back and modify any request, and it will effectively branch off into a different conversation from there. It doesn’t seem to be possible in Composer at the moment. Please consider adding this, as Composer becomes more and more used, this feature would be extremely helpful and it avoids having to start a new Composer flow and losing the context

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [June 18, 2026, 10:17am UTC](https://forum.cursor.com/t/canned-prompts-quick-qol-feature/16590/5 "2026-06-18T10:17:33Z")

</div>

Closed on June 18, 2026, 10:17am UTC


