Fill-in-the-blank prompts you can steal and use today. Each one is built on the same idea: tell the model the goal, the format, the length, and the audience. Tap copy, paste, swap the brackets.
Understand any topic at the right level, fast.
Explain [TOPIC] to a [AUDIENCE, e.g. curious beginner]. Rules: - Keep it under [WORD COUNT] words. - No jargon. If you must use a term, define it in one line. - Use one everyday analogy. - End with the single most important takeaway.
Turn a long document into something you can actually use.
Summarize the text below. Format: - 5 bullet points, each under 15 words. - Focus on decisions, numbers, and action items. - Add a one-line "bottom line" at the end. Text: [PASTE TEXT]
Get real critique instead of polite agreement.
Review the [PLAN / DRAFT / IDEA] below as a skeptical [ROLE, e.g. investor, editor]. - List the 3 biggest weaknesses. - Give one concrete fix for each. - Be blunt. Skip the praise. Here it is: [PASTE]
Make AI writing sound like you, not a robot.
Here is a sample of my writing so you can match my voice: [PASTE 2-3 PARAGRAPHS YOU WROTE] Now write [WHAT YOU NEED] in that same voice. Topic: [TOPIC] Length: [WORD COUNT] Keep sentences short and plain. No em-dashes.
Rewrite text to a clear, specific standard.
Rewrite the text below. - Reading level: [e.g. 6th grade] - Voice: active - Sentences under 15 words - Keep every fact unchanged - Tone: [e.g. warm but professional] Text: [PASTE TEXT]
Get usable ideas, not 50 generic ones.
Give me [NUMBER] ideas for [WHAT]. Constraints: - [CONSTRAINT 1, e.g. one or two words each] - [CONSTRAINT 2, e.g. avoid the word "smart"] - Aimed at [AUDIENCE] Format: a numbered list, each with a one-line reason it works.
Pull clean data out of messy text.
From the text below, extract these fields as JSON with exactly these keys: [field1, field2, field3]. - If a field is missing, use null. - Do not invent values. Text: [PASTE TEXT]
Compare options fairly and get a clear call.
Help me choose between [OPTION A] and [OPTION B]. - Compare on: [criterion 1], [criterion 2], [criterion 3] - I am a [YOUR SITUATION, e.g. solo founder on a budget] - Show a short comparison table - Then give one recommendation with the reason.
Turn an overwhelming task into today-sized steps.
I want to [GOAL] but I do not know where to start. Give me a numbered checklist: - [MAX NUMBER] steps - Each step is one action I can do today - Note which steps need [a tool / money / help] - Mark the one step that unblocks everything else.
Stop the model from making things up.
Using only the information in the document below, answer this question: [QUESTION]. - If the answer is not in the document, say "not stated in the source." - Do not use outside knowledge. - Quote the exact line you based your answer on. Document: [PASTE]
A ready-to-send email in the right tone.
Write a [LENGTH, e.g. 3-sentence] email to [WHO]. Goal: [WHAT YOU WANT TO HAPPEN] Tone: [e.g. friendly but firm] Include: [KEY POINT 1], [KEY POINT 2] End with a clear next step. Sign as [NAME].
Turn notes or a transcript into next steps.
Turn the notes below into: 1. A 3-line summary 2. A list of decisions made 3. A list of action items with an owner and a due date each (guess owners if unclear and flag your guesses) Notes: [PASTE NOTES OR TRANSCRIPT]
Get code you can actually run and understand.
Write a [LANGUAGE] function named [NAME] that [WHAT IT DOES]. - Inputs: [INPUTS] - Output: [OUTPUT] - Handle this edge case: [EDGE CASE] - Include 3 example calls with expected results - Add a one-line comment above the tricky part explaining why.
Understand and fix an error, not just patch it.
I am getting this error: [PASTE FULL ERROR] Here is the relevant code: [PASTE CODE] Please: 1. Explain in plain English what is going wrong and why. 2. Give the corrected code. 3. Tell me how to avoid this class of bug next time.
A ready-to-paste posting plan.
Make a [NUMBER]-week content calendar as a table. Columns: Date, Channel, Topic, Call to action - One row per [weekday / posting day] - Audience: [WHO] - Theme: [OPTIONAL THEME] Keep topics specific, not generic.
Draft honest FAQs from your own material.
Based only on the product info below, write [NUMBER] frequently asked questions with clear, short answers. - Answer only from the info provided. - If something common is not covered, list it separately as "gaps to fill." Product info: [PASTE]
Define an agent's identity before you build it.
You are [NAME], [ROLE] for [WHO IT SERVES]. Voice: [e.g. warm, calm, plain-spoken]. [Any voice rules]. Job: [the main things it does, in one or two lines]. Rules: - [Hard rule 1, e.g. never give medical or legal advice] - [Hard rule 2, e.g. if unsure, say so and ask] - [Hard rule 3, e.g. never share internal notes] When you cannot help, [what it should do instead].
Get the model to plan tool calls before acting.
You have these tools: [tool 1: what it does], [tool 2: what it does]. For the task below: 1. Think step by step about what you need. 2. Say which tool you will use and why, before each call. 3. After each result, decide the next step. 4. Stop when the goal is met and summarize what you did. Task: [TASK]
A repeatable prompt for a recurring report.
Every [FREQUENCY], produce a digest of [SOURCE, e.g. these updates]. Format: - Top 3 things that matter, one line each - One thing that needs my decision, phrased as a question - Anything that changed since last time Keep it under [WORD COUNT] words. Facts only. Flag anything you are unsure about. Input: [PASTE OR CONNECT SOURCE]