AI Text Generator Prompts

Write a comprehensive, SEO-optimised blog post on [TOPIC]:

Target keyword: [PRIMARY KEYWORD]
Secondary keywords: [2-3 RELATED KEYWORDS]
Target audience: [WHO IS READING THIS — expertise level, role, goals]
Word count: [1500 / 2000 / 2500 words]
Tone: [AUTHORITATIVE / CONVERSATIONAL / INSPIRATIONAL / TECHNICAL]
CTA at the end: [WHAT ACTION DO YOU WANT READERS TO TAKE]

Structure the post as:
- Compelling headline (include primary keyword, promise a specific benefit)
- Hook introduction (open with a surprising statistic, story, or provocative question)
- Problem context (why this topic matters right now)
- Main body with H2 and H3 subheadings (each section addresses a specific sub-question)
- Actionable advice throughout (specific steps, not vague guidance)
- Real examples or case studies
- Conclusion with summary and clear CTA

Avoid: generic advice that could apply to any topic, passive voice, filler phrases

Write a high-value listicle on [TOPIC]:
Format: [NUMBER] [TITLE — e.g., "10 Ways to Improve Your Team's AI Literacy"]
Audience: [WHO WILL READ THIS]
Each point should:
1. Have a specific, action-oriented heading (not "Be More Organised" — try "Block deep work time using the 90-minute focus method")
2. Open with a 1-2 sentence explanation of why this matters
3. Provide a specific, actionable technique or example (not just "you should do X")
4. Include a stat, study reference, or real-world example where possible
5. Close with a quick implementation tip ("Start tomorrow by...")

Overall tone: [TONE]
Estimated reading time target: [5 / 7 / 10 minutes]
Include intro and conclusion paragraphs around the list.

Write a thought leadership article for [TOPIC/INDUSTRY]:
Author perspective: [YOUR ROLE/EXPERTISE AND UNIQUE ANGLE]
Core argument or thesis: [WHAT COUNTER-INTUITIVE OR FORWARD-LOOKING POINT DO YOU WANT TO MAKE]
Supporting evidence: [3 KEY DATA POINTS, OBSERVATIONS, OR EXAMPLES]
Target publication: [LINKEDIN ARTICLE / INDUSTRY BLOG / NEWSLETTER / COMPANY BLOG]
Word count: [800-1200 words]

Structure:
1. Bold opening thesis (the most provocative version of your argument)
2. Why the conventional wisdom is wrong or incomplete (challenge the status quo)
3. Three evidence-based reasons your argument is correct
4. A concrete example or case study that proves the point
5. The practical implication (what should readers do differently?)
6. A memorable close that reinforces the core message

Tone: confident, specific, evidence-driven — not hedged or vague

Write a complete Facebook/Meta ad copy set for [PRODUCT/SERVICE]:
Product: [DESCRIBE WHAT YOU ARE ADVERTISING]
Target audience: [WHO ARE YOU REACHING — demographics, interests, pain points]
Campaign objective: [AWARENESS / TRAFFIC / CONVERSIONS / LEADS]
Key benefit: [SINGLE MOST IMPORTANT BENEFIT — choose one]
Offer or CTA: [WHAT DO YOU WANT THEM TO DO]

Write three ad variations:
Ad 1 — PAIN POINT: Opens by agitating the problem this product solves
Ad 2 — SOCIAL PROOF: Leads with a result or testimonial
Ad 3 — CURIOSITY/HOOK: Opens with a surprising question or bold statement

For each ad provide:
- Primary text (125 characters for mobile preview)
- Headline (40 characters)
- Description (30 characters)
- Full expanded text (for desktop — up to 250 words)
- Suggested image or video concept

Write a complete landing page copy framework for [PRODUCT/SERVICE]:
Product/service: [DESCRIBE IT]
Target customer: [WHO AND WHAT PAIN DO THEY HAVE]
Main offer: [WHAT ARE THEY GETTING]
Price point: [COST OR FREE]
Key benefits: [LIST 3-5]
Social proof available: [TESTIMONIALS / NUMBERS / LOGOS / CASE STUDIES]
Primary CTA: [SIGN UP / BUY / BOOK DEMO / DOWNLOAD]

