AI agent prompts for makers

Make me a launch week plan for [product name], launching on [launch site] in the week of [date]. The launch week runs Monday to Sunday. About me: [solo maker or team size], [hours per day I can spend], [audience I already have: email list size, followers, communities I'm active in] The goal for the week: [signups, feedback or first paying users] Give me: 1. A checklist for the week before: assets to prepare (screenshots, a short demo video, the listing copy, one launch post per channel) and people to tell in advance. 2. A day-by-day plan from Monday to Sunday: where to post each day, who to message and when to reply to comments. Spread the effort across the week instead of spending it all on Monday. 3. What to measure each day, and what to change if a channel isn't working. 4. A short follow-up plan for the week after. Keep it realistic for the hours I gave. Never suggest buying votes, vote swaps or fake accounts: they get launches removed.

Help me write a launch thread for X. Product: [product name] What it does, in one sentence: [one-sentence description] Who it's for: [target user] The problem it solves, in their words: [problem] How it differs from [main alternative]: [difference] Launch link: [link] Something real I can show: [demo GIF, screenshot or a result a user got] Write a thread of 5 to 7 posts: 1. A first post under 240 characters that names the problem and the product in plain words. No "excited to announce", no wall of emoji. 2. Two or three posts that each show one concrete thing the product does. Mark the image I should attach as [image: ...]. 3. One post on why I built it, in first person, with one specific detail from my own experience. 4. A last post with the link and one clear ask (try it, give feedback or upvote), not all three. Short sentences, at most one hashtag, no "1/7" numbering. Then give me 3 alternative first posts with different angles (the problem, the result, the story) so I can pick one.

Write a LinkedIn post announcing that I launched [product name]. Context: - What it does: [one-sentence description] - Who it's for: [target user and their role] - Why I built it: [the moment or frustration that started it] - One result I can honestly share: [early result, or "none yet"] - Link: [link] Structure: - A first line under 150 characters that makes [target user] stop scrolling. It names their problem, not my product. - 3 to 5 short paragraphs of one or two sentences: the problem, what I built, how it works in practice, what I learned building it. - One closing question that invites [target user] to share their own experience in the comments. - The link on the last line, not the first. Plain and specific, first person, no buzzwords (leverage, synergy, revolutionize, game-changer), no emoji bullets, at most 3 hashtags at the end, under 1,300 characters. Give me two versions: one that opens with the story and one that opens with the problem.

I want to share [product name] in r/[subreddit]. Reddit punishes self-promotion, so help me write a post that gives value first. About the product: [one-sentence description] Who it's for: [target user] What I learned building it that this subreddit would find useful: [lesson, data or story] The subreddit's rules on self-promotion, pasted: [rules] Do this: 1. Check my plan against the rules I pasted and tell me plainly if this post would break them, and what to change. 2. Suggest 3 titles that describe the lesson or question, not the product. No clickbait, no capitals for emphasis. 3. Write the post: lead with the lesson or story in 150 to 250 words, mention the product once near the end in one sentence with the link, and end with a genuine question for the community. 4. Write short replies for 3 likely comments: "Is this an ad?", "How is this different from [alternative]?" and "What does it cost?". Honest and friendly, no marketing voice.

Help me post [product name] to Show HN. What it is: [one-sentence description] How it works under the hood: [stack, approach, anything technically interesting] Why I made it: [motivation] What's free and what's paid: [pricing] Link (ideally usable without signing up): [link] Give me: 1. Five title options in the format "Show HN: [product name] - [what it does]". Literal, under 80 characters, no adjectives like fast, simple or powerful unless they're the point. 2. The first comment I post myself, 150 to 300 words: who I am in one line, the problem, how it works technically, what is rough or missing, and the feedback I'm looking for. Hacker News readers respect honesty about limits, so include them. 3. 5 hard questions commenters are likely to ask about [product name], with a short, direct answer to each. Flag anything in my description that would read as marketing to this audience.

Act as a first-time visitor who has never heard of [product name]. You arrived on the homepage from [traffic source, e.g. a search for "keyword"]. Here is the text of the first screen, everything visible without scrolling (headline, subheadline, buttons, labels): [paste first-screen text] 1. In one sentence, say what you think the product does and who it's for, based only on this text. Don't guess generously. 2. List every word or phrase a newcomer might not understand. 3. Say what you would click, and what you'd expect to happen next. 4. Compare your understanding with what the product actually does: [one-sentence description]. Where is the gap? 5. Rewrite the headline and subheadline 3 ways: one that leads with the outcome, one with the audience, one with how it works. Headline under 10 words, subheadline under 25. Plain words, no "all-in-one" or "next-generation".

You are a conversion copywriter reviewing the landing page for [product name], a [one-sentence description] for [target user]. The action I want visitors to take is [primary action, e.g. start a free trial]. Here is the full page text, top to bottom, with section breaks marked: [paste page text] Review it section by section. For each section give: - What it's trying to do. - What a skeptical [target user] would think reading it. - The biggest problem, quoting the exact words. - A rewritten version. Then list the 5 changes most likely to increase [primary action], ranked by expected impact, with one sentence on why for each. Look for claims without proof, features without outcomes, unanswered objections (price, switching cost, trust, data security), a call to action that comes too late or says too little, and jargon. Don't suggest fake testimonials, invented numbers or false urgency.

I sell [product name] to [target user]. It costs [price] and replaces [current solution or habit]. Here is my landing page text: [paste page text] 1. List the 10 most likely reasons a qualified visitor leaves without [primary action]. Consider money, setup time, switching from [current solution], trust in a new company, data and privacy, and whether it works for their specific case. 2. For each reason, say whether the page answers it now (quote where), answers it weakly or doesn't answer it. 3. For the weak and missing ones, write the answer as it should appear on the page: a short FAQ entry, a line near the button or a small section. Keep each under 50 words and only use these facts: [facts you can stand behind, e.g. data export, refund policy, integrations].

Write tagline options for [product name]. What it does: [one-sentence description] Who it's for: [target user] The main outcome they get: [outcome] What it replaces: [current tool or habit] Words to avoid: [words] Write 20 taglines, 4 in each style: 1. Outcome: what the user gets. 2. Audience: who it's for and what it does for them. 3. Contrast: what it replaces or does differently. 4. Literal: exactly what it is, for search and directories. 5. Voice: a little personality, still clear to a newcomer. Under 60 characters, sentence case, no trailing period, no puns that hide the meaning, no "AI-powered" unless buyers care, no superlatives. Then pick the 3 strongest for a launch directory listing and say why in one line each.

Write a product description for [product name] that I'll reuse on launch sites, directories and app store listings. Facts (use only these; don't invent features, numbers or customers): - What it does: [description] - Main features: [feature 1], [feature 2], [feature 3] - Who it's for: [target user] - Pricing: [pricing] - Platforms: [web, iOS, Chrome extension, ...] - How it differs from [alternative]: [difference] Write three versions: 1. Short: one sentence under 160 characters, for meta descriptions and directory summaries. 2. Medium: one paragraph of 50 to 70 words. 3. Long: three short paragraphs, 150 to 220 words in total. First what it is and who it's for, then what you can do with it, then how it's different and what it costs. Third person, present tense, plain words, no superlatives, no calls to action, no emoji. Use [primary keyword] naturally once in each version.

