AI Prompts for Content Writers

Write a 1,200-word blog post using the TRACE framework.

Task: Write an in-depth, SEO-optimised blog post on [topic].
Requirements: Include H2 subheadings, a compelling introduction that hooks the reader within 2 sentences, actionable takeaways in each section, and a conclusion with a CTA.
Audience: [describe audience, e.g. 'early-career marketers who know the basics but struggle with strategy']
Context: The post will be published on [blog/company name]. Competitors rank for this topic but their posts are generic — this one should be more specific and practical.
Examples: Similar in tone to [e.g. HubSpot, First Round Capital, or a writer you admire].

Provide: title (3 options), meta description (155 chars), full post with headings.

Write the following content in a specific brand voice using the CRISP framework.

Context: [what the piece is — e.g. 'a weekly newsletter for indie founders']
Role: You are a [e.g. 'sharp, opinionated tech writer who has shipped 3 products']
Intent: To [e.g. 'teach one actionable insight per issue without being preachy']
Style: [e.g. 'conversational, uses em dashes and parentheses, short punchy sentences, never uses the word 'leverage'']
Parameters: [e.g. '400–500 words, end with a single reflection question, no bullet points']

Content to write: [paste your topic or rough notes here]

Write a thought leadership piece using the PREP framework.

Point: State a clear, specific, and potentially controversial position on [topic]. Not a hedged opinion — take a real stance.
Reason: Give the primary reason this is true. Back it with logic or evidence.
Example: Provide a concrete real-world example that proves the point.
Point (restated): Bring the argument home with a punchy restatement.

Format: LinkedIn article or blog post. 350–500 words. The opening line must work as a standalone hook for social sharing.

Create a detailed SEO blog post outline using the APE framework.

Action: Create a complete, SEO-optimised outline for a post targeting the keyword '[target keyword]'.
Purpose: To rank on page 1 for '[keyword]' while genuinely answering what the searcher wants to know — not padding for length.
Expectation:
- Title (3 H1 options with keyword)
- Meta description (155 chars)
- Introduction approach (hook angle)
- 5–7 H2 sections with 2–3 bullet points per section showing what to cover
- Internal linking suggestions
- FAQ section (3 questions from 'People Also Ask')
- Word count recommendation

Search intent for this keyword: [informational/commercial/navigational]

Write a weekly newsletter issue using the ERA framework.

Execution: Write a newsletter on [this week's topic/story]. Lead with the most interesting angle, not a summary.
Results: What should the reader walk away knowing or being able to do that they couldn't before reading?
Audience: [describe subscribers — who they are, what they care about, why they subscribed]

Format:
- Subject line (3 options)
- Preview text (90 chars)
- Opening hook (2 sentences max)
- Main section (250–350 words)
- One takeaway or action item
- Closing sign-off in brand voice

Tone: [e.g. warm + expert / irreverent + practical / calm + authoritative]

Edit the following draft using the CLEAR framework to make it significantly better.

Clarity: Identify and rewrite any sentence that requires re-reading to understand.
Language: Remove jargon, passive voice, and filler words (very, just, really, in order to).
Examples: Flag any claims that need a supporting example and add one where possible.
Audience: Adjust tone and vocabulary so it matches [audience description].
Requirements: The final version should be approximately [word count], include [specific elements if any], and end with [desired call to action or closing].

Here is the draft:
[PASTE YOUR DRAFT HERE]

Write a Twitter/X thread using the TRACE framework.

Task: Write a thread on [topic] that gets saves and retweets.
Requirements: 8–10 tweets. Tweet 1 must be a hook that makes someone stop scrolling. Each tweet should be a standalone idea. Thread must end with an engagement CTA.
Audience: [describe your Twitter audience and what they follow you for]
Context: [your niche/angle — e.g. 'bootstrapped SaaS founder', 'content strategist', 'developer turned PM']
Examples: Style similar to [@handle you admire] but original in content.

Also write: an alternate hook tweet (in case the first doesn't perform) and a note on the best time to post for this audience.

Repurpose the following content into multiple formats using the APE framework.

Action: Take the blog post below and repurpose it into 5 different content formats.
Purpose: Maximise reach from a single piece of original research/writing across different channels without it feeling like copy-paste.
Expectation: Produce all 5 formats:
1. LinkedIn post (200 words, first-person, conversational)
2. Twitter/X thread (6 tweets)
3. Short-form video script (60 seconds, hook + 3 points + CTA)
4. Email newsletter snippet (150 words, personal tone)
5. Instagram carousel concept (slide-by-slide outline)

Original blog post:
[PASTE POST HERE]

Write an origin story / personal narrative using the CRISP framework.

Context: [The situation or moment the story begins — setting, stakes, what was at risk]
Role: You are telling this story as [who you are — profession, background, perspective]
Intent: The story should make the reader feel [emotion] and understand [lesson/message]
Style: [e.g. 'vulnerable and honest, uses specific sensory detail, avoids inspirational-poster language']
Parameters: [300–500 words, present tense where possible, end on action not reflection]

Key moments to include:
- The problem or turning point: [describe]
- The lowest moment: [describe]
- The resolution: [describe]

Write a [product/book/tool] review using the PREP framework.

Point: State your overall verdict clearly in the opening — don't make the reader wait.
Reason: Give the 2–3 main reasons that lead to your verdict. Be specific, not generic.
Example: For each reason, give a concrete example from actual use (feature, quote, scenario).
Point (restated): Close with a clear recommendation — who should and shouldn't buy/read/use it.

Product/book/tool: [name]
My experience: [briefly describe how you used it and for how long]
Audience for the review: [who will read this]

Format: 400–600 words. No score/stars needed — make the recommendation clear through the writing.