Write all copy sections in order:
1. Hero headline + subheadline (solve the problem in 10 words)
2. Problem statement section (empathise with the pain)
3. Solution introduction (how your product solves it)
4. Benefits section (3-5 benefit headlines with short descriptions)
5. Social proof block (testimonial quotes + numbers)
6. Features breakdown (what they actually get — be specific)
7. FAQ section (address the top 4 objections)
8. Final CTA section (urgency-based close)

Write an e-commerce product description for [PRODUCT NAME]:
Product category: [CATEGORY]
Key features: [LIST 5-7 FEATURES]
Materials or ingredients: [IF RELEVANT]
Primary buyer: [WHO BUYS THIS AND WHY]
Emotional benefit: [HOW IT MAKES THEM FEEL]
Practical benefit: [WHAT PROBLEM IT SOLVES]
Price positioning: [BUDGET / MID / PREMIUM]

Deliver:
1. Short description (50-75 words — for product card/preview)
2. Full description (200-300 words — for product page)
3. Bullet point features list (5-7 bullets, benefit-led not feature-led)
4. SEO title tag (under 60 characters, includes keyword)
5. Meta description (150-160 characters)
6. Customer review-style testimonial (1 paragraph, specific and authentic-sounding)

Write an executive summary for a business report on [TOPIC]:
Full report context: [BRIEFLY DESCRIBE WHAT THE FULL REPORT COVERS]
Key findings: [LIST 3-5 KEY FINDINGS OR DATA POINTS]
Recommendations: [LIST 2-4 RECOMMENDED ACTIONS]
Audience: [C-SUITE / BOARD / SENIOR MANAGEMENT]
Decisions required: [WHAT DO YOU NEED THE READER TO DECIDE?]

Write a 300-word executive summary that:
- Opens with the single most important insight from the report
- Covers findings in order of business impact (most important first)
- Frames each finding in terms of opportunity or risk
- Presents recommendations with clear next steps and owners
- Ends with the specific decision or approval required
- Uses plain business language — no jargon or passive voice

Tone: direct, confident, decision-oriented

Write a business proposal for [WHAT YOU ARE PROPOSING]:
Client/recipient: [WHO WILL RECEIVE THIS]
Problem to solve: [THEIR CHALLENGE OR NEED]
Your proposed solution: [WHAT YOU ARE OFFERING]
Timeline: [DURATION OF ENGAGEMENT]
Investment: [BUDGET RANGE OR "TO BE DISCUSSED"]
Your credentials: [WHY YOU / YOUR COMPANY IS QUALIFIED]

Structure the proposal as:
1. Executive overview (problem + solution in 2 sentences)
2. Understanding of the challenge (show you understand their situation)
3. Proposed approach (methodology, stages, deliverables)
4. Timeline and milestones (specific dates and outputs)
5. Team and credentials (relevant experience, case studies)
6. Investment (pricing structure and what it includes)
7. Terms and next steps (how to proceed)

Tone: professional, confident, client-focused — "you" more than "we"

Write a professional email for the following situation:
Sender: [YOUR NAME/ROLE]
Recipient: [WHO YOU ARE EMAILING — THEIR ROLE AND RELATIONSHIP TO YOU]
Purpose: [WHAT THIS EMAIL NEEDS TO ACHIEVE]
Key information to convey: [LIST THE KEY POINTS]
Tone needed: [FORMAL / WARM PROFESSIONAL / ASSERTIVE / DIPLOMATIC]
Desired outcome: [WHAT ACTION OR RESPONSE DO YOU WANT]

Write an email with:
- Subject line (specific and action-oriented — avoid vague subjects)
- Appropriate greeting
- Clear opening line that states purpose immediately
- Body paragraphs organised logically (context → substance → ask)
- Specific, frictionless call to action
- Professional close
- Avoid: long paragraphs, buried ask, passive-aggressive phrasing, excessive softening

