What makes a good AI writing prompt?

Four parts: a role that sets the standard of judgment, constraints that rule out the generic version, an explicit structure for the output, and quality bars the draft must clear. In practice that lands at 80–150 words. The templates on this page carry all four parts pre-written; you supply only the topic, audience, and tone.

How long should an AI prompt be?

For article-length writing, 80–150 words is the working range — long enough to specify structure and quality bars, short enough that every sentence still constrains the output. Under about 30 words the model has to guess at length, audience, and format, and it guesses the average. Past 300 words, instructions start contradicting each other.

Do these prompts work with ChatGPT, Claude, and Gemini?

Yes. All 30 templates are plain-language instructions with no model-specific syntax, so they run unchanged in ChatGPT, Claude, Gemini, or any chat model. The templates with [PASTE TEXT] slots benefit from long-context models, which is the only practical difference between providers here.

Why does AI writing sound so generic?

Because an unconstrained model reproduces the most statistically typical version of the request — the average blog post, which is mediocre by definition. Generic output is almost always a prompt problem: no banned phrases, no required specifics, no stated reader. The fix is constraints, which is most of what these templates are.

Is my topic sent to a server when I generate prompts?

No. The tool fills the templates deterministically in your browser — no AI call, no network request, and it keeps working offline. What you paste into your AI tool afterwards is governed by that provider’s terms, so keep confidential material out of prompts you send to third-party models.

AI Writing Prompts Generator

30 expert prompt templates for articles, outlines, headlines and rewrites.

Why “write me a blog post about X” fails

A language model answers an underspecified request with the most statistically typical response — and the typical blog post is mediocre by definition. Ask for “a blog post about email deliverability” and the model must guess the length, the reader, the depth, the format, and the stakes. It resolves every one of those guesses toward the average of its training data: a 700-word listicle voice, an introduction about how important email is in today’s digital landscape, three obvious tips, a summary that repeats them. Nothing went wrong. You asked for the average and received it.

The failure is not a model limitation, which is why switching tools does not fix it. It is a specification gap, and it closes the same way a briefing gap with a human freelancer closes — with a role, constraints, structure, and a bar the draft must clear.

The anatomy of a strong prompt

Every template in this generator is built from the same four parts. Here is the difference they make, side by side:

Weak	Strong
Write a blog post about email deliverability.	You are a senior content editor at a publication known for practical, zero-fluff writing. Write a 1,200-word post about email deliverability for indie SaaS founders. State the reader’s payoff in the first two sentences; add an H2 every 250–300 words; include a concrete number, example, or named tool in every section; end with one specific next step. Banned: “in today’s fast-paced world”, rhetorical questions as transitions, any sentence that could appear unchanged in an article on a different topic.

Weak

Strong

Write a blog post about email deliverability.

You are a senior content editor at a publication known for practical, zero-fluff writing. Write a 1,200-word post about email deliverability for indie SaaS founders. State the reader’s payoff in the first two sentences; add an H2 every 250–300 words; include a concrete number, example, or named tool in every section; end with one specific next step. Banned: “in today’s fast-paced world”, rhetorical questions as transitions, any sentence that could appear unchanged in an article on a different topic.

Role. “You are a senior content editor at a publication known for zero-fluff writing” is not decoration — it selects which pocket of the model’s training to imitate. A named standard of judgment beats an unnamed one.
Constraints. Word count, audience, tone, and above all the ban list. Prohibiting stock phrases and topic-agnostic sentences removes the model’s cheapest failure mode before it happens.
Structure. H2 cadence, paragraph limits, what the ending must contain. Models follow explicit output shapes with high reliability; implied shapes, almost never.
Quality bars. Rules the draft must survive: an example or number in every section, claims that could only come from doing the work. These give you objective grounds for revision instead of “make it better”.

Adapting the templates to your model

The templates are deliberately model-agnostic — plain instructions, no vendor syntax — so they run unchanged in ChatGPT, Claude, Gemini, or anything else with a chat box. A few adjustments pay off at the margins. Long-context models handle the templates with [PASTE TEXT] and [PASTE ARTICLE] slots best; paste the full source rather than a summary, because the model can only be specific about material it has actually seen. If you work through an API, put the role sentence in the system prompt and keep the task in the user message. And when a model drifts from the requested structure, do not regenerate and hope — restate the one constraint it broke and ask it to revise. Repetition of constraints is cheap; re-rolling the dice is not a strategy.

