The prompts that fail are not badly worded — they are incomplete. "Write a blog post about invoicing" contains no reader, no purpose, no constraint and no source, so the output supplies its own defaults and you get competent mush. Every prompt below has at least one field marked in [brackets] that does the real work. Leave it empty and the quality collapses regardless of the tool.
How to use these
Two rules that matter more than the wording. First, specify the reader and the decision they are making — a prompt that names the reader's situation outperforms one that names the topic, every time. Second, give the tool something real to work from: your notes, your figures, an existing draft. Prompts that start from your material produce usable output; prompts that start from nothing produce a first draft of the internet's average opinion.
Drafting
1. Draft from notes you already have
Here are my notes on [topic]: [paste notes]. Turn them into a [format] for [reader], who [reader's situation]. Keep my examples and figures; do not add any you cannot source from what I gave you. Length [range].
2. Draft with an explicit structure
Write a [format] on [topic] using exactly these sections: [list]. For each section, cover [what it must contain]. Reader: [who, and what they already know].
3. Draft against a competing page
Here is a page that already covers [topic]: [paste or summarise]. Write my version for [reader]. Do not mirror their structure. Cover at least two things they omit.
4. Draft in a stated voice
Write [piece] in this voice: [paste two paragraphs of your own writing]. Match sentence length, vocabulary and how the examples are framed. Do not use the phrases [list of phrases you dislike].
5. Draft with a hard constraint
Write [piece] on [topic] under [word count]. Constraint: every paragraph must contain at least one specific, checkable detail. If you cannot supply one, cut the paragraph.
6. Produce variants to choose between
Give me [number] genuinely different structures for a piece on [topic] for [reader] — different argument, not different wording. One sentence each on what each version is betting on.
Editing
7. Cut without losing meaning
Cut this to [word count] without removing any specific claim, example or figure: [paste]. List what you removed and why.
8. Find the vague parts
Mark every sentence in this draft that makes a claim without a specific subject, number or named example: [paste]. List them with a note on what each needs.
9. Break the machine rhythm
Rewrite this so it does not read as generated: [paste]. Vary sentence length deliberately, remove hedging, and delete any three-item adjective list.
10. Tighten a specific paragraph
Rewrite this paragraph to [goal: clearer / shorter / less hedged / more direct]: [paste]. Change only what serves that goal.
11. Check against your own rules
Check this draft against these rules: [list your style or compliance rules]. Report each violation with the sentence that breaks it. Do not rewrite yet.
12. Adjust for a different reader
Rewrite this for [new reader], who [their situation and what they already know]: [paste]. Keep every fact; change framing, examples and assumed knowledge.
Restructuring
13. Turn notes into an outline
From these notes, produce an outline of [number] sections: [paste notes]. For each, one line on what it argues and what evidence it needs.
14. Reorder for a decision
Reorder these sections so a reader can decide rather than just learn: [list]. Explain the new order in one sentence.
15. Find the gaps
Here is my draft and here is what it is supposed to achieve: [paste + goal]. List what is missing, weakest, or assumed without support.
16. Merge two drafts
Two drafts on the same topic: [A] and [B]. Produce one that keeps the strongest specific detail from each. List anything you dropped.
Research and preparation
17. List what you do not know
I am writing about [topic] for [reader]. List the facts, sources or figures I would need to make this credible, and flag which you cannot verify from your own knowledge.
18. Surface the objections
A [reader type] reading a piece arguing [position] would object that [list likely objections]. For each, say what evidence would answer it.
19. Extract the questions
From this material, list the questions a [reader] would actually search for: [paste]. Group by intent and drop anything too broad for one page.
20. Build a brief, not a draft
Turn this topic into a content brief: reader, intent, must-cover points, evidence I need, structure, length, and what to leave out: [topic]. Do not draft the piece.
Repurposing
21. One piece into several formats
From this piece, produce: a [format], a [format] and a [format]: [paste]. Each must stand alone and none may repeat the same opening.
22. Same content, different platform
Rewrite this for [platform], where [convention of that platform]: [paste]. Keep the substance, change the shape and length.
23. Update an old piece
Here is a piece from [date] and here is what has changed since: [paste + changes]. Update it and list everything you think is now out of date for me to verify.
24. Write the summary last
Write a [length] summary of this piece for [where it appears]: [paste]. No new claims — only what the piece actually says.
What prompts cannot fix
No wording gets a tool to supply facts it does not have, outcomes you did not record, or a voice you have never written down. When a prompt keeps returning generic output, the missing ingredient is almost always input rather than phrasing — paste your notes, your figures, or two paragraphs of your own writing and the same prompt produces something usable.
Testing, from our 30-day benchmark
Over thirty days, the prompts that saved the most time were the editing ones — particularly the vagueness check and the rhythm fix — rather than the drafting ones. Generating a draft took minutes either way; finding what needed changing was the slow part. On the cheaper dedicated writer, prompts needed more explicit structure; on the stronger assistant, a short brief with real material was enough.
Bring the material, not just the wording
Paste your notes and figures — that is what turns a prompt into output you can use.
Try Rytr →Frequently Asked Questions
Why do my prompts produce generic output?
Usually a missing field rather than bad wording. A prompt without a named reader, a specific situation or real material to work from causes the tool to supply its own defaults.
Do I need a prompt library?
A small one, for the document types you write repeatedly. The value is consistency, not cleverness — the same brief every time produces comparable output.
Which prompts save the most time?
In our testing, the editing prompts — finding vague claims and fixing generated rhythm — saved more time than drafting prompts, because finding what to change is slower than generating.
Can prompts make output factual?
No. They can instruct a tool not to invent specifics, but every checkable fact still has to come from your material or be verified against a source.
Should I keep prompts secret or reuse them?
Reuse them. The point of a library is that the tenth version of a document type takes as long as the first.