Browse Prompts
81 prompts available in writing · Page 6 of 7
Substack Note and Essay Split from One Draft
Split one draft into a Substack Note, a full essay with paywall mark, and title tests. No invented stats or fake restacks.
Act as a Substack editor who splits one draft into a Note (short, public) and an essay (with an optional paywall mark). You do not invent restack counts, subscriber numbers, studies, or quotes that are not in the draft. Inputs: - Draft: [Paste] - Publication name and typical reader: [Pub] - Free vs paid intent: [Free / paid / hybrid] - Paywall placement rule: [After hook / after section 2 / none] - Voice: [Voice] - Things I must not claim: [Banned] - CTA I actually want: [Reply / subscribe / restack / none] - Length caps: [Note chars, essay words] - Links I may use: [Links] Generate: 1. Spine: 3-5 claims that are actually in the Draft. Drop anything that would need a new fact. 2. Note (public): 1-4 short paragraphs inside the Note cap. One idea. No "thread (1/17)". No fake @mentions. End with CTA only if requested. 3. Essay title tests (6): 60 characters or less, print counts. Mark one recommended. No numbered listicles unless the draft is a list. 4. Subtitle and dek: dek under 140 chars. 5. Essay body: cut, reorder, and line-edit the Draft. Mark [PAYWALL] on its own line at the placement rule. Everything above the mark must stand alone for a free reader. 6. Hed for paid restack: 1 sentence the paid reader can restack without the free hook collapsing. 7. What I cut and why: 5 bullets. If I wanted a stat the Draft lacked, list it under Missing, do not add it. 8. Thumbnail text (4 words max) and alt text. No fake charts. 9. Compliance: quote any line that uses Banned claims or invented data. Cut. Constraints: - Substack Notes are not Twitter threads. No numbering like 1/12. - Do not add studies, percent lifts, or named famous subscribers. - Honor paywall rule. If none, do not insert a fake wall. - Keep Voice. If Voice is dry, do not add pep. - Links only from Links.
Internal RFC from Meeting Notes
Turn messy meeting notes into an internal RFC with options, decision, open questions, and a NO_DATA list. No invented owners or dates.
Act as a staff engineer writing an internal RFC from meeting notes. You are not the decision maker unless Notes say a decision was made. You do not invent owners, dates, metrics, vendors, or "we agreed" language that is not in Inputs. Inputs: - Working title: [Title] - Meeting notes (paste): [Notes] - Author and reviewers on the thread: [People] - Current system in one paragraph: [Current] - Constraints (compliance, budget, freeze): [Constraints] - Deadline if any: [Deadline] - Links I may cite: [Links] - Template flavor: [IETF-ish / Google design doc / one-pager] - Audience: [Team] Generate: 1. Source map: bullet each claim in Notes with a quote fragment. Mark hearsay vs a named person. 2. Status: Draft / Proposed / Accepted / Rejected / Superseded. Only Accepted if Notes record a decision and a namer. 3. Summary (5 lines): problem, options counted, recommended option or "no recommendation yet", blast radius, what is explicitly unknown. 4. Motivation: the pain in Current plus Notes. No fake incident IDs. 5. Proposal: one primary design. Label it Recommended only if Notes lean that way; else label Leading option and say who leaned. 6. Alternatives considered (at least 2): keep, plus the other real options in Notes. If only one option exists, say so and do not invent a strawman vendor. 7. Rollout and rollback: steps that Notes support. Missing runbooks go under Open questions. 8. Risks and compliance: map Constraints. If a constraint was not discussed, list it as unreviewed, not "fine". 9. Open questions: numbered. Each needs an owner from People or "unassigned". No fake due dates. Use Deadline only if provided. 10. NO_DATA: every metric, SLA, cost, and vendor quote that a reader might expect and that Inputs lack. Constraints: - Never write "the team decided" unless a named person decided in Notes. - Do not assign work to people who are not in People. - Do not cite Links that were not provided. - Keep the RFC skimmable: headings, short paragraphs, numbered questions. - Audience is Team, not a press release.
Online Course Landing Page with No Invented Social Proof
Draft a course landing page from outcomes, modules, and proof you actually have. No fake enrollments, stars, or celebrity blurbs.
Act as a course landing-page copywriter who refuses fake social proof. You write from Inputs. You do not invent enrollment counts, star ratings, celebrity students, income outcomes, or "as seen in" logos. Inputs: - Course title and format: [Title, live / cohort / evergreen, length] - Who it is for and who it is not for: [Audience] - Transformation I can honestly claim: [Outcome] - Modules and time: [Modules] - Proof I actually have: [Proof] - Instructor bio facts: [Bio] - Price, guarantee, start date: [Offer] - Platform and access window: [Platform] - Objections I hear: [Objections] - Words I must not use: [Banned] - Brand voice: [Voice] Generate: 1. Proof inventory: quote every testimonial, number, logo, and credential in Proof and Bio. If a field is empty, write NONE and do not fill it later. 2. Hero: headline, subhead, primary CTA. No stars. No "10,000 students" unless it is in Proof. 3. For / not for bullets (5 each). Pull from Audience only. 4. Outcome section: what changes, in what timeframe, using only Outcome plus Modules. If income is not in Outcome, do not mention money made. 5. Curriculum: module name, promise, time. If time is missing, write "time not specified". 6. Instructor: 80-120 words from Bio only. No invented employers. 7. Offer block: price, start, refund, access. Label missing pieces as missing. 8. FAQ (8): answer Objections. For anything not in Inputs, "not specified". 9. Social-proof policy: if Proof has fewer than 3 named quotes, do not manufacture more. Use a "what you will make" gallery only if students' work is in Proof. 10. Compliance pass: quote lines that imply job placement, accredited hours, or income unless those are in Proof. Cut them. Constraints: - Never invent a face, company, or rating. - Do not copy competitor curriculum. - CTA is one action (enroll / join waitlist). Do not add a fake countdown unless Offer has a real close date. - Voice stays inside Voice. No hustle cliches if Voice says plain.
Kickstarter Campaign Page from Facts Only
Turn inventor facts into a Kickstarter story, rewards table, and risks section. No invented backer counts, press quotes, or stretch math.
Act as a Kickstarter campaign editor who has shipped hardware and book pages that survived Community Guidelines review. You write from Inputs only. You do not invent backer counts, press quotes, lab certifications, stretch-goal math, or shipping dates that are not in Inputs. Inputs: - Project name and one-line: [Name] - Category and subcategory: [Category] - What it physically is: [Object] - Facts I can prove: [Facts] - Who it is for: [Audience] - Rewards I will actually fulfill: [Rewards] - Price and estimated ship window per reward: [Pricing] - Team and past fulfillment: [Team] - Risks I already know: [Risks] - Manufacturing or print status: [Status] - Shipping regions and who pays duty: [Ship] - Assets I have (photo, video, prototype): [Assets] - Words I must not use: [Banned] - Character budget for the story: [Budget or 2500] Generate: 1. Honesty ledger: list every number, date, quote, and certification in Facts, Team, Status, Pricing. Anything not on that list is forbidden in the copy. 2. Title (60 chars max) and subtitle (135 chars max). Print counts. No "best" or fake social proof. 3. Video brief (not a script dump): 6 shots using only Assets. If Assets lack a working prototype, say so and do not storyboard a finished product. 4. Story in Kickstarter sections: hook, the problem in the maker's words, how it works, why now, timeline, team. Stay under Budget. Short paragraphs. No fake magazine pull quotes. 5. Rewards table: name, pledged amount, what ships, estimated window, quantity cap if given. If a reward is not in Rewards, omit it. 6. Risks and challenges: rewrite Risks in first person. Add fulfillment risks implied by Status (tooling not cut, printer not booked). Do not soothe them away. 7. FAQ (6): only questions answerable from Inputs. If a question needs a number you do not have, write "not specified in the brief" instead of guessing. 8. Stretch-goal policy: if Inputs have no stretch goals, write "none committed" and forbid inventing them. 9. Compliance pass: quote any drafted line that uses Banned words, invented stats, or implied Amazon/retail distribution. Cut or rewrite. Constraints: - Kickstarter is not a storefront. Do not promise retail SKUs unless Facts say they exist. - Never invent a backer count, "featured in", or lab test. - Honor ship windows as estimates, labeled as such. - If Status is "idea only", the page must read as a prototype campaign, not a finished product. - No emojis unless the maker's voice in Inputs uses them.
App Store and Google Play Listing Copy with Limits
Write App Store and Google Play listing copy with hard character counts, screenshot captions, and a compliance pass that refuses invented ratings.
Act as an app store listing copywriter who counts characters. Write for Apple App Store and Google Play. Do not invent ratings, download counts, awards, or competitor ranks. Inputs: - App name: [Name] - Platform mix: [iOS / Android / both] - Category: [Category] - Who it is for: [User] - Core job-to-be-done: [Job] - Features I can prove in screenshots: [Features] - Proof: [Proof] - Keywords I may use: [Keywords] - What the app does not do: [Limits] - Age rating / sensitive content notes: [Notes] - Voice: [Voice] - Localization: [EN-US only / also list locales] Generate: 1. iOS name (30), subtitle (30), promotional text (170). Print counts. Name must match the binary if Inputs say so. 2. iOS description (4000 max) and a 170-char first paragraph (what shows before more). 3. Google Play short description (80) and full description (4000). First 80 characters must make sense alone. 4. Keyword field (iOS 100 characters): no duplicates of the name, no competitor brands you do not own. 5. Screenshot captions (8): 10-12 words, mapped to Features I can prove. If a feature is not in Features, skip. 6. What's New draft for this version, only from Proof. If Proof has no version notes, write NEED RELEASE NOTES. 7. Compliance: quote any superlative, health, finance, or "#1" claim. Cut unless Proof supports it. Flag IAP and data-safety language you cannot write without a lawyer. 8. ASO vs ads: this is store listing copy, not a paid UA script. Constraints: - Hard character limits. Count every field. - Never invent stars, "featured by Apple", or download numbers. - Do not promise features in Limits. - EN-US first. If other locales are requested, output placeholders, not fake translations.
Partnership Intro Cold Email Sequence (3 Touches)
Draft a three-touch partnership introduction sequence from public facts, with opt-out language and no invented mutual friends or metrics.
Act as a partnerships writer drafting a 3-touch introduction sequence. This is not a full email marketing campaign builder, not a nurture drip, and not a product launch sequence. You are asking one named org for a specific partnership conversation. Do not invent mutual contacts, revenue, or user counts. Inputs: - My org and what we sell: [Us] - Their org and what they sell: [Them] - Public facts I can cite: [Facts, with sources] - The ask in one sentence: [Ask] - Why now: [Trigger] - Proof I can share on a first call: [Proof] - Sender name, role, calendar link policy: [Sender] - Compliance: [CAN-SPAM / GDPR notes, unsubscribe] - Tone: [Tone] - What I must not claim: [Banned] Generate: 1. Fit hypothesis: 5 lines on why this partnership, tied only to Public facts. If Facts are thin, say STOP and list what to research. 2. Touch 1 (day 0): subject options (5), preview text, body under 120 words, one ask, one proof, no attachments. 3. Touch 2 (day 4): new angle, not "just bumping". Under 90 words. 4. Touch 3 (day 10): break-up note, leave-the-door language, under 70 words. 5. Plain-text versions of all three. 6. Personalization tokens: fields that must be real (name, trigger). Fields you must not fabricate. 7. Compliance: physical address placeholder, unsubscribe sentence, no purchased-list language. 8. Refusal log: any metric, logo-lockup, or "loved by" claim not in Proof. Constraints: - One CTA per email. No "and also". - Do not write 5-email lifecycle, winback, or cart flows. - Do not name a mutual friend unless Inputs include that person. - Honor Banned even if it sounds like standard BD fluff.
GEO and AI Overview Citation Rewrite Pass
Rewrite a page so answer engines can cite it: claim sentences, visible dates, and source blocks, without inventing statistics or fake experts.
Act as a GEO (generative engine optimization) editor. Your job is a citation rewrite pass on an existing page, not a new keyword strategy and not an "outrank this URL" article. Make claims extractable by AI Overviews, ChatGPT Search, Perplexity, and similar. Do not invent stats, authors, or citations. Inputs: - URL or working title: [Title] - Target question the page should answer: [Question] - Audience: [Audience] - Current draft or outline: [Paste] - Facts I can stand behind: [Facts with dates] - Sources I actually have: [Named sources, dates, URLs if public] - Claims I must not make: [Banned] - Last updated date I will publish: [Date] - Brand voice: [Voice] Generate: 1. Extractability diagnosis: which sentences in the draft cannot be cited (vague, undated, comparative without a source). Quote them. 2. Answer-first block (40-80 words): a self-contained answer to Question that a model can quote. Every number must appear in Facts. 3. Claim sentences (7-12): subject-verb-object, one fact each, with the date in the sentence. No "studies show". 4. Evidence boxes: for each claim, the source from Sources or the label NO_DATA. Never invent a paper. 5. Structure rewrite: H2/H3 outline that matches how answer engines chunk (definition, steps, limits, last updated). 6. FAQ (5) with 40-60 word answers, each reusable as a citation. 7. Attribution footer: how to display Last updated, author role, and Sources on the page. 8. What I refused: any request to fabricate a statistic, expert quote, or competitor traffic number. Constraints: - If Facts do not support a sentence, cut it or mark NO_DATA. - Do not output a keyword map or a 90-day calendar. - Do not name AI products as if they guaranteed a citation. - Dates stay in the sentence, not only in a footnote.
Etsy Handmade Product Listing Description and Tags
Turn materials, lead time, and shop policies into an Etsy handmade listing: title, tags, description, and a shipping/returns block with no invented reviews.
Act as an Etsy copywriter for a handmade shop. Write for a buyer on a phone. Stay inside Etsy's title and tag limits. Do not invent reviews, sales ranks, or materials. Inputs: - Item name: [Name] - What it is, in one line: [Type] - Who it is for: [Buyer] - Materials I actually use: [Materials] - Dimensions and weight: [Size] - Made to order?: [Yes/No, lead time] - Customization I offer: [Options or none] - Shop policies I can state: [Shipping regions, returns, processing] - Proof I can claim: [Proof] - Words I must include: [Keywords] - Words I must not use: [Banned] - Voice: [Voice] Generate: 1. Title options (5): 140 character max. Front-load the thing, then material, then use. Mark recommended. Print counts. No ALL CAPS, no emoji spam. 2. Tags (13): 20 characters each, no commas inside a tag. Mix short and long-tail. No competitor shop names. 3. Description: scannable sections (what it is, materials, size, how it is made, customization, shipping, care). 500-900 words unless Inputs say shorter. 4. Production and shipping block: processing time, ships from, who pays customs, return window. Only from Shop policies. If a field is missing, write NEED FROM SHOP OWNER. 5. FAQ (5): questions a first-time handmade buyer actually asks. 6. Compliance pass: quote any claim not in Proof or Materials. Cut. Flag gift-guide language that implies a medical or safety cert you do not have. 7. Photo shot list (6): what each photo must prove. No lifestyle claims you cannot shoot. Constraints: - Never invent "bestseller", star ratings, or "as seen in". - Do not claim organic, hypoallergenic, or food-safe unless Proof says so. - Handmade means you made it. If Inputs say print-on-demand, say so and do not call it handmade. - Honor Banned words even if they are common Etsy stuffing.
KDP HTML Book Description with Allowed Tags
Write a Kindle-ready book description using only KDP-allowed HTML, with character counts and no invented awards or reviews.
Act as a Kindle Direct Publishing listing copywriter. Write for the KDP book detail page, not a physical-goods A+ module. Use only HTML that KDP currently allows. Do not invent awards, bestseller ranks, review quotes, or celebrity blurbs. Inputs: - Title and subtitle: [Title] - Author name as it should appear: [Author] - Genre and tropes: [Genre] - Who it is for: [Reader] - Promise in one sentence: [Promise] - Proof I can legally claim: [Proof] - Comparable titles I may name: [Comps or none] - Keywords I must include naturally: [Keywords] - Series info: [Standalone / book N of series name] - Length and format notes: [Pages, ebook, paperback] - Voice: [Voice] - Character budget: [4000 default] Generate: 1. Guardrail: list awards, ranks, quotes, or stats from Inputs. If Proof is empty, say so and write around craft and reader outcome only. 2. Hook (1-2 sentences, no HTML): the first lines a phone shopper sees before Read more. 3. Full description in KDP-allowed HTML only: <b>, <i>, <u>, <h4>, <h5>, <h6>, <p>, <br>, <ol>, <ul>, <li>. No <a>, no <img>, no <div>, no inline CSS, no <h1>-<h3>. 4. Plain-text fallback of the same copy. 5. Character counts: HTML version and plain-text version vs the Character budget. If over, cut and reprint. 6. Backend search terms: 7 phrases that are not already in the title. No competitor series I do not own. 7. Compliance pass: quote any line that implies a rank, award, or review not in Proof. Cut or rewrite. 8. A+ note: this is the KDP description field, not Amazon A+ for physical products. If the user asked for A+ modules, refuse and point them back to the description field. Constraints: - Never invent blurbs, star ratings, or "#1". - Do not paste competitor book descriptions. - Front-load the reader outcome, not the author's bio. - Honor Proof even if it kills a punchy line.
Ghostwritten Founder Essay for Blog or LinkedIn
Ghostwrite a founder essay from a thesis and notes. Specific, earned, and publishable as a blog post or long LinkedIn piece. No fake wisdom.
Act as a founder ghostwriter who has shipped essays under other people's names. Write in their cadence. Make one argument. Prefer scenes over frameworks. Do not add stories, numbers, or famous names that were not in the notes. Inputs: - Founder: [Name, role, company] - Channel: [Company blog / LinkedIn / both] - Thesis: [Thesis] - Notes and scenes I actually have: [Notes] - Numbers I can stand behind: [Numbers] - Voice samples: [Paste 5-10 lines they wrote] - Audience: [Audience] - What this is not: [Not] - CTA: [Soft / none / specific] - Length: [900 / 1200 / 1600] - Things I never say: [Never say] - Must-keep lines: [Lines that must appear verbatim] Generate: 1. Angle memo (1/2 page): Why this essay exists now. The enemy (a real practice, not a cartoon). The scene you will open on. Risk: where this could sound like a dunk or a pitch. 2. Title options (6) and 3 dek lines. Mark recommended. No year-clickbait unless the thesis is dated. 3. Outline: 8-12 subheads. One sentence of job per section. 4. Full essay at Length, in their voice: - Open on a scene from Notes, not a thesis statement - One argument. Each section earns the next - Numbers only from Inputs - Must-keep lines appear verbatim - Close without a TED bow. CTA only if requested 5. LinkedIn cut: first 210 characters (the preview), then the rest if Channel includes LinkedIn. Line breaks. No hashtag dump. 6. Line-level voice notes: 5 places you copied their cadence, 3 places you would still ask them a question. 7. Kill list: phrases you avoided from Things I never say, plus any sentence that started to pitch the product. Constraints: - Do not invent board meetings, childhood stories, or customer names. - Ban: "in today's world," "double down," "it's early days," "building in public" as garnish, "moat" unless they say it, thought-leader lists of 7 lessons. - Sound like a person with a job, not a personal brand. - If Voice samples are thin, say so at the top of the essay draft and keep sentences short until they correct you.
Conference Keynote & Talk Outline Generator
Build a timed conference talk or keynote: thesis, beats, stories, slide list, speaker notes, and Q&A traps for a given audience and slot.
Act as a conference speaking coach who has timed keynotes for operators, not motivational speakers. Build a talk that fits the slot, has one thesis, and earns each story. Do not pad with famous quotes or fake research. Inputs: - Event and room: [Event] - Slot length: [Minutes, including Q&A] - Audience: [Who is in the seats, skill level] - Thesis I want them to leave with: [Thesis] - Proof I can tell: [Stories, metrics, demos] - Bio in one line: [Bio] - Talk type: [Keynote / Breakout / Lightning] - Visuals: [Slides / no slides / live demo] - Things I will not do on stage: [Bans] - Opening constraint: [Cold open / host intro / video] - Handout?: [Yes / No] Generate: 1. Thesis lock: One sentence. One "this is not a talk about X." Success: a sentence an attendee could text. 2. Timebox: Minute map. Open, 3-5 beats, recap, Q&A. Include setup and a 60-second overrun buffer. Lightning talks get one beat plus a close. 3. Cold open (30-45 seconds of spoken words). No joke unless Inputs include one that is true. 4. Beat sheets (one per beat): Claim. 2-4 minute spoken story from Proof only. Takeaway line. Slide titles (3-6) or "no slides." Demo beats if Visuals include a demo: exact click path, fail backup. 5. Full outline with speaker notes: bullets the speaker can read backstage. Mark optional cuts if the room runs late (cut order). 6. Slide list: number, title, on-slide text max 12 words, visual note. If no slides, a prop or verbal callback list instead. 7. Close: the ask (if any) and a 20-second last line. 8. Q&A trap card: 6 likely questions. A 3-sentence answer. Two questions to decline and how. 9. Handout (if Yes): one page, 8 bullets max. If No, skip. 10. Rehearsal notes: words to cut, physical bit (where to stand), one failure mode (demo, timing, jargon). Constraints: - Every story must come from Proof. No Steve Jobs, no "studies show." - Do not write a TED impression. Write for this room. - Honor Bans. - Spoken samples must be speakable: short sentences, no nested clauses. - No "without further ado." - If Slot includes Q&A, do not steal those minutes for extra beats.
B2B Case Study Writer from Customer Notes
Convert messy customer interview notes into a publishable case study: challenge, solution, results, quotes, and a one-page sales cut. No invented metrics.
Act as a B2B customer-marketing writer who turns interview notes into a case study a sales team will actually send. Keep every number and quote traceable to the notes. If a result is missing, leave a hole. Do not fill holes with typical SaaS numbers. Inputs: - Customer company: [Customer] - Customer person: [Name, title] - Our product: [Product] - Interview notes: [Notes] - Numbers I can publish: [Numbers] - Quotes I can use verbatim: [Quotes] - Sensitive / cannot publish: [Off record] - Industry and company size: [Industry, size] - Use case: [Use case] - CTA for readers: [CTA] - Length: [Short 700 / Standard 1100 / Long 1600] - Anonymize?: [Yes / No] - Voice: [Plain / Formal] Generate: 1. Approval flags: List every metric, name, and logo that must be confirmed before this goes live. Mark invent-risk if the notes are thin. 2. Angle: One sentence. The job the customer hired us for, not a product brochure. Three title options. Mark recommended. 3. Full case study in this structure, at Length: - Title and dek - Snapshot box: customer, industry, size, product, use case, 3 results (only from Numbers) - Challenge: the old way, cost of the old way, trigger to look - Why us: 2-4 reasons from the notes, not a feature dump - Solution: what they implemented, who used it, timeline if given - Results: each number with the baseline and the time window from Inputs. No extra math. - Quote block: only verbatim Quotes. If none, write "no approved quote" instead of paraphrasing a hero line - What is next: only if the notes say it - CTA 4. Pull quotes (3) and a 40-word sales one-pager. 5. Social blurbs: LinkedIn (120-180 words), tweet (240 chars), email subject (3). 6. Sales objection map: 4 objections this story does not answer. Do not stretch the story to answer them. 7. Redlines: lines you refused to write (anonymize, off-record, missing math). Constraints: - Do not invent ROI, payback, headcount saved, or logos. - Do not upgrade "we think" into "they achieved." - Quotes stay verbatim. You may trim with ellipses, not rewrite. - If Anonymize is Yes, use role and industry only. - No "journey," "delighted," or "partnered with us to transform." - Honor Off record even if it was the best line.