Here are the features of [product name], a tool for [target user]: [paste feature list] For each feature, write: - Benefit: what the user can now do or stop doing, under 12 words, starting with a verb. - Proof: what a screenshot, number or example should show to make the benefit believable. - Who cares most: which kind of [target user] this matters to. Then order the features from most to least important for a first-time visitor, and say which 3 belong on the homepage and which belong on a features page. Keep to the real capabilities I listed; don't add features.

Create an SEO content brief for an article targeting the search "[target keyword]". My site: [site URL], which sells [product name], a [one-sentence description] for [target user]. Reader: someone searching "[target keyword]" who is [their situation]. Include: 1. Search intent: what the searcher wants to walk away with, in one sentence, and the format that fits (guide, list, comparison, template or tool page). 2. A working title under 60 characters and a meta description under 155 characters. 3. An outline with H2s and H3s. Under each heading, 1 to 3 bullet points on what to cover, including the examples, steps or data the section needs. 4. Questions the article must answer, phrased the way people ask them. 5. Related terms and entities a thorough article would naturally mention. 6. Where [product name] fits naturally, at most twice, without turning the article into an ad. 7. Internal links to add from these pages of mine: [list of your relevant pages]. 8. What would make this article better than a typical one on the topic: original examples, a screenshot walkthrough, a template or first-hand data. Don't guess search volumes or difficulty. If you're unsure about the intent, give two options and say how I can check.

