Prompt library
Save and organize prompts in this browser. Nothing leaves the device.
Runs in this tab. The file stays here.
Code review
CodingReview the following code for bugs, security issues, and readability. List problems by severity, quote the relevant lines, and suggest a concrete fix for each. Do not rewrite the whole file. <code> {{code}} </code>
Explain code
CodingExplain what this code does to a developer who has never seen the codebase. Start with a one-sentence summary, then walk through the main steps, then note any surprising behaviour. {{code}}
Write unit tests
CodingWrite unit tests for the function below using {{framework}}. Cover the happy path, edge cases, and error handling. Keep each test focused on one behaviour and name tests after what they check. {{code}}
Refactor safely
CodingRefactor this code to reduce duplication and improve naming without changing behaviour. Show a before/after for each change and explain why. Flag anything you are not sure is behaviour-preserving. {{code}}
Debug an error
CodingI get this error: {{error}} Relevant code: {{code}} List the three most likely causes in order, how to confirm each, and the fix. Ask me for more information if you need it.
Commit message
CodingWrite a commit message for this diff. Use the imperative mood, a subject under 72 characters, and a short body explaining why the change was made, not what. {{diff}}
Summarize
WritingSummarize the text below in {{n}} bullet points. Keep names, numbers, and dates exact. End with one sentence on what action, if any, the reader should take. {{text}}
Rewrite in plain English
WritingRewrite the text below in plain English at about an 8th-grade reading level. Keep the meaning, drop jargon, and use short sentences. {{text}}
Draft an email reply
WritingDraft a reply to the email below. Tone: {{tone}}. Keep it under 120 words, answer every question asked, and end with a clear next step. {{email}}
Proofread
WritingProofread the text below. Fix spelling, grammar, and punctuation only. Return the corrected text, then a short list of what you changed. {{text}}
Pros and cons
AnalysisCompare these options for {{goal}}: {{options}}. For each, give pros, cons, and the situation where it is the best choice. Finish with a recommendation and the main assumption it depends on.
Extract to JSON
AnalysisExtract the following fields from the text and reply with JSON only, no commentary: {{fields}}. Use null for anything not stated. Do not guess. {{text}}
Insights from data
AnalysisHere is a CSV sample: {{csv}} Describe the columns, point out data quality problems, and suggest three questions this data could answer.
Plan before acting
AgentsBefore making changes, restate the task in your own words, list the files you expect to touch, and describe your plan in numbered steps. Wait for my approval before editing anything.
Verify your work
AgentsAfter finishing, run the project's tests and linter, report the exact commands and results, and list anything you could not verify. Do not claim success if a check failed or was skipped.
Replace the {{placeholders}} with your own content before sending.
This runs in your browser. Nothing is uploaded.
About Prompt library
Browse fifteen ready-made prompts for coding, writing, analysis, and agents, search them, and copy one. The prompts are built into the page.
This is a small, fixed shelf of prompts, not a place to store your own. Fifteen are included in four groups: Coding (code review, explain code, write tests, safe refactor, debug an error, commit message), Writing (summarise, plain-English rewrite, email reply, proofread), Analysis (pros and cons, extract to JSON, insights from a CSV), and Agents (plan before acting, verify your work). Pick a group or search the titles and text, and click Copy.
Most contain {{placeholders}} such as {{code}}, {{text}}, or {{tone}}. Replace them with your own content before you send the prompt, because a model will take the braces literally. They are written to be specific. They say what to return, what not to do, and when to stop and ask, because a prompt that spells out its own limits tends to be easier to get right.
You can't edit the list, add your own prompts, or save anything, and there's no account or storage. If you want to keep a variation, copy it into a notes app or a file in your repo. The library is a starting point for wording, not a recommendation about which model to use: try a prompt on your own data before relying on it.
How to use Prompt library
- 1Choose a group or type in the search box.
- 2Click Copy on the prompt you want.
- 3Replace each {{placeholder}} with your own content, then send it.
What it won't do
- Fifteen fixed prompts in four groups; you can't add, edit, or delete them.
- No saving, sync, or export.
- Starting points only; test them on your own material.
Common questions
Can I save my own prompts here?
No. The fifteen prompts are built in and the page stores nothing. Keep your own in a notes app, a snippets manager, or a file in your repository.
What are the {{placeholders}}?
Markers for the content you supply, such as the code to review or the text to summarise. Replace the whole marker, braces included.
Are these prompts tuned for a particular model?
No. They are written in plain instructions that work reasonably on most chat models. Expect to adjust wording for your model and your data.
Related tools
Why this one doesn't upload your file
There is no server to upload to. This page is a static file, and the work happens in your browser using the same graphics and WebAssembly code that renders every other site you visit. Your file is read from disk into memory, processed, and handed back as a download. Once the page has loaded you can disconnect from the network entirely and it keeps working. The longer explanation