Prompt library
117 prompts, organised by what you're doing
Every prompt here is written to ask for a specific answer rather than a survey. Free to read and copy. Inside SnipTray they're searchable, and the blanks become fields you fill in before pasting.
Explain it to someone new
Plain language, no analogies that need explaining.
Proofread without rewriting
Fix errors only, and show what changed.
Reply that says no
Decline clearly, once, without three paragraphs of cushioning.
Reply to a long email
Answer every question asked, in a fraction of the words.
Rewrite for one specific reader
Same facts, aimed at the person who has to act.
Rewrite in our tone
Match a voice you paste in, not a generic one.
Shorten without losing the point
Cut by half, keep the argument intact.
Subject lines that get opened
Specific over clever, every time.
Thank-you note that isn't generic
Name the specific thing, skip the template.
Tighten this paragraph
Same meaning, fewer words, better rhythm.
Turn a decision into a short doc
What we chose, what we rejected, and why.
Turn notes into an update
Bullet dump in, readable paragraph out.
Write a changelog entry
What changed, from the user's side of the screen.
Review this API surface
How it reads at the call site, and what it lets you do wrong.
Explain this code
What it does, why it might be written this way.
Explain this error
What it means, why it happened here, what to try first.
Find the edge cases
Where this breaks, before a user finds out.
Name this thing
Options that say what it is, with the trade-offs.
First look at a performance problem
What to measure before changing anything.
Refactor without changing behaviour
Smallest safe steps, each one verifiable.
Regex from a description
The pattern, plus what it deliberately excludes.
Review this diff
Correctness pass that insists on a test check.
Write a minimal reproduction
Strip it to the smallest thing that still fails.
Write a commit message from this diff
Imperative subject, a body that explains why.
Write a data migration
Forward path, failure path, and how to verify it.
Write tests for this
Cases that could actually fail, not coverage theatre.
Critique this screen
Hierarchy, affordance, and the one thing to cut.
Dark mode pass
What to change beyond inverting the greys.
Empty state that earns its keep
Explain, then give the one action that fills it.
Empty, loading, and error states
Three states people forget, written together so they agree.
Error message that helps
What went wrong, and the one thing to do about it.
Brief for an icon
What it must read as at 16 points.
Landing page hero section
One promise, one action, no adjective soup.
Mobile version of a desktop screen
What survives the narrow width, and what changes job.
First-run experience
Get to the first real use in as few steps as possible.
Reduce this screen
Find the third of it that isn't earning its place.
Settings screen that scales
Group by what people came looking for, not by subsystem.
Make this table readable
Column order, alignment, and what to cut.
Three-column pricing table
Tiers a visitor can choose between in ten seconds.
Ad variations from one promise
Same claim, several angles, testable against each other.
Cold email that isn't spam
One specific reason you're writing to them.
Compare against a competitor, fairly
Credible because it concedes what they do better.
Ask a customer for a quote
Make it two minutes of their time, not twenty.
Landing page outline
Section order that answers objections as they arise.
Launch post from a changelog
Ship notes turned into something worth reading.
Meta description that gets clicks
155 characters, one promise, no keyword stuffing.
Positioning in one sentence
Who it's for, what it replaces, why it wins.
Press pitch in one paragraph
The story, not the feature list.
Pricing page copy
Make the choice easy and the limits honest.
SEO brief for a new page
Intent first, keywords second.
Social posts from a longer piece
Pull the parts that stand alone.
Apology that lands
Once, specifically, then straight to the remedy.
Bug report from a user complaint
Turn a frustrated message into something a developer can act on.
Canned reply from a help doc
Turn documentation into an answer you can send.
De-escalate a thread that's gone wrong
Reset the conversation without conceding facts.
Escalation reply
Firm, warm, and free of promises we cannot keep.
Explain a bug honestly
What broke, what it cost them, what happens now.
Handover note for a live issue
What the next person needs and nothing else.
Build a macro set for one topic
Three replies that cover the real variants.
Decide and explain a refund
Say yes or no in the first line, then why.
Decline a feature request well
Take the problem seriously, decline the solution.
Triage this ticket
Severity, owner, and the one question to ask back.
Close the loop on a complaint
Tell the person who reported it that it shipped.
Write a help doc from repeated questions
Answer first, steps second, edge cases last.
Build a reading list on a topic
Ordered so each piece prepares the next.
Compare two options honestly
Where each one wins, and what would change the call.
Estimate something, showing the work
A number I can argue with, not a number to trust.
Extract a timeline
What happened when, and what's only inferred.
Extract the facts from a page
Claims and numbers, separated from the pitch.
Find the counterexample
Test a rule by hunting the case it breaks on.
Trace a claim to its source
Who said it first, and did they measure it.
Questions to ask before committing
The ones that are cheap now and expensive later.
Reconcile two sources that disagree
Where they diverge and which to trust.
Turn a vague question into an answerable one
Split it until each part can actually be settled.
Summarize a long thread
What was decided, what is still open, who owes what.
Summarize for a specific decision
Only the parts that change the answer.
What am I missing?
Argue against your own conclusion.
Check this analysis
Where the numbers could be lying.
Clean up this messy column
Find the patterns, then the rule that normalises them.
Turn a CSV into something useful
Understand the shape before transforming it.
Deduplicate records
Decide what counts as the same thing first.
Define a metric precisely
Pin the edges so two people compute the same number.
Explain a number to a non-analyst
What it means and what it doesn't.
Explain this query
What it returns, and where it will hurt.
Model this in a spreadsheet
Inputs, formulas, and the assumption doing the work.
Pick the right chart
Match the form to the comparison being made.
Spot-check a dataset
The five queries to run before trusting it.
SQL from a plain-English question
The query, plus the assumptions it is making.
Why did this number change?
Decompose the move before explaining it.
Write a query that guards a report
Fail loudly when the underlying data drifts.
Agenda from a messy thread
Turn forty replies into a meeting worth having.
Decide between options I'm circling
Force the trade-off into the open.
Hand off to tomorrow-you
Leave a note that makes restarting cheap.
Estimate a piece of work
Break it down until the estimate is boring.
Turn an inbox into a plan
Sort by what it needs from you, not by sender.
Meeting notes to actions
Only the commitments, with owners.
Plan a week that fits
Commit to less than you'd like, deliberately.
Prepare for a hard conversation
Your point, their likely response, your actual goal.
Get out of a commitment gracefully
Own the change, don't over-explain it.
Standup from commits
Yesterday, today, blockers — read off the log.
Triage this backlog
What to do now, what to drop, and why.
Get unstuck on a task
Find the smallest next action that isn't the whole thing.
Weekly review from raw notes
What moved, what stalled, what to drop.
Add the constraints a prompt is missing
Name what you'd reject, then forbid it.
Debug inconsistent output
Find the instruction the model is free to interpret.
Split one prompt into a chain
When one call is doing three jobs badly.
Extract a template from examples
Find what's constant across prompts you've written before.
Improve a prompt that half-works
Diagnose why it drifts, then fix it.
Get output in an exact format
Specify the shape by showing it.
Write a prompt for a colleague to use
Self-contained, with the context they'll forget.
Stop a prompt producing hedged answers
Ask for a position, not a survey.
Shorten a prompt without weakening it
Cut the padding, keep the constraints.
Test a prompt before relying on it
The inputs most likely to embarrass it.
Turn a workflow into a reusable prompt
Capture something you do often, with the right blanks.
Turn feedback into a prompt change
Translate 'not quite right' into a specific edit.
Write a rubric for judging output
Criteria specific enough to disagree with.
Write a system prompt
Durable instructions, not a one-off request.
No prompts match that. Try a shorter word, or .
Browse by category
Drafting, editing, and rewriting — tone matching, cutting length without losing the argument, and turning notes into something readable.
Coding 13Code review, commit messages, tests, naming, migrations, and the debugging prompts that ask for a diagnosis instead of a guess.
Design 13Interface work — sections, empty states, error messages, dark mode, and critique that names the one thing to cut.
Marketing 12Positioning, landing pages, pricing copy, and outreach that gives one specific reason it is being sent to you.
Support 13Replies that decide in the first line — escalations, refunds, declined requests, and bug reports pulled out of a complaint.
Research 13Comparing options honestly, tracing a claim to its source, arguing against your own conclusion, and summarising for a decision.
Data 13SQL from a question, checking an analysis for the ways it could be lying, picking a chart, and defining a metric precisely.
Productivity 13Planning a week that fits, getting unstuck, turning meeting notes into owned actions, and handing off to tomorrow-you.
Promptcraft 14Prompts about prompts — diagnosing why one drifts, adding the constraint it is missing, and testing it before you rely on it.
Use these without the copy-paste
SnipTray keeps the whole library a keystroke away, fills in the blanks, and pastes into whatever app you're in. Your own prompts live alongside them.