Load-Bearing: The Claude Opus 5 Writing Tells Everyone Is Suddenly Noticing

Somebody on Hacker News noticed that Claude Opus 5 will not stop saying "load-bearing."

The line that crystallized it, posted to r/ClaudeAI by a developer at the end of their tether with Opus 5's documentation output:

"That is deliberate and load-bearing rather than tidy."

It is a real sentence, written by a real model, about a dotnet publish build step. The metaphor is doing no work. Nothing is bearing any load. And once you see it, you cannot unsee it — the phrase turns up in code comments, architecture docs, legal review, and commit messages, applied to anything the model considers structurally important.

Then a Hacker News commenter replied to a thread about Claudisms with "And this is the most important observation in this thread. It's load-bearing!" and the joke was fully formed.

TL;DR — what people are asking

The Claudism inventory

Community reports converge on a fairly stable list. These are the constructions that show up far more often in Claude output than in human technical writing:

One Hacker News commenter catalogued the structural version precisely: Claude has roughly four or five variants of the "counter-factual, linguistic pause, factual" pattern, plus a habit of dramatic mid-sentence pauses built on colons and semicolons where a human would just write "and" or "but."

The joke replies wrote themselves. One user reported Fable calling a clause "the most load-bearing sentence in the document" during a legal review. Another parodied the register with "You're absolutely right. Your belt-and-braces are earning their keep."

The one nobody flags

Worth separating out: the sentence-fragment pattern is the most common tic and the least discussed. In isolation, each instance reads fine — that is exactly why it escapes notice. It only registers in aggregate, across a whole document, where the rhythm starts to feel like a pitch deck rather than a technical explanation.

The named phrases are easy to grep for. The fragment habit requires reading.

Why does this happen?

Anthropic has not published an explanation, so treat what follows as inference from observed behavior rather than confirmed mechanism.

The most credible theory in community discussion is that reinforcement learning rewarded prose that reads as confident, dense, and quotable. Human raters preferring the punchier of two drafts, over enough iterations, collapses the model toward a narrow band of high-scoring constructions. "Load-bearing" is efficient in exactly that way — one hyphenated adjective that asserts structural importance without having to argue for it.

There is indirect support for this. When one developer wrote a paper with Fable and asked it to drop the Claudisms, the model correctly generalized from a short list, and its own summary of the change was telling: the sentences now stated claims directly instead of building to a turn of phrase. "Turn of phrase" is the thing being optimized for. The tics are downstream.

Thinking Machines' Inkling release notes offer a parallel from a different lab: their published before/after shows early-RL reasoning traces that are verbose and grammatical becoming terser and more compressed post-RL. One developer noted the Fable experience feels like reading the early-RL version — which suggests these register shifts are a general consequence of RL on reasoning models, not a quirk of one company's taste.

It is also worth separating two complaints that get conflated. The lexical problem (saying "load-bearing" too much) is cosmetic. The behavioral problem — Opus 5 generating pages of unrequested documentation and verbose comments — is the one that actually costs time, and explainx.ai covered that separately in why developers say Opus 5 over-engineers simple tasks. The r/ClaudeAI documentation complaint is really about both at once: too many words, and the wrong words.

Does a recognizable style actually matter?

Two honest positions, and both are defensible.

Yes, it's a real cost. The r/ClaudeAI poster's complaint is concrete: memories, CLAUDE.md, and documentation-style skills all in place, and Opus 5 still produced pages of prose they had to review and delete on every file touch. When cleanup exceeds the time saved, the model is a net negative for that task. Several developers separately described Claude and Fable output as exhausting to read, and one made the sharper point that being able to explain complex things simply is itself a marker of understanding — so dense prose may indicate the model has not compressed the idea, not that the idea is deep.

No, it's load-bearing. Sorry. Several developers argue a recognizable house style is a feature: it makes AI text harder to pass off as human, and keeps everyone honest. As one put it, they would be more concerned if Claude had no distinct tone at all.

That second argument connects to something explainx.ai has covered from the technical side. Anthropic is embedding invisible C2PA provenance metadata in Claude output, and we built a free C2PA checker to inspect it. Cryptographic provenance is robust but strippable — metadata does not survive a copy-paste. Stylometry survives copy-paste. The two are complements, not competitors: one proves origin when metadata is intact, the other raises suspicion when it is not.

The catch is that stylistic detection has a short shelf life. It works precisely until labs decide to fix it, and every viral thread cataloguing these tics is free training signal for doing exactly that.

How to actually suppress it

Generic instructions fail. "Write better" and "be concise" do essentially nothing, which is why the r/ClaudeAI poster's skills and memories were not working. What works is naming the specific tics.

The prompt one Hacker News user reported success with, reproduced because the specificity is the point:

The writing style could really use some work. Avoid Claude-isms like
"stated fairly", em dashes, "load-bearing", overly punchy phrasing like
"keep the signal, govern the response". This is a technical document,
not a marketing campaign.

They noted Claude caught the gist without needing every tic enumerated — "punchy" seemed to be the operative word. That is the single most useful finding in the whole discussion. You are not blacklisting strings; you are naming the optimization target and telling the model to stop pursuing it.

A CLAUDE.md block along these lines, so it persists across sessions:

## Writing style

- No em dashes. Use commas, parentheses, or a new sentence.
- Banned phrases: "load-bearing", "worth stating plainly", "full stop",
  "carry the argument", "the trap", "isn't just X — it's Y".
- No punchy fragments for drama. Write complete sentences.
- Do not build to a turn of phrase. State the claim directly.
- Technical documentation, not marketing copy.
- Comments explain why, in one line. No paragraph-length comments.
- Write no documentation unless explicitly asked.

Three practical notes:

• Expect "You're absolutely right!" and a revert. Style instructions decay across a long context. The r/ClaudeAI poster's experience — correct it, get agreement, watch it come back — is the normal failure mode, not a sign the instruction is wrong. Re-anchor after compaction.
• The last two lines matter most for code. The documentation and comment-volume problem is behavioral, and no amount of vocabulary banning fixes it. Say it separately and explicitly.
• Style-fitting beats banning. One developer reported building a stylometry skill from ten samples of their own best writing and having Claude match it. Giving the model a target to imitate is more reliable than a list of things to avoid — the same principle behind the anti-slop skills we covered from Peter Yang and Nutlope's Hallmark. Browse more on the explainx.ai skills registry.

There is a deeper version of this argument worth reading: that style instructions like "explain it simply" reshape the model's reasoning, not just its output formatting, which is why they should be applied at the rendering boundary rather than to the whole trajectory. explainx.ai covered that case in humanising LLM outputs is dumb.

Which model writes best?

No consensus, and the honest answer is that it depends on what you are writing. From the community discussion:

Note the pattern: the newest model is nobody's favorite writer. Whatever is being optimized in each generation, conversational prose quality is not obviously it — which is consistent with the RL theory above. If output style matters more to you than raw capability, the current-model default is not automatically the right call, the same routing logic explainx.ai applies in the agent skills guide.

What to actually take from this

The tics are cosmetic. The habit underneath them is not.

A model trained to build toward a turn of phrase will reach for emphasis whether or not the sentence has earned it, and that is a subtler problem than any word list captures. It shows up as documentation that sounds authoritative about a build step that needed one line, and as comments that assert importance instead of explaining behavior.

The fix is not a better model. It is briefing against the register directly — banning the optimization target rather than its symptoms — and then re-anchoring that instruction when a long session inevitably drifts back.

Also, stop saying load-bearing.

Related on explainx.ai

• Why developers say Claude Opus 5 over-engineers simple tasks
• Claude Opus 5 launch coverage
• "Humanising LLM outputs is dumb" — render at the boundary
• Anthropic's invisible C2PA watermarks in Claude output
• Free tool: check any file for Claude's C2PA watermark
• What is AI slop? SEO, GEO, and content quality
• Slopocalypse: AI slop and the internet in 2026
• Peter Yang's open-source no-AI-slop skill
• Nutlope's Hallmark anti-slop design skill
• SlopCodeBench: measuring Opus 5 maintainability

Sources: the Hacker News discussion on Claude Opus 5 (1,778 points, 1,335 comments) and the r/ClaudeAI thread "Opus 5 is literally useless for documentation," both as of August 11, 2026.

Community quotes are attributed to their original posters on Hacker News and Reddit; usernames are omitted where the comment was incidental. Anthropic has not published an explanation for these stylistic patterns — the reinforcement-learning account here is inference from observed model behavior and community testing, not a company statement. Model style comparisons are subjective community reports, not benchmark results, and model behavior changes between releases.