Prompt Template Library

Cold outreach email

Write a short cold outreach email to [recipient's role, e.g. "a marketing director at a mid-size retail company"] introducing [your product/service] and its main benefit: [benefit]. Keep it under 120 words, no generic flattery, and end with a low-commitment call to action (like a quick question, not a meeting ask).

Tip: Paste in 2-3 real facts about the recipient's company for a noticeably better result than a fully generic version.

Handling a pricing objection

A prospective client said: "[paste their objection]" in response to our pricing for [product/service]. Write a short, non-defensive reply that acknowledges the concern, reframes value without being pushy, and ends with one clear next step.

One-page business plan outline

Draft a one-page business plan outline for [business idea in one sentence]. Include: problem, target customer, solution, revenue model, biggest risk, and first 90-day milestone. Keep each section to 2-3 sentences.

Meeting follow-up summary

Turn these raw meeting notes into a clean follow-up email: [paste notes]. Structure it as: brief recap, decisions made, action items with owners, and open questions. Professional but not stiff.

Customer win-back email

Write a short win-back email to a customer who hasn't purchased from [business type] in [timeframe]. Acknowledge the gap honestly, offer one specific reason to come back ([offer/update]), and keep the tone warm, not desperate.

Landing page headline options

Generate 8 distinct headline options for a landing page selling [product/service] to [target audience]. The core benefit is [benefit]. Vary the angle across the options — some benefit-led, some curiosity-led, some direct — rather than just rephrasing the same one.

Repurpose a long article into social posts

Turn this article into 5 standalone social media posts, each highlighting a different specific takeaway (not just a summary of the whole thing): [paste article text or key points]. Keep each post under 280 characters.

Email subject line testing set

Write 6 email subject lines for a campaign about [topic/offer]. Include a mix: 2 direct/clear, 2 curiosity-driven, 2 urgency-driven — no clickbait that the email itself wouldn't deliver on.

Product description

Write a product description for [product name], a [one-sentence description]. Target customer: [audience]. Lead with the main benefit, not the features, then list 3 supporting details. Tone: [e.g. "confident but not salesy"].

Press release draft

Draft a press release announcing [news: launch/partnership/milestone]. Include a headline, dateline, a strong opening paragraph covering who/what/when/why it matters, one quote placeholder from [role, e.g. "the CEO"], and boilerplate placeholder at the end.

Get direct feedback, not a rewrite

Give me direct feedback on this writing — don't rewrite it. Focus specifically on: clarity of the main argument, where the structure loses momentum, and any places tone shifts unexpectedly. Explain briefly why each point matters: [paste your text]

Explain, don't just summarize

Explain [topic] to me like I'm smart but new to this specific subject. Don't just summarize — build up the reasoning, use one concrete example, and flag anything commonly misunderstood about it.

Tighten a draft without losing meaning

Tighten this text by roughly 30% without cutting any of the substantive points. Cut filler and redundancy, not ideas: [paste text]

Match a specific tone

Rewrite this in a [tone, e.g. "warm but professional"] tone, keeping the same core content and length: [paste text]. Afterward, briefly note what specifically you changed to shift the tone.

Difficult email draft

Help me draft a [type of difficult email, e.g. "resignation letter" / "complaint" / "declining an offer"]. Key facts to include: [facts]. Tone: direct and respectful, no unnecessary apology or over-explaining.

Explain unfamiliar code

Explain what this code does, step by step, and flag anything that looks like a potential bug or edge case it doesn't handle: [paste code]

Code review before committing

Review this code as if you were a careful senior engineer doing a pull request review. Check for: correctness, edge cases, naming clarity, and anything that would confuse someone reading it in 6 months. Be specific, not generic: [paste code]

Write unit tests

Write unit tests for this function, covering the normal case, at least 2 edge cases, and one invalid-input case. Use [testing framework]: [paste function]

Debug a specific error

I'm getting this error: [paste exact error message]. Here's the relevant code: [paste code]. What's the most likely cause, and what's the smallest fix that addresses it without changing unrelated behavior?

Convert code between languages

Convert this [source language] code to idiomatic [target language] — not a literal line-by-line translation, but code a [target language] developer would actually write: [paste code]

Product mockup prompt

A realistic product photo of [product] on [surface/setting], soft natural lighting, shallow depth of field, minimal background clutter, high resolution, commercial product photography style.

Brand-consistent illustration

A flat vector illustration of [subject], using a [color palette, e.g. "warm orange and navy"] color scheme, clean simple shapes, no gradients, in the style of modern tech-brand illustration.

Social media header image

A wide banner image for [platform, e.g. "a LinkedIn header"] representing [theme/industry], professional and modern, plenty of negative space on the [left/right] side for text overlay, no text in the image itself.

Concept art starting point

Concept art of [subject/scene], [mood, e.g. "moody and atmospheric"], [art style, e.g. "digital painting, cinematic lighting"], wide shot, highly detailed environment.

Iterating on a generated image

Keep the composition and subject the same, but change [one specific element, e.g. "the background color to deep blue"] and make [another specific adjustment]. Don't change anything else about the image.

Tip: Changing one specific thing per request gets more predictable results than a broad 'make it better' follow-up.

Meeting notes to action items

Turn these raw meeting notes into a clear list of action items, each with an owner (if mentioned) and any deadline mentioned. Flag anything that sounds like a decision was made but the owner wasn't specified: [paste notes]

Prioritize a task list with real context

Here's my task list with context on each: [paste tasks with deadlines/stakes/dependencies]. Suggest a priority order and briefly explain the reasoning for the top 3, specifically calling out any dependencies between tasks.

Summarize a long document, with citations

Summarize the key points of this document in [5-7] bullet points. For each point, note which section of the source it came from so I can verify it: [paste document text]

Prepare talking points for a hard conversation

I need to have a conversation about [topic] with [role, e.g. "a coworker" / "my manager"]. Context: [brief context]. Help me prepare 3-4 talking points that are direct but not confrontational, plus one likely pushback and how to respond to it.

Learn a new topic efficiently

I want to learn [topic] well enough to [specific goal, e.g. "have an informed conversation about it at work"]. Give me a study plan: the 5 core concepts to understand first, in order, and one good way to test whether I actually understand each one.