Write a short fiction scene with the following parameters:
Genre: [GENRE]
POV character: [BRIEF DESCRIPTION — personality, emotional state in this scene]
Setting: [SPECIFIC PLACE + ATMOSPHERE]
What happens in this scene: [THE KEY EVENT OR ENCOUNTER]
Emotional stakes: [WHAT DOES THIS SCENE COST OR MEAN TO THE CHARACTER]
Tone: [DARK / HOPEFUL / TENSE / WISTFUL / COMEDIC]
Word count: [500 / 800 / 1200 words]

Requirements:
- Open with a sentence that immediately puts us in the scene (no setup preamble)
- Use specific sensory detail throughout (what the character sees, hears, smells)
- Include internal thought or emotional awareness without stating emotions flatly
- Include at least one line of dialogue that reveals character
- End in a way that creates forward momentum or leaves a resonant feeling

Avoid: clichés, over-explaining, passive voice, on-the-nose emotional statements

Write a poem about [SUBJECT/THEME]:
Form: [FREE VERSE / SONNET / HAIKU SEQUENCE / VILLANELLE / PROSE POEM / ODE]
Tone: [ELEGIAC / CELEBRATORY / SARDONIC / TENDER / URGENT / MEDITATIVE]
Central image or metaphor: [OPTIONAL — a specific image to build around]
What the poem should make the reader feel: [EMOTION OR REALISATION]
Length: [SHORT — 12 lines / MEDIUM — 24 lines / LONG — 40+ lines]

Craft requirements:
- Avoid clichéd imagery (hearts, flowers as defaults — find unexpected angles)
- Use concrete, specific nouns rather than abstract ones
- Let the form serve the content — if writing a sonnet, the volta should land emotionally
- The ending should feel earned, not telegraphed
- Sound matters: read it aloud — rhythm, assonance, and consonance should work

Provide: the poem + a brief note on craft choices made

Write a screenplay scene formatted to industry standard:
Scene location: [INT./EXT. LOCATION — DAY/NIGHT]
Characters in scene: [LIST CHARACTERS WITH BRIEF DESCRIPTION]
Purpose of scene: [WHAT THIS SCENE ACCOMPLISHES IN THE STORY]
Subtext: [WHAT IS REALLY HAPPENING UNDERNEATH THE SURFACE DIALOGUE]
Scene length: [1 PAGE / 2 PAGES / 3 PAGES (roughly 1 minute per page)]

Write the scene with:
- Proper screenplay formatting (scene heading, action lines, dialogue, parentheticals sparingly)
- Action lines that are visual and present-tense ("MARA stands at the window" not "Mara was standing")
- Dialogue that is subtext-rich (characters rarely say what they mean)
- Business (physical activity) that grounds characters during dialogue
- A clear scene turn — the situation should be different at the end than at the start

Write technical documentation for [FEATURE/PRODUCT/API]:
Audience: [DEVELOPERS / END USERS / ADMINS / NON-TECHNICAL USERS]
Documentation type: [GETTING STARTED GUIDE / API REFERENCE / HOW-TO / TROUBLESHOOTING]
Technical context: [DESCRIBE WHAT THE FEATURE/PRODUCT DOES]
Key tasks users need to accomplish: [LIST 3-5]

Structure the documentation with:
1. Overview section (what this does in 2-3 sentences)
2. Prerequisites (what users need before starting)
3. Step-by-step instructions (numbered, specific, one action per step)
4. Code examples (formatted as code blocks where relevant)
5. Expected outcomes (what success looks like at each stage)
6. Common errors and troubleshooting (the top 3 things that go wrong)
7. Next steps or related documentation

Writing principles: active voice, imperative mood ("Click the button" not "The button should be clicked"), concrete examples

Write a comprehensive how-to guide for [TASK]:
Audience knowledge level: [BEGINNER / INTERMEDIATE / ADVANCED]
Platform or context: [WHERE THIS TASK IS PERFORMED]
Time required: [ESTIMATED COMPLETION TIME]
Tools or resources needed: [LIST]

