How to Save and Reuse Prompts Across ChatGPT, Claude, and Gemini

This isn't the same as custom instructions

ChatGPT's custom instructions, Claude's Projects, and Gemini's Gems all do something related but different: they set standing context that applies automatically to new chats — your role, your tone preferences, facts you want remembered without repeating. That's useful, and it's not what's being covered here.

Saved prompts solve a narrower problem: a request you've written well once and want to reuse exactly, but only when that particular task comes up — not every conversation you have. Custom instructions apply everywhere, all the time. A saved prompt sits in a library until you decide to pull it out.

How to save and reuse a prompt

1. Save it once. Open Settings, go to the Prompts tab, and add a name and the prompt content.
2. Insert it anywhere. In any ChatGPT, Claude, or Gemini conversation, click the Saved Prompts button above the chat input and select it — the text drops into the composer, ready to edit or send as-is.

Worth knowing: saved prompts are free and don't use any AI quota, on any plan. Saving one and inserting it are both unlimited actions — the quota only applies once you actually send a message to the model.

Prompts worth saving

The ones that earn a permanent slot in a library are the ones you'd otherwise retype close to verbatim. A few starting points:

• A code review checklist — the specific things you always want flagged: error handling, naming, obvious performance issues.
• An email tone template — "rewrite this in a direct, friendly tone, no more than 150 words, no exclamation points."
• A meeting-notes structure — decisions, action items with owners, open questions, in that order every time.
• An interview or interview-prep question set — the same five questions you ask every candidate for a given role.
• An "explain this like I'm reviewing it, not learning it" instruction — useful for anything technical you need summarized for a decision, not a tutorial.

The common thread: each one took real effort to phrase well the first time, and each one is generic enough that you'll want the exact same wording again rather than a new version each time.

A worked example

Say you review pull requests a few times a week and always check the same handful of things — but you've never written it down consistently, so every review starts with deciding all over again what to look for. A saved prompt like "Review this diff for: unhandled errors, functions doing more than one thing, magic numbers that should be named constants, and anything that will be confusing to someone reading this in six months" turns a five-minute mental warm-up into a one-click insert.

The value compounds because it's the same checklist every time. A prompt you rewrite slightly differently for each review drifts over time — you catch different things depending on what you happened to type that day. A saved one doesn't drift, and that consistency becomes more valuable the more often you use it.