You're a few clicks away from a prompt library that actually works — saved once, organized by workflow, filled with variables, and used everywhere.
This is the practical guide for PromptMate, a free and open-source prompt library built by Jitan Gupta. If you came here wondering what to save, where context belongs, or how to make prompts reusable, start here.
Install PromptMate, connect sync, set context, save your first variable prompt, and use it without leaving the chat page.
Jump to sectionWatch the core workflow, editing flow, history restore, and cross-platform use across ChatGPT, Claude, DeepSeek, and Kimi.
Jump to sectionLearn what belongs in user context, group instructions, prompt body, variables, tone, and format so your library stays clean.
Jump to sectionVariables, groups, group instructions, and user context make saved prompts behave more like reusable tools.
Go to pageSix practical rules for writing prompts that are specific, reusable, easy to test, and worth keeping in your library.
Go to pageCopy-ready prompts for engineers across code review, writing, debugging, and more. Add them to your library in one click.
Go to pageIf you edited a prompt and want an older version back, learn how version history and restore work.
Jump to sectionNo PromptMate account. No product backend. Start with one useful group and one reusable prompt.
Add PromptMate from the Chrome Web Store. Works on Chrome, Brave, Edge, and all Chromium-based browsers.
Connect your private Google Drive folder, then add your role, background, and preferences in User Context so repeated personal framing travels with every prompt.
Make one simple group like Code Review, Writing, or Learning. Add a group instruction only if every prompt in that group should follow the same rules.
Click "New Prompt", write the task, add {{variables}} for changing inputs, choose a tone and output format, then save it to your group.
Open ChatGPT, Claude, DeepSeek, or Kimi. Click "Use", fill the variable dialog, preview the final prompt, and insert it into the chat.
Every prompt in PromptMate carries two signals beyond the text: a tone (formal, casual, technical) and an output format (bullets, steps, prose, code). When you click Use, both are appended automatically — no manual adjustment every session.
Prompts aren't static. Open any saved prompt and edit it mid-session — your changes save back to the library. Every edit creates a version, so you can browse the history and restore any prior version without losing work.
Same sidebar, same library, all four interfaces. Install once and your entire prompt collection is available wherever you work — ChatGPT, Claude, DeepSeek, Kimi. No duplicate setup, no syncing.
PromptMate works best when each layer has a job. Stable background belongs in context, workflow rules belong in groups, and changing inputs belong in variables.
Use this for stable background: your role, stack, preferences, audience, and recurring constraints that apply across many prompts.
Use this for shared rules inside a project or workflow. It keeps repeated setup out of every individual prompt.
This is the core instruction you save: what the AI should do, what to inspect, and what good output looks like.
Use variables for session-specific inputs like {{topic}}, {{diff}}, {{audience}}, or {{error_message}}. Fill them only when you click Use.
Tone controls the voice. Format controls the shape. Set both once so repeated work comes back in a consistent form.
User context: I am a senior engineer working on TypeScript, cloud, and AI tooling. Prefer practical tradeoffs over abstract theory. Group instruction: For code review prompts, prioritize correctness, security, regressions, and missing tests before style feedback. Prompt: Review this pull request for correctness, edge cases, and maintainability. Call out risky assumptions before suggesting changes. Variable values: diff = [the pull request diff you filled in] Tone: Technical and direct. Be precise, avoid fluff, and explain tradeoffs like a senior engineer reviewing the work. Format: Return the answer as a checklist with sections for blockers, important fixes, small improvements, and tests to add.
Small habits that make PromptMate worth keeping open.
Think about instructions you type every week — code review format, email drafts, explaining concepts. Those are your first 5 saves.
If you edit the same part every time you paste a prompt, turn that part into a {{variable}} and let PromptMate ask for it at send time.
Use user context for you, group instructions for a workflow, and prompt text for the task. This keeps prompts shorter and easier to reuse.
Save a rough version, use it, then refine the prompt based on the output. Version history keeps older versions available if a change makes it worse.
Install PromptMate, save the prompts you actually use, and get them back in one click — in ChatGPT, Claude, DeepSeek, or Kimi, every session.