What does not transfer between models: none of them can supply your facts. Every template treats missing information honestly — stat-led prompts instruct the model to output a marked [STAT + SOURCE] placeholder rather than invent a number, and the case-study prompts mark missing facts as [MISSING] instead of fabricating. Keep those guardrails when you edit the templates. A model that is forbidden to invent is a drafting tool; one that is allowed to invent is a liability with good grammar.

An iteration workflow that converges

The first output is raw material, not a verdict. The workflow that reliably gets from template to publishable draft:

Generate with the template as-is. Read the draft once without editing.
Mark the three standard failure modes: claims with no evidence, hedged positions, and sentences that would fit any article on the topic.
Reply with targeted instructions, one per problem — “replace the example in section two with a concrete scenario for a five-person team”, “cut the introduction to 60 words”, “take a position in the pricing section”. Targeted edits preserve what already works; “try again” throws it away.
Ask the model to audit its own draft against the prompt’s quality bars and list what fails. Models are noticeably better at finding violations than at avoiding them, and the list becomes your next revision instruction.
Do the final pass yourself: verify every number, every named tool, every claim. This step does not delegate.

Two or three targeted revision turns beat ten regenerations, in both quality and time. If you are still regenerating after three attempts, the prompt is missing a constraint — go back one level and fix the specification, not the output.

What the 30 templates encode

The generator holds 30 templates across 10 categories — three each for blog posts, outlines, introductions, headlines, meta descriptions, social threads, newsletters, rewrites, landing pages, and case studies. The three within a category are different editorial strategies, not variations: the blog-post set, for instance, covers a standard publication-grade post, a contrarian argument with a steelman requirement, and a first-hand experience piece that bans secondhand claims. Your topic, audience, tone, word count, and keyword fill the slots; if you leave the keyword blank, the sentences that reference it are removed cleanly instead of leaving a hole. Nothing here calls a model — the output is the prompt, finished and ready to paste wherever you draft.

Frequently asked questions

What makes a good AI writing prompt?: Four parts: a role that sets the standard of judgment, constraints that rule out the generic version, an explicit structure for the output, and quality bars the draft must clear. In practice that lands at 80–150 words. The templates on this page carry all four parts pre-written; you supply only the topic, audience, and tone.
How long should an AI prompt be?: For article-length writing, 80–150 words is the working range — long enough to specify structure and quality bars, short enough that every sentence still constrains the output. Under about 30 words the model has to guess at length, audience, and format, and it guesses the average. Past 300 words, instructions start contradicting each other.
Do these prompts work with ChatGPT, Claude, and Gemini?: Yes. All 30 templates are plain-language instructions with no model-specific syntax, so they run unchanged in ChatGPT, Claude, Gemini, or any chat model. The templates with [PASTE TEXT] slots benefit from long-context models, which is the only practical difference between providers here.
Why does AI writing sound so generic?: Because an unconstrained model reproduces the most statistically typical version of the request — the average blog post, which is mediocre by definition. Generic output is almost always a prompt problem: no banned phrases, no required specifics, no stated reader. The fix is constraints, which is most of what these templates are.
How many prompt templates does this tool include?: 30 templates across 10 categories — blog posts, outlines, introductions, headlines, meta descriptions, social threads, newsletters, rewrites, landing pages, and case studies — three per category, each encoding a different editorial strategy.
Is my topic sent to a server when I generate prompts?: No. The tool fills the templates deterministically in your browser — no AI call, no network request, and it keeps working offline. What you paste into your AI tool afterwards is governed by that provider’s terms, so keep confidential material out of prompts you send to third-party models.

Free download

The Pre-Publish Checklist

A good prompt starts the draft. The checklist ships it. 47 checks WriteZu runs before an article ships — as a checklist you can run by hand.

No spam. The checklist, then only what's worth knowing.

Blog Outline GeneratorProven article structures for how-tos, listicles, comparisons and guides.Headline AnalyzerScore any headline 0–100 on length, power words, emotion and type — with fixes.Readability CheckerFlesch reading ease, grade level, and the exact sentences that drag you down.

WriteZu does this automatically — for every article

It reads your site, maps the topics you can win, writes the calendar, and publishes articles that pass every check on this page — scored and revised before you ever see them.

Start free