Write the guide with:
1. Introduction: what the reader will achieve and why it matters (2-3 sentences)
2. What you need: tools, access, prerequisites (bullet list)
3. Step-by-step instructions:
   - Number each step clearly
   - One action per step (break complex steps into sub-steps)
   - Include screenshots guidance or visual cues where helpful
   - Explain WHY for non-obvious steps
4. Verification: how to confirm it worked
5. Troubleshooting: 3 common problems and their solutions
6. Tips and best practices (optional pro-level advice)

Avoid: assuming knowledge without stating it, multiple actions in one step, vague instructions ("configure the settings")

Write a Standard Operating Procedure (SOP) for [PROCESS]:
Department/team: [WHO USES THIS SOP]
Process name: [OFFICIAL NAME OF THE PROCESS]
Frequency: [HOW OFTEN THIS IS PERFORMED]
Owner: [WHO IS RESPONSIBLE]
Time to complete: [ESTIMATED DURATION]

SOP structure:
1. Purpose (why this process exists — 2 sentences)
2. Scope (who this applies to and what it covers)
3. Definitions (any terms that need clarifying)
4. Responsibilities (who does what — use role names not person names)
5. Procedure (numbered steps with sub-steps where needed)
6. Quality checks (what to verify at key stages)
7. Exception handling (what to do if something goes wrong)
8. Document control (version, last updated, reviewed by)

Format: formal, passive-free, consistent verb tense throughout

Write a high-performing LinkedIn post about [TOPIC]:
Your perspective or unique angle: [WHAT IS YOUR TAKE — contrarian, personal story, data-driven]
Target audience: [WHO YOU WANT TO REACH]
Core message: [THE ONE THING YOU WANT PEOPLE TO REMEMBER]
CTA: [WHAT SHOULD PEOPLE DO — comment, share, visit link, reflect]
Tone: [PROFESSIONAL / CONVERSATIONAL / INSPIRING / EDUCATIONAL]

Write the post with:
- Hook line (first line must stop the scroll — do not start with "I" or "Excited to share")
- Hook formats that work: provocative question, bold claim, surprising statistic, "X years ago..."
- Body: 4-8 short paragraphs (2-3 lines each for mobile readability)
- Use white space liberally — no long blocks of text
- Personal insight or lesson (not just information — your interpretation)
- CTA that invites engagement without being desperate ("What's your experience?")
- 3-5 relevant hashtags at the end

Word count: 150-250 words

Write a Twitter/X thread about [TOPIC]:
Core idea: [THE MAIN POINT OF THE THREAD]
Thread length: [5 / 8 / 12 tweets]
Audience: [WHO YOU ARE WRITING FOR]
Tone: [EDUCATIONAL / ENTERTAINING / PROVOCATIVE / PERSONAL]

Structure the thread:
Tweet 1 (Hook): The most compelling version of your argument — must make people want to read on
Tweets 2-[N-1] (Body): Each tweet = one idea, example, or insight. Short paragraphs, white space, specific data when possible
Tweet [N] (Close): Actionable summary, strong takeaway, or CTA

Rules for each tweet:
- Maximum 280 characters each
- Standalone readable but better in sequence
- No jargon unless your audience specifically knows it
- Numbers, specifics, and examples over vague claims
- End hook tweet with a cliffhanger or number ("Here's what I learned: (thread)")

Write an email newsletter section/edition on [TOPIC]:
Newsletter name/brand: [NAME AND BRIEF DESCRIPTION OF THE NEWSLETTER]
Subscriber audience: [WHO SUBSCRIBES]
This edition's central theme: [FOCUS FOR THIS ISSUE]
Sections to include: [INTRO / MAIN STORY / 3 LINKS / QUICK TIPS / CLOSING]

Write each section:
1. Subject line (40-50 characters — open-worthy, specific, honest)
2. Preview text (90 characters — complements subject line)
3. Greeting/intro (2-3 sentences — this week's context, what's inside)
4. Main article section (400-500 words — the core piece of value)
5. Curated links section (3 links with 2-sentence commentary on each)
6. Quick tip or insight (100 words — fast actionable value)
7. Closing personal note (3-4 sentences — human, warm, builds relationship)

Tone: [NEWSLETTER VOICE — match established newsletter brands readers would know]