Free AI prompt generator

PROMPT Turn my raw meeting notes into a status update email for my VP, [VP NAME]. She reads on her phone between meetings, so the email must be scannable in under a minute and lead with anything she needs to decide. Project and meeting: [PROJECT NAME AND MEETING DATE] My notes are below. Treat them as the only source of truth. [PASTE MEETING NOTES] Work through the notes in this order: 1. Pull out every decision, date or deadline, risk or blocker, and open question, with the owner when the notes name one. 2. Decide the overall status: On track, At risk, or Off track. Base it on the dates and blockers, not on how upbeat the discussion sounded. 3. Separate what needs her decision or help from what is information only. Write the email in this format: - Subject line: the project name, the status, and the single biggest change, under 12 words. - First line: the status and the one thing she needs to know or decide. - "Needs your input": only if something requires her decision, each item with the options and a deadline. - "Progress": 3 to 5 bullets, each under 20 words, with dates. - "Risks": each with its likely impact and who owns the fix. - "Next steps": owner and date for each. Keep the whole email under 200 words, in plain, direct language with no warm-up. Use only what is in the notes. Do not invent dates, owners, numbers or reasons. Where an important owner or date is missing, write [OWNER?] or [DATE?]. If the notes contradict each other, add a final line starting "Check:". Before answering, check that every date and name in the email appears in my notes, and that the first line still makes sense if she reads nothing else. FILL IN [VP NAME] — Her first name, for the greeting. [PROJECT NAME AND MEETING DATE] — So the subject line and dates are right. [PASTE MEETING NOTES] — Your raw notes or transcript. Messy is fine. WHY IT WORKS - It tells the AI what your VP cares about (decisions, dates, risks), so it knows what to keep and what to cut. - Status is judged from dates and blockers, not from the mood of the meeting. - [OWNER?] and [DATE?] markers replace guesses, so nothing made up reaches your VP.

PROMPT Review the freelance contract below before I sign it. I'm a freelance designer in [YOUR STATE], US, and the client is a mid-size agency. My priorities are getting paid on time and keeping clear rights to my work. I'm not asking for legal advice; I want a clear business read so I know what to push back on and when a lawyer is worth paying for. <contract> [PASTE THE FULL CONTRACT] </contract> <my_deal> Scope, fee and timeline as agreed: [SCOPE, FEE, DEADLINE] Terms I won't accept: [DEAL-BREAKERS] </my_deal> Work through it in this order: 1. Read the whole contract first, then list any clause that contradicts <my_deal>. 2. Review these areas clause by clause, quoting the exact wording: payment (schedule, invoice terms, late fees, kill fee), scope and revisions, intellectual property and portfolio rights, termination, liability and indemnification, non-compete or non-solicitation, confidentiality, and dispute resolution. 3. Rate each issue High, Medium or Low for a freelancer in my position, with one sentence on why. 4. For every High and Medium issue, write replacement language I could propose, in plain contract English. Output: - Summary: three sentences on overall risk and the top issue. - A table with columns Clause (quoted) | What it means in practice | Risk | Suggested change. - Missing protections: terms freelancers usually want that this contract lacks, such as a deposit, a kill fee or a revision cap. Only list what is absent. - An email to the client, under 150 words, proposing the top three changes politely. - Questions for a lawyer: up to three, only where the answer depends on local law. Rules: quote the contract exactly and never present a paraphrase as a quote. If a clause is ambiguous, give both readings instead of picking one. Don't state what the law in my state requires without flagging it as something to confirm. If part of the contract seems to be missing from what I pasted, say so. Before answering, check that every quoted clause appears word for word in <contract>, and that every suggested change fixes the risk you named. FILL IN [YOUR STATE] — Where you work; some contract terms depend on state law. [PASTE THE FULL CONTRACT] — The whole text, not just the parts that worry you. [SCOPE, FEE, DEADLINE] — What you agreed in emails or calls. [DEAL-BREAKERS] — Anything you won't sign, such as unlimited revisions. Write "none yet" if unsure. WHY IT WORKS - The XML tags keep the contract apart from your instructions, a structure Anthropic recommends for long documents in Claude. - Exact quotes plus a word-for-word check stop the AI from reviewing a clause that isn't there. - You get proposed wording and a ready-to-send email, not just a list of worries. - It marks where local law matters, so you know when an hour with a lawyer is worth it.

PROMPT Below are answers to the survey question "What almost stopped you from buying?" from customers of [PRODUCT NAME], a software subscription. Group them into 5 to 8 themes. For each theme, give a short name, the number of answers in it, and two verbatim quotes. Sort themes by count, count each answer once under its main theme, and put answers that fit no theme under "Other" instead of stretching a theme to fit them. End with the three themes most worth fixing first, with one sentence each on why. Use only the answers I pasted, and don't guess at reasons customers didn't give. Before answering, check that the theme counts add up to the total number of answers. [PASTE SURVEY ANSWERS, ONE PER LINE] FILL IN [PRODUCT NAME] — So the themes are read in the right context. [PASTE SURVEY ANSWERS, ONE PER LINE] — All the answers. For 300, upload a CSV so ChatGPT can count with code. WHY IT WORKS - Counts plus real quotes let you check each theme against what customers actually said. - The "Other" bucket stops the AI from forcing answers into a tidy list. - The sum check catches skipped or double-counted answers, the most common failure with long lists.