Starter prompts that earn their keep.

The move: forces a decision, not a menu.

I need to choose between the following options for {context}: {list}. Compare them on the factors that matter most for my situation. End with a clear recommendation and your main reason.

The move: demands a recommendation at the end — stops Claude at "here are the pros and cons" and makes it take a position.

Compare {option A} and {option B} for {specific context or use case}. Show the pros and cons of each in a table. Then give me your recommendation and the main reason for it.

The move: the "key decisions" field focuses the meeting on outcomes, not updates.

Draft a meeting agenda for a {length} meeting. Topic: {purpose}. Attendees: {roles or names}. Key decisions to make: {list}. Format with time blocks for each section.

The move: anchors the output in your tone by specifying audience, topic, and explicit tone — Claude doesn't have to guess.

I need to send an email to {recipient and their role} about {topic}. The tone should be {professional / friendly / direct}. Here are the key points I want to make: {list your points, one per line}. Write a draft email I can review and send.

The move: word limit forces real simplification, not just shorter jargon.

Explain {topic or concept} as if I have no background in it. Plain language, no jargon, under 200 words.

The move: forces owner and deadline attribution — catches "someone should do X" ambiguity.

Read the following meeting transcript or notes. Extract every action item. For each one, list: who is responsible, what the task is, and any deadline mentioned. If no deadline was stated, write "no deadline given."

{PASTE TEXT HERE}

The move: separates quantities from narrative — the numbers are what you'll re-use.

Read the following and pull out all the important numbers, dates, or financial figures. Present them as a simple list with a one-line explanation for each.

{PASTE TEXT HERE}

The move: volume forces Claude past the obvious three — ideas 7–10 are usually where interesting options live.

Generate 10 ideas for {topic or challenge}. Be specific and practical. Don't explain each one — just list them.

The move: gives Claude a narrow editing lane — fix clarity, don't rewrite the argument.

Edit the following for clarity and readability. Do not change the meaning or tone. Fix awkward sentences, passive voice, or unnecessary jargon.

{PASTE TEXT HERE}

The move: adjectives anchor the vibe; ranking by preference lets you sanity-check Claude's taste.

I need a name for {what it is and who it's for}. The name should feel {adjectives: professional, memorable, simple}. Give me 10 options, ranked from your favorite to least favorite.

The move: gives Claude explicit permission to disagree, and asks for strength rank so you see the best counter first.

I'm considering {idea or plan}. Play devil's advocate. Give me the 5 strongest arguments against doing this. Be honest, not polite.

The move: primes your attention before reading — you notice more of what matters.

I'm about to read {document type or topic}. Before I do, what 5 questions should I be trying to answer as I read it?

The move: gives Claude a specific audience and explicit license to cut — removes the reason it tends to hedge.

Rewrite the following so it is concise, direct, and appropriate for a senior executive audience. Cut anything that doesn't need to be there. Keep the core message intact.

{PASTE TEXT HERE}

The move: a hard numerical constraint forces prioritization — no more "I shortened it a bit."

Condense the following to 100 words or fewer. Keep the most important information. Do not add anything new.

{PASTE TEXT HERE}

The move: time estimates per section turn a topic list into an actual runnable meeting.

I have a {length} meeting with {attendees or roles} about {meeting purpose}. Topics: {list}. Draft a structured agenda with time estimates for each section.

The move: a count forces signal density — "summarize this" leaves Claude room to ramble.

Summarize the following in exactly 3 bullet points. Each bullet should capture one key point. Use plain language.

{PASTE TEXT HERE}

The move: "what is being asked of me" cuts through the performance and finds the actual request.

I've been added to an email thread. Summarize what has happened so far and what (if anything) is being asked of me.

{PASTE THE FULL EMAIL THREAD HERE}

The move: explicitly invites disagreement — counters Claude's default of supporting whatever plan you present.

I'm planning to {describe your plan or decision}. What risks, blind spots, or considerations am I likely missing? Be direct and specific.

The move: surfaces blind spots before they become problems — preparation, not recall.

I'm about to {action: negotiate a contract, hire for a new role, pitch to an investor}. What are the 5–7 most important things I should know or understand beforehand? Be specific.

The move: pre-loads the four things every follow-up needs (who/what/next/length), so the output is ready to send.

Write a brief, professional follow-up email after a meeting with {person's name and company}. We discussed {main topics covered}. The next step is {who does what by when}. Keep it to 3–4 sentences.