31 prompts to start from

Proofread the following text for grammar, spelling and punctuation. Return only the corrected text, with no preamble and no explanation. Keep the author's voice and do not shorten it. Text:

Rewrite the following text to be about half as long, keeping every fact and the same tone. Do not add a summary line. Return only the rewritten text. Text:

Rewrite the following text so it reads as warm and human without becoming informal or adding filler. Do not add greetings that were not there. Return only the rewritten text. Text:

Rewrite the following text in plain English at roughly a 12-year-old reading level. Keep all the meaning; drop the jargon, or explain it inline the first time. Return only the rewritten text. Text:

Turn the following rough notes into a short, professional email. Infer a sensible subject line and put it on the first line. No filler openings, no "I hope this finds you well". Return only the email. Notes:

Write a reply to the following message. Match its register. Answer every question it asks, say clearly what happens next, and keep it under 150 words. Return only the reply. Message:

Write revision notes on the following topic. Use headings, short bullets and bold for key terms. Include what it is, the mechanism or sequence, and a short section on what exams usually test. Aim for 200-250 words. Topic:

Explain the following in plain language, as if to a smart person outside the field. Lead with a one-sentence answer, then the two or three things worth knowing. No preamble. Text:

Write a quiz from the following brief. Use four plausible options per multiple-choice question, make at least one question require reasoning rather than recall, and put the answer key at the end. Brief:

Turn the following into a lesson plan with timings that add up to the stated length. Include a starter, two activities, a discussion question, and homework. Brief:

Turn the following marking shorthand into feedback addressed to the student. Name one thing that worked, be specific about what did not, and end with the two changes to make next time. Under 200 words. Notes:

Turn the following into flashcards, one per line, in the format "question | answer". Cover every distinct fact. No preamble. Text:

Write documentation for the following code: a one-line summary, arguments, return value, exceptions raised, and a note on any edge case a caller would get wrong. Then list test cases as input → expected output, including the edge cases. Code:

Explain what the following code does, in order, in plain language. Call out anything surprising or likely to be a bug. Do not rewrite it. Code:

The following code has a bug. State what the bug is, what input triggers it, and the smallest fix. Show only the changed lines. Code:

Explain the following error: what actually failed, the most likely causes in order of likelihood, and the first thing to check. Be concrete. Error:

Write a conventional-commit message for the following change. Subject line under 72 characters, imperative mood, then a body explaining why rather than what. Return only the message. Change:

Review the following code as a senior engineer would. List only real problems — correctness, then edge cases, then clarity. No style nitpicks, no praise. Cite line content when you refer to it. Code:

Turn the following into a weekly update with these sections: Headline (one sentence), Shipped, Blocked, What that means, Next week, and one Ask. Be specific and do not pad. Notes:

Extract the decisions and action items from the following meeting notes. Format as: Decisions (one line each), then Actions as "owner — action — by when". If an owner or date is missing, write "unassigned". Notes:

Turn the following into a short decision record: context, the options considered, what was decided, what it costs, and when it should be revisited. Under 200 words. Decision:

Turn the following blunt note into feedback for a 1:1. Lead with the specific thing that is working. Name the problem once, with an example. End with a question rather than an instruction. Note:

Rewrite the following for an executive audience: three sentences maximum, lead with the outcome, no implementation detail, and state explicitly whether anything is needed from them. Text:

Turn the following shorthand into a job post with: about the role, what you will do, what we look for, nice to have, and how we hire. Concrete and specific, no "rockstar", no "fast-paced environment". Shorthand:

Turn the following interview notes into a structured debrief: one section per competency with the evidence, then a recommendation stated separately from the evidence. Flag anything you could not assess. Notes:

Write a rejection email from the following notes. Be brief, be human, give one specific and true reason, and do not offer feedback you cannot substantiate. No "we were impressed by the calibre". Notes:

Turn the following into an internal announcement: what is changing, when, why, what changes for whom, and a short FAQ answering the four questions people will actually ask. Change:

Turn the following shorthand into a customer reply. Apologise once if an apology is warranted, say what you have already done, explain what actually happened without blaming anyone else, and state what happens next. Shorthand:

Turn the following into a reusable canned response: the honest reason, the realistic timeline, and the one thing the customer can do to speed it up. Neutral tone, no company-speak. Topic:

Turn the following call notes into a follow-up email: repeat their concerns back in their words, answer the one they cared most about, and propose the next meeting with a short agenda. Notes:

Write a response to the following objection. Concede whatever is genuinely true, answer the real concern underneath it, and end with a question. Do not oversell. Objection: