Matt Pocock — the developer educator behind Total TypeScript, AI Hero, and the widely used /teach Claude Code skill — asked Claude Opus 5 to teach him about Buddhism. What came back was, by his own account, correct and useful. It was also, in his words, "seamslop."
TL;DR
| Question | Answer |
|---|---|
| Who coined it? | Matt Pocock, in an August 15, 2026 tweet |
| What triggered it? | Asking Claude Opus 5's /teach skill to explain Buddhism |
| What does it name? | AI writing that reuses one clever word or metaphor relentlessly as structural connective tissue |
| Is it about being wrong? | No — Pocock is explicit that the output was accurate and useful |
| What's the actual tell? | Not vocabulary or errors — a smoothed-over, "corporate presentation" quality, per a reply from Arch Valmiki |
| Is it fixable with one prompt? | Unclear — Pocock's own "just change the record, please Opus" suggests it isn't a one-shot fix |
The tweet
On August 15, 2026, Pocock posted: "Just asked Opus 5 to /teach me about Buddhism. I think I see what people mean about seamslop." The phrasing — "what people mean" — implies the term already had some circulation before his tweet, though there's no earlier documented source; Pocock's post is the clearest, most-cited point of origin available.
The follow-up is the part that actually defines the term:
"The annoying thing is that it's using the word correctly AND it's useful in this situation AND I genuinely love the word seam. Just change the record, please Opus"
Read closely, this is a precise complaint, not a vague one. Opus 5 had apparently settled on "seam" as a recurring metaphor for something in the Buddhism explanation — plausibly the seams between self and non-self, or between conditioned states, the kind of image that works well once. Pocock's objection isn't that the metaphor was wrong. It's that the model kept returning to it, correctly and usefully every time, in a way that stopped feeling like composition and started feeling like a stuck record.
What the replies clarify
One reply, from Vlady, asks the useful diagnostic question directly: "curious what specifically tipped you off, structure or just tone?" Pocock's response — "Guess what tipped me off to you" — is a joke, but the more substantive answer comes from a different reply, by Arch Valmiki:
"it's not even the words. someone talking like that has sanitized away anything human about the topic and optimized for applause at a corporate presentation. a psychopath. you cannot address this at grammar/word level."
That's the actual definition worth keeping: seamslop isn't a vocabulary problem. You can't grep for it or ban a word list and fix it. It's a structural pattern — a specific rhetorical device (in this case, one metaphor) deployed as connective tissue across an entire explanation, in a way that reads as optimized for a smooth, presentation-ready cadence rather than genuinely varied, human composition. Arthas Proudmore's reply generalizes the same instinct to writing more broadly: "If it sounds like a brochure, i bounce. Same test I use on my own drafts" — seamslop as one specific instance of the broader "sounds like a brochure" tell.
Why this is a harder problem than regular AI slop
AI slop, as a term, mostly names content that's wrong, generic, or substanceless — the fix, in principle, is more accuracy, more specificity, more effort. Seamslop describes almost the opposite situation: Pocock is explicit that the Buddhism explanation was correct and useful. That's what makes it a harder failure mode to name and fix. You can't prompt your way out of it by asking for "more accuracy," because accuracy isn't what's missing. What's missing is variation — the same discipline a human writer applies almost unconsciously, catching themselves reaching for the same clever turn of phrase twice and reaching for something else instead.
It sits in the same family as other named AI writing tics — em-dash overuse, the "it's not just X, it's Y" construction, the reflexive rule-of-three — but seamslop is more specific than any of those: it's not a fixed phrase pattern, it's the behavior of over-anchoring on one apt metaphor and riding it past the point of usefulness, per explanation, per session.
What seamslop looks like on the page
Pocock's tweet doesn't quote the actual Buddhism explanation, so the exact wording isn't public — but the shape of the pattern is easy to illustrate with a constructed example that shows what "correct every time, exhausting by the fourth time" actually reads like:
Buddhism treats the self as a seam rather than a solid thing — a place where separate processes appear to join. Suffering, in this view, is what happens when we mistake the seam for a seamless whole. Meditation is often described as learning to notice the seam directly, rather than being fooled by the surface it creates. Even enlightenment gets described this way: not the erasure of the seam, but full awareness of it.
Every sentence in that paragraph is defensible on its own. "Seam" is doing real conceptual work each time — it's not a filler word, and swapping it for a synonym in isolation wouldn't obviously improve any single sentence. The problem only shows up at the paragraph level, where a reader notices the same image doing the same job four times in a row and starts reading the pattern instead of the content. That's the exact mechanism Arch Valmiki's reply names: sanitized, presentation-smooth, optimized for the individual sentence rather than for how the whole thing reads back.
How this connects to other RLHF-driven writing tics
Seamslop isn't an isolated Claude Opus 5 quirk — it's one instance of a broader category explainx.ai has covered elsewhere: AI models developing consistent, nameable prose habits as a byproduct of how they're trained, not as a deliberate style choice anyone asked for. The clearest parallel is Opus 5's own documented "load-bearing" Claudisms — a separate, specific phrase that shows up constantly across unrelated contexts, traced to the same underlying cause: reinforcement learning from human feedback rewards certain phrasings and structures during training, and those rewarded patterns generalize into habits the model reaches for by default, whether or not they fit the specific thing being written.
What makes seamslop a slightly different animal than a fixed-phrase Claudism like "load-bearing" is that it isn't tied to one word. Ban "seam" specifically and the same underlying behavior — over-anchoring on whichever metaphor got selected early in a response and riding it structurally through the rest — will very likely resurface around a different word the next time the topic changes. That's why Arch Valmiki's reply insists "you cannot address this at grammar/word level": a word-list ban treats the symptom, not the generative habit producing it.
Is it fixable?
Pocock's own thread doesn't resolve this — "just change the record, please Opus" is a plea mid-conversation, not a report that a follow-up instruction worked. That's consistent with how these things usually go: a single "stop doing that" rarely holds for the rest of a long response, because the model isn't tracking "I already used this metaphor" as an explicit constraint unless something in the prompt or system instructions makes it one. The more durable fixes are structural — a style guide or /teach-skill-level instruction discouraging metaphor reuse within a single response, or a human edit pass that catches it the way Pocock himself did.
A few concrete tactics generalize better than a mid-conversation complaint:
- Name the specific behavior, not the topic. "Don't lean on a single metaphor as a structural device across the whole response" targets the mechanism directly, the same way the Claudisms guide found that naming an exact phrase to avoid works better than a generic "write better" instruction.
- Ask for a self-review pass. Prompting the model to reread its own draft and flag any word or image used more than twice as a structural connector catches the pattern after the fact, when it's easier for the model to spot in finished text than to avoid while generating it sentence by sentence.
- Cap explanation length per concept. Seamslop tends to show up more in longer, single-shot explanations where a model has more room to settle into a groove. Breaking a long
/teach-style explanation into shorter, separately-prompted sections gives less runway for one metaphor to become load-bearing. - Treat it as a signal to simplify, not just to vary. If a model is reaching for one image four times to explain something, that's sometimes evidence the underlying concept could be stated more directly in the first place — variation isn't the only fix; sometimes the honest fix is cutting the metaphor's third and fourth appearances entirely rather than replacing them with synonyms.
None of these are confirmed fixes from Pocock's own thread — they're the same category of mitigation that's worked for other named AI writing tics, applied to this one, and worth testing rather than assuming will hold.
Related reading
- Top 10 signs of AI-generated text — seamslop as one of ten reader-spottable tells
- What Is AI Slop? A Practical Definition
- What Is Mermaid Slop? The Generic AI Diagram Problem, Explained
- Matt Pocock: Why Real Engineers Are Using Agent Skills
- Matt Pocock's TypeScript Skills v1: Progressive Disclosure
- Seamslop dictionary entry
Term origin and quotes reflect the public thread on X as posted August 15, 2026. explainx.ai has not independently verified whether "seamslop" had prior circulation beyond this tweet.