Plan a topic cluster for [site URL], which sells [product name] to [target user]. Core topic: [topic] Pages I already have: [list of URLs and titles] Give me: 1. One pillar page: title, the search it targets and an outline of 6 to 10 headings. 2. 10 to 15 supporting articles. For each: working title, the search it targets, the intent (informational, commercial or transactional) and the one question it answers. 3. How the pages link to each other: which supporting pages link to the pillar, which link to the product, and with what anchor text. 4. An order to publish them in, starting with the pages closest to a buying decision. 5. Which of my existing pages overlap with the plan and should be merged, updated or linked instead of duplicated. No search volume numbers. Mark any idea you're unsure people search for, so I can check it in a keyword tool first.

This article on my site used to get search traffic and is slipping: URL: [URL] Target search: [target keyword] Published: [date] Text: [paste article] Review it against what someone searching "[target keyword]" needs today: 1. Sections that are out of date, thin or no longer accurate (quote them). 2. Questions it doesn't answer and should. 3. A better title and meta description, under 60 and 155 characters. 4. A revised outline that keeps the useful parts, with each section marked KEEP, UPDATE, ADD or CUT. 5. Two or three original things I could add that other articles on this topic can't copy: my own data, screenshots, examples from [product name] users or a template. Keep the URL the same. Don't pad the article: cut anything that doesn't help the reader.

Write an llms.txt file for my site in the llmstxt.org format: an H1 with the site name, a one-paragraph summary in a blockquote, a few plain sentences of context, then H2 sections of markdown links in the form "- [Page title](URL): one-line description". Site: [site URL] Product: [product name], [one-sentence description] Who it's for: [target user] Facts an assistant must get right: [pricing, platforms, company location, founding year, integrations] Important pages, with what each covers: [list of pages] Rules: - Facts only, written for a machine that may quote you: no slogans, no superlatives. - Most important pages first: product overview, pricing, docs, comparisons. - An "Optional" section at the end for pages an assistant can skip when short on context. - Descriptions under 20 words. After the file, list facts I should also add to the pages themselves, since assistants trust a page more than an llms.txt.

