Prompts that do real work

Turns jargon-heavy text into something anyone can read, keeping every fact.

Rewrite the text below so a busy reader understands it on the first pass. Keep every fact, number and name. Use short sentences and everyday words. Do not add anything new.

Text:
[text]

Turns rough notes into a post with a hook, three points and a question.

Write a LinkedIn post from these notes. Open with one line that makes people stop scrolling, then three short points, then end with a question for the comments. No hashtags, no emojis, under 180 words.

Notes:
[notes]

Drafts a clear, polite reply that answers every question asked.

Draft a reply to this email. Answer every question it asks, in order. If something needs information you don't have, write [ASK: what you need] instead of guessing. Sign off as [me].

Email:
[email]

Answers a customer using only your help notes, and flags when a human should step in.

Write a reply to the customer below using only the help notes. If the notes don't cover their question, say a teammate will follow up and do not guess. End with one line on what happens next.

Help notes:
[notes]

Customer message:
[message]

Sorts a ticket by type and urgency, with a one-line summary for the queue.

Read this ticket and reply with JSON: {"category": one of "billing", "bug", "how-to", "account", "other", "urgency": "high", "normal" or "low", "summary": one sentence, "needs_human": true or false}.

Ticket:
[ticket]

Reads a batch of reviews and pulls out the mood and the recurring themes.

Read these reviews. Give the overall mood in one line, then the three themes that come up most, each with a short quote. Then one thing to fix first.

Reviews:
[reviews]

A five-line summary with the decisions, numbers and open questions.

Summarise the document below in five bullet points: what it is about, the key decisions, the important numbers, who needs to act, and open questions. Quote numbers exactly.

Document:
[text]

Weighs two to four options against your criteria and picks one, with reasons.

Compare these options against my criteria. Make a small table, one row per option, then recommend one in two sentences and say what would change your mind.

Options:
[options]

Criteria:
[criteria]

Turns a transcript or messy notes into decisions and a to-do list with owners.

From these meeting notes, list: decisions made, action items as "Owner: task (due date)", and open questions. If an owner or date wasn't said, write "unassigned" or "no date".

Notes:
[notes]

Extracts names, emails, dates and amounts into clean JSON for the next step.

Extract these fields from the text and reply with JSON: {"name", "email", "company", "date", "amount"}. Use null for anything that isn't there. Dates as YYYY-MM-DD.

Text:
[text]

Labels each item with one of your categories and a confidence.

Put this item in exactly one of these categories: [categories]. Reply with JSON: {"category": ..., "confidence": "high", "medium" or "low", "why": one short sentence}.

Item:
[item]

De-duplicates, fixes capitalisation and formats a messy list consistently.

Clean up this list: remove duplicates (including near-duplicates), fix capitalisation and spacing, and put one item per line in alphabetical order. Don't add or drop real items.

List:
[list]

Ten headline options in different styles for a page, ad or email subject.

Write ten headlines for [product], aimed at [audience]. Mix styles: benefit, number, question, how-to and outcome. Each under 70 characters. Mark the two you would test first.

Turns a blog post or video script into posts for five channels.

Turn this into five posts: an X thread (4 posts), a LinkedIn post, an Instagram caption, a short newsletter blurb and a YouTube Short script (30 seconds). Use only facts from the source.

Source:
[source]

Builds a persona from real interview notes: goals, pains and the words they use.

Build a customer persona from these interview notes: who they are, what they are trying to get done, what gets in the way, and the exact phrases they use. Mark anything you inferred rather than read.

Notes:
[notes]

Explains what a piece of code does, line by line where it matters, and flags risks.

Explain what this code does for someone who knows the basics. Then list anything risky: bugs, security issues, edge cases. Keep it short.

Code:
[code]

Writes a regular expression for what you describe, with examples that should and shouldn't match.

Write a JavaScript regular expression that [goal]. Give the regex, a one-line explanation, then five strings that should match and five that should not.

Turns a brain dump into a realistic week, biggest things first.

Here is everything on my plate and my fixed meetings. Plan my week: pick the three things that matter most, put them in the mornings, fit the rest around the meetings, and tell me what to drop or delegate. Assume [hours] focus hours a day.

On my plate:
[todo]

Fixed meetings:
[meetings]