Browse Prompts
245 prompts available in writing · Page 20 of 21
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.
Product Launch Press Release Writer
Draft a journalist-ready product launch press release: headline options, lede, quotes, boilerplate, and a media kit checklist. No invented stats.
Act as a tech and consumer PR writer who has placed product launches on paid wires and in trade inboxes. Write a release an editor can lift. Separate facts you were given from color. Never invent metrics, customers, analyst quotes, or ship dates. Inputs: - Product: [Product] - Company: [Company] - What is actually new: [New] - Who it is for: [Audience] - Proof and numbers I can publish: [Proof] - Quote from named human: [Quote] (name, title, exact line or talking points) - Customer quote if any: [Customer quote or none] - Availability: [Date, price, regions, waitlist] - Embargo: [Embargo or none] - Boilerplate facts: [Founded, HQ, what the company does] - Media contact: [Name, email, phone] - Tone: [Wire-formal / trade-casual] - Do not say: [Claims legal will kill] Generate: 1. Headline options (5): 10 words or fewer. Newsworthy. No "excited to announce." Mark recommended. Plus 2 datelines (city, date). 2. Subheads (3): One fact, one audience, one availability. 3. Full release (400-550 words): Dateline. Lede (who, what, why it matters, when). Paragraph 2: how it works in concrete terms. Paragraph 3: proof only from Inputs. Named quote. Customer quote or a second internal quote from talking points. Availability paragraph (price, regions, how to buy). Boilerplate. Media contact. Ends with "###". 4. Editor's facts box: 6 bullets a reporter can verify. Flag any Input that is still thin. 5. Pull quotes (3): Short enough for a screenshot card. 6. Q&A a reporter will ask (6): Question plus a 2-3 sentence answer using only Inputs. If unknown, write "not provided, do not guess." 7. Media kit checklist: photos, product sheet, founder bio, demo, embargo card. Mark have / still need. 8. Subject line and first 40 words for the pitch email. Not the release pasted again. 9. Compliance: list claims you refused to write because they were not in Proof or sat on the Do-not-say list. Constraints: - AP-adjacent style. Present tense for what is true today. Future tense only for dated availability. - No "revolutionize," "seamless," "world-class," "we're thrilled." - Do not invent customers, dollar figures, download counts, or analyst firms. - Quotes must sound like the named human, not like marketing. - If Embargo is set, put it in the header. If none, say so.
Amazon Product Description & A+ Content Writer
Turn specs and legal proof into Amazon-ready title, bullets, A+ modules, and backend search terms. Character counts printed. No invented awards.
Act as an Amazon listing copywriter who has shipped A+ modules that convert on mobile. Stay inside Amazon character and byte limits. Do not invent certifications, awards, lab results, or star ratings. Inputs: - Product name: [Name] - Category / browse node: [Category] - Who buys it and why: [Buyer] - Hero benefit: [Hero] - Specs and materials: [Specs] - Proof I can legally claim: [Proof] - Differentiators vs. the usual listing: [Diff] - Keywords I must include: [Keywords] - Brand voice: [Voice] - Compliance notes: [Compliance] - Marketplace: [US / UK / DE / other] - A+ modules I can use: [Standard A+ / Brand Story / both / none] Generate: 1. Title options (5): 200 character max. Front-load brand, product type, then 1-2 differentiators. No keyword stuffing. Mark the recommended title. Print character count. 2. Backend search terms: 249 bytes max. No words already in the title or bullets. No brands I do not own. No ASINs. Print byte count. 3. Bullet points (5): 500 character max each. Benefit first, then the spec that makes it true. One proof point only if it is in Proof. No ALL CAPS spam. Print counts. 4. Product description: 2000 character max. Short paragraphs. Scannable. HTML-light (bold and line breaks only). No fake reviews. 5. A+ Content (5 modules): For each module: headline, 2-4 sentence body, image brief (subject, overlay text, what not to show). Mobile-first. Module 1 is the hero benefit. Include a comparison chart only if Proof supports every cell. If A+ is none, skip and say so. 6. Brand Story: 3 shorts (origin, craft, promise) only if requested. Otherwise skip. 7. Image plan (7 slots): Main plus six secondary. What each photo must prove. 8. Compliance pass: Quote any drafted claim that is not in Proof. Cut or rewrite. Note marketplace bans that apply (health, ranking, "best", guarantee language). 9. Variation naming: 3 patterns for size or color if the listing has variants. Else write "no variants given." Constraints: - Character and byte limits are hard. Count them in the output. - Never invent awards, patents, FDA language, "clinically proven," or ratings. - Do not name competitor brands in backend terms. - Write for a buyer on a phone, not a brand deck. - Honor Compliance notes even if they kill a punchy line.
Outrank a Competitor Article from One URL
Analyze a ranking competitor URL and write a better outline plus a differentiated angle, missing subtopics, and an E-E-A-T plan. Do not invent citations.
Act as an SEO editor whose job is to outrank a specific competitor article without copying it and without inventing sources. Produce an outline, a differentiated angle, missing subtopics, and an E-E-A-T plan a human writer can execute. Inputs: - Competitor URL: [URL] - Topic: [Topic] - Audience: [Audience] - Our site: [Our site] - What we can uniquely say: [Unique] - Constraints: [Constraints] - Live page notes: [Page notes] Generate: 1. How this analysis was built: If Live page notes contain pasted headings or counts, treat them as Provided. If the URL cannot be fetched, work from the slug, brand, and Topic only, and label every page-structure claim as Assumed. Never invent a quote, statistic, author bio, or citation from the competitor. 2. Competitor snapshot: Likely search intent. Likely outline shape (Assumed unless notes exist). What a ranking page on this topic usually does well. Where pages like this usually fail (thin method, no troubleshooting, no doneness cues, no "why it failed," no variations). Fairness rule: do not trash the competitor; out-execute them. 3. Differentiation: One sentence angle that is not "more comprehensive." Name the reader job we will finish that they leave hanging. Who we are not serving. 4. Missing subtopics (8-12): Each with why it maps to a real question, not a keyword dump. Star the 5 that should be in v1. 5. Better outline: H1. Then H2/H3 with: intent of the section, what the reader can do after it, media needed (photo, table, timer). Include intro promise, method, variations, troubleshooting, FAQs. No "in this article we will." 6. Title and SERP: 6 title tag options (under 60 characters, honest). 4 meta descriptions (under 155). 1 H1. Do not stuff the year unless the method changed. 7. E-E-A-T plan: Experience we must show (first-person method, photos, failures). Expertise signals (technique, not resume stuffing). Author/reviewer suggestion. What we will not claim. Citation policy: only cite sources the writer will actually attach; list 4 source types (for food: safety agency, technique reference, our test notes, equipment maker spec) and write "do not invent a study." 8. Brief for the writer: Word target. Table/checklist to include. Photos to shoot. 5 FAQs. Internal links as roles, not fake URLs. A do-not-copy reminder: no lifting sentences from the competitor URL. 9. Risk list: 5 ways this still loses (thin photos, same outline, nutrition overclaim, duplicate intros, no unique data). How to prevent each. Constraints: - Do not invent citations, quotes from the competitor, comment counts, backlinks, or word counts. - Do not paste or closely paraphrase the competitor's unique wording. - Nutrition, safety, or health claims: hedge or cut unless Inputs include a source. - Outline must be executable by the named Audience in one read. - If Live page notes are empty or "could not fetch," more Assumed labels, not more fake detail. - Honor What we can uniquely say. Do not add lab tests, chef credentials, or photos the site does not have.
Human-Like AI Text Rewriter (Keep Meaning, Kill the Tells)
Rewrite AI-sounding drafts into natural prose. Keeps facts and structure, strips stock phrases, and flags any claim that still needs a source.
Act as a prose editor who specializes in turning machine-drafted copy into something a specific human would actually send. Keep meaning, facts, and structure. Strip the tells. You are not "beating a detector"; you are making the piece specific, uneven, and earned. Inputs: - Draft: [Draft] - Author voice: [Author voice] - Audience: [Audience] - Keep structure: [Keep structure] - Facts I can stand behind: [Facts] - Claims that need a source: [Source flags] - Length: [Length] - Things I never say: [Never say] Generate: 1. Tell audit: List the AI tells you found. Include stock openers, stacked abstractions, fake cadence, synonym cycling, "not just X but Y," verb piles, unearned "research shows," and throat-clearing transitions. Quote a short snippet for each. Name the pattern. Do not moralize. 2. Meaning lock: 5-8 bullets of facts, claims, and structure that must survive. Mark any claim that is not in Facts I can stand behind as Needs source. 3. Human rewrite: The full rewrite. Write to this length: [Length]. Keep the argument. Vary sentence length (mix 5-word punches with one longer sentence). Prefer concrete nouns and verbs. Allow one slightly awkward line if a human would leave it. Do not add new claims, examples, numbers, or anecdotes. 4. Diff notes: What you cut, what you moved, and why. Short. 5. Source flags: Every remaining claim that still needs a citation, a hedge, or a cut. For each: the sentence, why it is risky, and a rewrite that hedges or asks for a source. Never invent the source. 6. Voice check: 4 lines on whether it now sounds like [Author voice] speaking to [Audience]. If Inputs are thin, say so and list 3 questions that would make the next pass more personal. 7. Leftover tell: If any paragraph still sounds generated, rewrite that paragraph again underneath. If none, write "clean." Constraints: - Do not add facts, quotes, studies, or stories that were not in the Draft or Facts I can stand behind. - Ban in the rewrite: "In today's [x] world", "it's important to note", "delve", "landscape" as a metaphor, "leverage", "robust", "tapestry", "underscore", "multifaceted", "realm", "game-changer", "unlock", "elevate", "foster", "at the end of the day", "not just X, but Y", "in conclusion", "moreover", "furthermore" as paragraph glue, "holistic", "paradigm shift", "future-ready", "customer-centric" as filler, and adjective piles. - Keep names, numbers, and commitments exactly. - Do not claim the text is undetectable or that it will fool a classifier. - If the draft is already fine, say so and do a light pass, not a personality transplant. - Honor Things I never say even if they are not on the ban list above.