AI assistants cite pages that state facts clearly, answer questions directly and are easy to quote. Review this page from [site URL] with that in mind: [paste page text] The questions I want assistants to answer with this page: [questions, e.g. "what is a good tool for X" or "how much does it cost"] 1. For each question, say whether the page answers it in one or two quotable sentences, and quote them if so. 2. Write or rewrite those answer sentences: self-contained, specific, with the product name in them and no pronouns that depend on earlier text. 3. Draft a short FAQ section of 4 to 6 entries using the exact questions. 4. List missing or vague facts (pricing, who it's for, limits, integrations, dates) and where on the page they belong. 5. Suggest the schema.org types this page should declare in JSON-LD (for example SoftwareApplication, FAQPage, Organization) and which fields to fill. Don't make claims I haven't given you. Mark anything you need me to confirm.

Step 1. Ask this in ChatGPT, Claude, Perplexity and Gemini, each in a new chat: "I'm a [target user] looking for a tool to [job to be done]. What are the best options, and what are the pros and cons of each? Is [product name] ([site URL]) a good choice?" Step 2. In a new chat, paste all the answers and send this: Here are answers from several AI assistants: [paste answers] About [product name]: 1. Did each assistant mention it unprompted, only when asked, or not at all? 2. What did each say it does, who it's for and what it costs? Mark anything wrong or out of date. 3. Which competitors came up most, and why were they recommended? 4. Which sources or pages did the assistants seem to rely on, where visible? 5. List the pages, facts and third-party mentions I should create or fix so future answers are accurate and include [product name], ordered by effort and likely effect.

Here is the homepage text of [competitor name], a competitor of my product [product name]: [paste competitor homepage text] Analyze it: 1. Positioning: who they say it's for, the main promise and the category they place themselves in. 2. The 3 claims they lead with, and the proof they show for each. 3. Objections they handle, and how. 4. Who this page doesn't speak to, or speaks to badly. 5. Words and phrases their buyers would recognize, so I learn the language of this market. Then compare with my product: [one-sentence description, who it's for, price]. Suggest 3 positioning angles where I can be clearly different rather than a cheaper copy, with a one-line headline for each. Stick to what's on the page and mark any inference as a guess.

Below are reviews of [competitor name] from [G2, Capterra, the App Store, Reddit or elsewhere]: [paste reviews] 1. Group the complaints into themes. For each: how often it appears, a typical quote and the need underneath it. 2. Do the same for praise: what users love and wouldn't give up if they switched. 3. List the switching triggers: the moments that made someone look for an alternative. 4. From this, write 3 features or fixes [product name] should prioritize, 3 lines for a "[competitor name] alternative" page and 3 questions to ask in user interviews to test these findings. Quote reviewers exactly. Don't invent quotes or counts; if a theme appears once, say so.

Write a comparison page for people searching "[competitor name] alternative". My product: [product name], [one-sentence description], [price] Competitor: [competitor name], [what it does], [price] Where we're better, with facts: [differences] Where they're better, honestly: [their strengths] Who should pick which: [your view] Structure: 1. A title under 60 characters and a meta description under 155. 2. A short intro: who the page is for and a one-paragraph summary of the difference. 3. A comparison table of 8 to 12 rows: feature, [product name], [competitor name]. Use "Yes", "No" or a short fact, never vague ratings. 4. A section on each of the 3 biggest differences, with an example. 5. "When [competitor name] is the better choice", honest and specific. 6. How to switch, step by step, including what can be imported. 7. An FAQ with 4 questions. Stay factual and fair. Readers can check, and a balanced page earns more trust and links than an attack.

Write a cold email sequence to a [prospect role] at a [company type]. My product: [product name], [one-sentence description] The problem I think they have: [problem] Why I think so: [signal, e.g. a job post, a public complaint, their tech stack] Proof I can share: [customer result, demo link, or "early, no results yet"] What I want: [a 15-minute call, a reply or a trial] Write: 1. A first email under 90 words. Subject line in lowercase, under 6 words, no clickbait. Open with the signal, not with me. One sentence on what the product does for someone like them. One small ask. 2. Follow-up 1, three days later, under 50 words, adding one new piece of value (a tip, a short example) instead of "just bumping this". 3. Follow-up 2, a week later, under 40 words, making it easy to say no. Also give me 5 variations of the first line, each built on a different kind of signal. No flattery, no fake familiarity, no "I hope this finds you well".

I want [product name] added to this article: [article URL and title], written by [author name]. About the article: it lists [what it lists], including [examples]. About my product: [one-sentence description], [price], for [target user]. Why it fits the article's readers: [reason] Something useful I can offer: [an updated screenshot, a quote, a reader discount, or a broken link I found in the article] Write a short email to [author name]: - Under 120 words. - Show I read the article by mentioning one specific thing in it. - One sentence on why their readers would care, not why I want the link. - Offer something that saves them time, such as a ready-to-paste entry of 40 to 60 words in the article's existing format. Write that entry too. - A subject line under 8 words. Then write one polite follow-up for a week later, under 50 words.

Help me pitch a partnership to [partner company], which makes [partner product]. Why our users overlap: [overlap] The integration or joint promotion idea: [idea] What's in it for them, concretely: [benefit to them] What I'll do on my side: [build the integration, write the guide, share it with my N users] Who I'm writing to: [name and role, if known] Write: 1. A cold email under 130 words with a clear, specific proposal and the smallest possible first step. 2. A one-paragraph description of the idea that they can forward internally. 3. Three objections they'll likely raise (priority, support load, brand risk) and a one-sentence answer to each.

Write a 30-minute interview script for talking to [type of user] about [problem area]. I make [product name], but the goal is to learn, not to sell. What I want to learn: [learning goals, e.g. how they handle the problem today, what they've tried, what it costs them] Follow these rules, from "The Mom Test": - Ask about specific past events, not opinions about the future ("Tell me about the last time..." rather than "Would you use...?"). - Don't mention my product or its features until the last 5 minutes. - No leading questions and no yes-or-no questions. Structure: 1. Warm-up (3 minutes): 2 questions about their role and day. 2. The problem (15 minutes): 6 to 8 questions, each with follow-up probes. 3. Current solutions (7 minutes): what they use, what they pay and what they dislike about it. 4. Wrap-up (5 minutes): what I should have asked, and who else I should talk to. After the script, list 5 signals that the problem is real and painful, and 5 that suggest it isn't.

Here are my notes from [number] customer interviews about [problem area]. Interviews are separated by ---. [paste notes] Synthesize them: 1. The 5 most common problems, each with how many interviews mentioned it and 2 exact quotes. 2. Current solutions people use and what they spend on them, in money or time. 3. Differences between segments, such as company size or role, if the notes show any. 4. Surprises: anything that contradicts what I believed, which was: [your assumptions]. 5. The 3 decisions these interviews support for [product name], and what I still don't know. Only use what's in the notes. When something comes from one interview, say so, and don't count one strong opinion as a pattern.

I need to recruit [number] [type of user] for 20-minute calls about [problem area]. Where I'll find them: [communities, LinkedIn, my user list, Reddit] What I can offer: [gift card amount, early access, a summary of the findings, or nothing] Write: 1. A short post for [community] asking for people to talk to, under 100 words, that makes clear I'm not selling anything. 2. A direct message to someone who posted about this problem, under 60 words, referring to what they posted. 3. An email to my existing users, under 120 words, with a [booking link]. 4. 3 screening questions to check that a volunteer really has the problem, with the answers that qualify them.

Turn these changes into a changelog entry for [product name]. My users are [target user], and most aren't developers. Changes (commits, pull request titles or tickets): [paste changes] Write: 1. A title for the release that names the most useful change, not just a version number. 2. A one-paragraph summary of what's new for users. 3. Sections for New, Improved and Fixed. One line per item, starting with what the user can now do, in plain words. Skip internal work (refactors, dependency updates, CI) unless users notice a difference, such as speed. 4. For the biggest change, 2 or 3 sentences on how to use it, and where a screenshot should go, marked [screenshot: ...]. Don't overstate: say "faster" only if I said it's faster. Ask me about anything ambiguous instead of guessing.

Write an email to [product name] users announcing [feature or update]. What changed: [description] Who benefits most: [segment] How to try it: [steps or link] What it replaces or fixes: [previous behavior or common complaint] Anything users must do: [action required, or "nothing"] Rules: - A subject line under 50 characters that names the benefit, plus 2 alternatives. - Preview text under 90 characters. - A body under 180 words: the benefit in the first sentence, how it works in 2 or 3 short sentences, one button with a clear label, and a line saying where to send feedback. - Plain style: no "we're thrilled", no strings of exclamation marks. Also write a 2-sentence version for an in-app banner and a post for X under 260 characters.

I'm relaunching [product name] on [launch site] and need a short "What's new" note. Since the last launch on [date], we changed: [list of changes] Results since then, if any: [users, revenue, reviews, or "none to share"] Write: 1. A "What's new" note under 280 characters that leads with the change that matters most to someone who saw the first launch. 2. A longer version of 3 to 5 bullet points, each starting with a verb. 3. A first comment for the launch page, under 150 words, thanking early users for specific feedback and saying what it led to. Be specific: "Rebuilt the editor so documents open in under a second" beats "Lots of improvements".

Review the pricing page for [product name], a [one-sentence description] for [target user]. Pricing page text: [paste pricing page text] What I know about customers: [who buys, which plan is most popular, common questions before buying] Check: 1. Can a visitor tell which plan is for them within 10 seconds? Which plan names, limits or units are unclear? 2. Is the value metric (per seat, per project, per use) one the buyer understands and sees as fair? 3. Which questions about billing, limits, overages, trials, cancellation and refunds go unanswered? 4. Does the page help buyers compare against doing nothing or using [alternative]? 5. Suggest better plan names and a one-line description for each plan that says who it's for. 6. Draft an FAQ with the 6 questions buyers most need answered, using only facts I gave you. Mark missing facts as [need to confirm]. Don't suggest dark patterns: no fake discounts, countdown timers or hidden fees.

I want to set or change the price of [product name]. It costs [current price] now, and similar tools charge [competitor prices]. Help me decide with evidence: 1. Write 8 interview questions for current customers about the value they get, what they'd use instead and how they decide on spending. No direct "how much would you pay?" questions. 2. Write a short survey using the Van Westendorp questions (too cheap, a bargain, getting expensive, too expensive), adapted to my product, plus 2 questions to segment answers by [customer segment]. 3. Explain how to read the results, and how many responses I need before trusting them. 4. Suggest 3 pricing experiments I could run safely with new visitors, and the result that would make me keep each one.

Help me structure the plans for [product name]. Customer types and how each uses the product: [segment 1: usage], [segment 2: usage], [segment 3: usage] Features and what they cost me to run: [feature list, noting anything expensive such as AI calls or storage] Current plans, if any: [plans and prices] What I want pricing to do: [e.g. let small teams start free, make larger teams pay for collaboration] Give me: 1. Two or three plan structures, each with plan names, who each plan is for, the value metric and which features sit in which plan. 2. For each structure, the upgrade moment: the specific point at which a customer outgrows their plan. 3. Risks of each, such as a free plan that's too generous or a limit that annoys good customers. 4. Your recommendation, and what to measure in the first 60 days to know whether it works. Don't pick prices for me without saying what the guess is based on.

Write support reply templates (macros) for [product name]. Our voice: [e.g. friendly and direct, first names, no corporate phrases] The most common tickets: [list, e.g. can't log in, refund request, how to export, bug report, feature request] Policies to follow: [refund policy, response times, things we can't do] For each ticket type, write a reply under 120 words that: - Opens by restating the person's problem in one line, so they know we read it. - Gives the answer or next step, numbered if there are several. - Uses variables like {first_name} and {link} where details change. - Ends with one clear next step, not "let us know if you have any other questions". Give each macro a short internal name and a note on when not to use it.

Help me reply to this message from an upset customer: [paste message] Context: [what actually happened, what we can offer, any policy that applies] Write a reply that: 1. Acknowledges the specific problem in their words, without "we apologize for any inconvenience". 2. Says plainly what went wrong, if we know, and takes responsibility where it's ours. 3. Says exactly what we'll do and by when. 4. Offers [remedy] if it fits. 5. Stays under 150 words, with no defensive explanations. Then tell me if anything in their message points to a bigger problem, such as a bug affecting others or a gap in our docs.

Turn this support conversation into a help center article for [product name]: [paste conversation] Write: 1. A title phrased the way users search, such as "How to [task]" or "Why [problem] happens". 2. A one-sentence answer at the top for people who read nothing else. 3. Numbered steps, one action each, with [screenshot: ...] markers where an image helps. 4. A "Still not working?" section with the 2 or 3 most likely causes and fixes. 5. Titles of related articles I should link to. Remove names and personal details from the conversation. Keep it under 400 words.