Prompt library

One home for the prompts you actually use, with their variables pulled out into fields and the previous version kept when an edit makes things worse. Everything is stored in this browser - no account, and no prompt of yours on anyone else's disk.

  • StorageThis browser only
  • Variables{{ double braces }}
  • BackupExport to a JSON file

Prompts

4 stored here

Edit

Write {{ variable }} anywhere and it becomes a field below.

Fill and copy

2 variables in this prompt.

You are reviewing a pull request in a {{language}} codebase.

Diff:
{{diff}}

List only changes that would break an existing caller, with the file and line for each. Ignore style. If nothing would break, say so in one line and stop.
≈ 63 tokens · 2 still unfilled

Why it is stored in your browser

A prompt is often the most specific thing a team owns - it encodes how they talk to customers and what their data looks like. Keeping the library in localStorage means there is no account to breach and no copy of it on anyone else's disk. The trade is that it lives in this browser, which is what Export is for.

Variables, not copies

Ten near-identical prompts with one word changed is how a library rots. One prompt with {{ variables }} stays one thing to improve, and the fields make the differences explicit rather than hidden in the middle of a paragraph.

Versions catch the bad edit

Every time the text changes, the previous body is kept - up to ten back. Prompt edits are hard to judge and easy to regret, and a one-click restore is the difference between experimenting and being careful.

Frequently asked questions

Where are my prompts stored?
In this browser's local storage, on your own machine. There is no account and no server copy - which also means they do not follow you to another browser, so export the JSON file and import it there.
How do prompt variables work?
Write a placeholder in double braces anywhere in the prompt and it becomes a field. Filling the field substitutes the value; anything left empty stays as the placeholder, so what is still missing is visible at a glance.
Why keep versions of a prompt?
Prompt edits are hard to judge and easy to regret. Keeping the previous text means an experiment that made the output worse is one click from being undone, which is the difference between iterating and guessing.
Can I share a prompt library with my team?
Export the JSON file and share it however you already share files. Importing merges by title, so re-importing an updated file does not duplicate anything.