The AI prompt pack

Here is an unstructured brain-dump of what I need to get done. Group the items into themes, order them by impact and urgency, flag anything that is blocking something else, and give me a realistic plan for today and this week. Ask me for anything that is unclear before you start. [paste your notes]

Read the conversation below and extract only what matters: the decisions made, the open questions, and who owns each next step with a due date if one is mentioned. Keep it under 200 words and use bullet points. [paste the thread]

Write a short status update for my team based on these notes. Structure it as: what shipped, what is in progress, what is blocked, and what I need from others. Keep the tone plain and confident, no filler. [paste notes]

I need to have a difficult conversation about the situation below. Help me prepare: what is the core message, what outcome do I want, what are the likely objections, and how do I stay calm and specific. Give me two or three opening lines I could actually say. [describe the situation]

I am deciding between these options. Build a simple weighted scorecard: propose 4 to 6 criteria that matter for this decision, weight them, score each option, and show the totals. Then tell me where the result is close enough that my own judgment should break the tie. [list the options]

Act as my weekly review coach. Ask me one question at a time about what went well, what slipped, and what I am carrying into next week. After my answers, summarize three lessons and one focus for the coming week.

Edit the text below for clarity and concision without changing my meaning or voice. Cut redundancy, replace vague words with specific ones, and fix any awkward phrasing. Show the edited version first, then a short list of the biggest changes and why. [paste your draft]

Rewrite this message for the following reader so it lands well with them: [describe the reader, their priorities, and how much detail they want]. Keep it honest and specific, and match their level of formality. [paste the message]

Write three subject-line options for the email below, each with a different angle (clarity, curiosity, urgency). For each, add one line explaining who it works best for. Then recommend one. [paste the email]

Explain the concept below to a smart person who is new to the topic. Use a concrete analogy, avoid jargon, and end with the one thing they should remember. Keep it under 150 words. [concept]

Turn these rough notes into a clear outline for a [article, talk, doc]. Propose a logical structure with a strong opening, three to five main sections, and a closing takeaway. Mark anywhere the argument is thin so I can fill it in. [paste notes]

Help me sharpen the positioning for the product below. Give me: the one-sentence value proposition, the specific audience it is for, the top three benefits framed as outcomes, and the single reason to choose it over the obvious alternative. Be concrete, no buzzwords. [describe the product]

Critique the landing-page copy below like a skeptical first-time visitor. Where would I get confused, where do I not believe the claim, and where is the call to action unclear. Then rewrite the weakest section. [paste the copy]

Here is one insight my audience cares about. Generate 10 content angles from it (posts, threads, short videos), each with a specific hook. Rank them by how likely they are to resonate and say why. [the insight]

Below are raw customer quotes or reviews. Cluster them into the recurring themes, quote the most vivid line for each theme, and tell me which theme I should lead with in my messaging and why. [paste quotes]

Write a short, specific outreach message to the person below. Reference something real about them, make one clear ask, and keep it under 90 words. No flattery, no fake urgency. [describe the recipient and the ask]

Explain what the code below does, step by step, in plain language. Call out anything surprising, any edge cases it does not handle, and one thing you would improve. Do not rewrite it yet. [paste code]

Here is the code, the expected behavior, and the actual behavior. Give me your top three hypotheses for the bug, ordered by likelihood, and the fastest way to test each one. Only then propose a fix. [paste code, expected, actual]

Review the change below the way a thoughtful senior engineer would. Focus on correctness, edge cases, and readability, not style nitpicks. For each issue, give a concrete failure scenario and a suggested fix. [paste the diff or code]

Write a focused set of tests for the function below. Cover the happy path, the boundary cases, and the failure modes. List the cases first as a short table, then the test code. [paste function]

I need to implement the feature below. Before any code, give me a short implementation plan: the files likely involved, the approach, the trickiest part, and how I would verify it works. Ask me anything you need first. [describe the feature]

I want to learn the topic below to a working level. Give me a roadmap: the core concepts in the order I should learn them, one concrete exercise per concept, and a way to test that I actually understand each one. Assume I have limited time. [topic]

Give me the strongest honest case for and against the claim below. For each side, state the best evidence and the weakest point. End by telling me what a careful person would still be uncertain about. [the claim]

Quiz me on the topic below to find the gaps in my understanding. Ask one question at a time, adapt the difficulty to my answers, and after five questions tell me exactly what to review. [topic]

Compare the options below on the dimensions that actually matter for someone in my situation: [describe your situation]. Use a table, be specific about tradeoffs, and note where the honest answer is that it depends. [list options]

Read the material below and pull out only what is useful to me: the key claims, the numbers worth remembering, and anything I could act on. Skip the background I likely already know. [paste material]