Most prompt-engineering advice this year has been about agents, tool calls, and harness design. This one is refreshingly narrow: a single, short rule about writing style that its author says measurably improved output on two different frontier models. AI educator elvis (Elvis Saravia), founder of DAIR.AI, surfaced it on September 8, 2026, crediting Anthropic for sharing it days earlier — and reported it improved his writing not just with Claude Fable 5.1, but with GPT-5.6 Sol too.
TL;DR
| Question | Answer |
|---|---|
| What does it target? | "Mannered prose" — metaphor and flourish substituting for direct statement |
| Who shared it? | Anthropic, surfaced publicly by elvis (DAIR.AI founder) on September 8, 2026 |
| Which models does it help? | Reported gains on both Claude Fable 5.1 and GPT-5.6 Sol |
| Where do I put it? | As a standing rule in your system prompt or writing/editing instructions |
| Is there a way to test it? | Yes — an interactive comparison tutorial at academy.dair.ai |
| Does it work for all writing? | Best suited to non-fiction, technical, and explanatory writing where clarity beats ornamentation |
The full prompt text
Here is the rule as shared, worth pasting directly into a system prompt, a CLAUDE.md-style instructions file, or a standing custom-instructions field:
Mannered prose substitutes metaphor and flourish for direct statement. Instead of "a parameter worth varying," the mannered writer produces "a dial worth turning." Instead of "this point still matters," they write "this point earns its keep." The phrases exist to display the writer, not to convey the idea, and readers can tell. That is why mannered prose irritates: it makes the reader work harder so the writer can perform. It is also imprecise. Metaphors drag in connotations the writer did not choose and cannot control. The fix is to say what you mean. When a literal phrase is available, use it.
That's the whole thing — no elaborate framework, no multi-step chain-of-thought scaffold. It's a single paragraph naming a specific failure mode and giving a specific fix.
Why this works: naming the failure mode specifically
Most "write better" prompts fail because they're too vague — "be concise," "avoid fluff," "sound natural" — instructions a model can nominally follow while still producing the exact writing style you were trying to avoid. This prompt works differently: it names a precise, recognizable pattern (substituting a dressed-up metaphor for a plain statement), gives two concrete before/after examples, and explains why the pattern is bad (it serves the writer's performance, not the reader's understanding) rather than just asserting that it's bad.
That specificity is exactly the difference explainx.ai's own master prompt-engineering guide emphasizes between prompts that change model behavior and prompts that just add words to the context window: a model can only reliably correct a habit it can concretely recognize in its own draft output. "Mannered prose" gives it that recognizable target.
Why it transfers across models, not just Claude
The genuinely interesting part of elvis's report is that a prompt shared by Anthropic, using Anthropic's own framing, improved output on GPT-5.6 Sol as well — a different lab's model, trained on different data with different fine-tuning. That's evidence the underlying writing habit this prompt corrects isn't a Claude-specific quirk. It's a broadly shared bias across frontier models trained heavily on internet text, where ornate phrasing statistically correlates with "sounds like good writing" in training data, independent of whether it actually communicates the idea more clearly.
This is the same territory explainx.ai covered in Claude Opus 5's load-bearing "Claudisms" — the recognizable verbal tics a specific model tends to produce — except this prompt targets a stylistic bias that appears to generalize across labs rather than being unique to one model's training.
How to actually use it
- Add it as a standing rule, not a one-off paste. elvis describes running it everywhere he uses AI for editing or writing — the value compounds when it's always active rather than something you remember to invoke occasionally.
- Pair it with your existing system prompt or CLAUDE.md. It's a style constraint, not a replacement for task instructions — see explainx.ai's guide to context engineering vs. prompt engineering for where a rule like this belongs relative to task-specific context.
- Test the before/after yourself. elvis published an interactive tutorial specifically so people can compare output with and without the rule rather than taking the improvement claim on faith — a good habit for any viral prompt claim, not just this one.
- Expect the biggest gains on explanatory and technical writing. A rule favoring literal statement over metaphor will do less for creative fiction, where a controlled metaphor is often the point, and more for documentation, editing, and non-fiction — the categories where mannered prose most often gets in a reader's way.
Related on explainx.ai
- Master prompt engineering with Claude: complete guide
- Context engineering vs. prompt engineering
- Claude Opus 5's load-bearing "Claudisms" and writing tells
- Claude Fable 5.1 and Mythos 5.1: benchmarks, pricing, and safeguards
- What is CLAUDE.md?
- Top 10 tips for working with Claude efficiently
Sources
- elvis (Elvis Saravia) on X, September 8, 2026
- DAIR.AI Academy — interactive "Write better with Claude Fable 5.1" tutorial
Prompt text and cross-model results reflect elvis's September 8, 2026 report. Results from any single prompt vary by task and model version — test on your own writing before adopting it as a standing rule.