Claude prompt for creative writing: Revision Letter (Common Fixes)
Claude · Creative Writing · Common Fixes
You are a hands-on practitioner using Claude for creative writing, specifically revision letter.
Job: give actionable notes.
Audience: workshoppers. Constraint: examples from the text.
Working style: diagnostic. Optimize for typical failures and how to repair the prompt.
Process:
1. Restate the brief in one sentence and list missing facts as questions.
2. Draft the artifact.
3. Stress-test it against the constraint.
4. Return a final version plus 3 numbered improvements.
Output contract: use headings, short paragraphs, and concrete examples. No filler. No invented statistics.
If information is missing, make the smallest reasonable assumption and label it.Claude users in creative writing use this revision letter prompt to ship faster drafts that respect "examples from the text". In practice, one customization pass is enough when the brief is this specific. The common fixes version uses diagnostic language and targets typical failures and how to repair the prompt.
When to use this prompt
Claude shines at creative writing work when you state the observable outcome: give actionable notes. The Common Fixes framing keeps typical failures and how to repair the prompt visible while you edit. Swap only nouns when adapting — keep the process intact.
Why this prompt works
- Names a clear job so Claude does not wander into generic advice.
- Forces an output contract: headings, examples, and a final version.
- Separates draft from critique so you can steal the structure later.
- Repeats the hard constraint: examples from the text.
- Uses diagnostic language that matches how practitioners actually brief work.
How to use it in Claude
Redact client names; keep structure. Slug revision-letter-fixes is your canonical URL for this brief. Paste the prompt into Claude and replace bracketed details with your facts. This Common Fixes path is for workshoppers who care about give actionable notes. Save the winning variant for revision letter — teams with a short library ship faster. Use diagnostic follow-ups only — mixing tones mid-thread confuses Anthropic models.
Run a constrained version and a wild version of revision letter. Keep structure from one and energy from the other. For revision letter in creative writing, the failure mode is usually style without substance. This prompt blocks that by design — especially "examples from the text". Expect two minutes customizing and two minutes editing for Common Fixes output. Anthropic models still need your facts for revision letter; they cannot invent metrics or brand rules. authors and storytellers teams bookmark slug revision-letter-fixes when typical failures and how to repair the prompt matters.
Step-by-step
- Open Claude and paste the prompt block unchanged.
- Replace placeholders with your project facts (workshoppers, offer, timeline).
- Confirm the constraint is still visible: examples from the text.
- If output is vague, ask Claude to restate assumptions as questions first.
- Reply with one fix list, then regenerate the final version only.
Example output
Example output shape: H1 with Revision Letter, 3 short sections, bullet list of recommendations, closing line that states examples from the text. Facts you supply appear; nothing invented.
Common mistakes
- Deleting "examples from the text" to save space — that is usually the whole point.
- Asking for revision letter plus three other jobs in one message.
- Ignoring the output contract headings.
Expert notes
Anthropic users working on revision letter in creative writing should treat "examples from the text" as non-negotiable. Scenes, voice, character, and narrative craft. When workshoppers run the Common Fixes variant, they usually care about typical failures and how to repair the prompt more than length.
If text output feels generic, re-paste examples from the text as the first follow-up message — do not rewrite the whole prompt.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a revision letter piece. |
| This prompt | You need a usable draft | Role, constraint, steps, and output contract included. |
| Plus examples | Voice must match yours | Paste 120 words of your writing or a still you like, then rerun in Claude. |
Key takeaways
- Compare against other Claude angles on the same use case before you standardize.
- Claude improves when you paste a real snippet or reference still.
- Keep examples from the text visible in the prompt, not only in your head.
- The Common Fixes variant is for typical failures and how to repair the prompt.
- Ship a draft, then tighten. Do not chase a perfect first token.
FAQ
- What is a Claude prompt for revision letter?
- It is a structured brief that tells Claude how to produce creative writing output for workshoppers. This common fixes version stresses typical failures and how to repair the prompt and keeps "examples from the text" in the instructions.
- How do I customize this Claude creative writing prompt?
- Swap project nouns, paste one real example, and leave the process steps intact. The constraint "examples from the text" should stay unless your brief truly changed.
- Why use the common fixes angle for revision letter?
- Different angles solve different failures. Common Fixes helps when workshoppers need typical failures and how to repair the prompt. It is not longer for its own sake — each line has a job.
- Is this Claude prompt updated for 2026?
- Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Anthropic models. Always verify facts before client delivery.