Dead Giveaway

newest comment read · rebuilt daily

41 signs your work was made with Claude

4,326 people on Reddit described them between 1 January and 5 October 2026. Where somebody posted a screenshot or the text itself, it is shown with the spots they pointed at. The list updates live, and the rules to avoid them come with it.

This is the plain version of the page. Its layout and text drop the habits that a rule can catch. See the original, made with Claude.

451Reddit boards covered

35,625,041comments and posts searched

41,331describe a habit of an AI model

7,809describe one of these 41 Claude habits

4,326people wrote them

Counts of comments searched and judged cover whole weeks.

When Claude builds a web page15 habits

The AI purple331 Serif headline, one italic word281 Cards, with an accent stripe150 Stock component kit120 The same hero, every time112 Pill above the headline93 AI-style copy on the page (em dash, metaphors, explanatory text)64 Cream and terracotta page60 Hairline borders, edge stripe57 Emoji as icons49 One spacing rhythm everywhere46 Dark by default, grey on grey43 An eyebrow over every heading41 Everything fades in and floats27 Dot-pill chips everywhere16

When Claude writes14 habits

The em dash hinge1,787 Claudish engineering words385 Document furniture in prose345 Metronome paragraphs298 Candour labels and signposts242 The "not X, but Y" reframe155 Buzzword-heavy corporate register128 Padded and long101 The tidy bow at the end95 Polished but says nothing90 Colon-led payoffs90 Rule of three55 Soft-framed hedging46 Prose too clean, with mess faked on top14

When Claude makes slides3 habits

The same-every-time Claude deck66 Over-written slide headings11 Claude's default deck palette10

No other habit was named by 10 or more people.

When Claude writes code9 habits

Diary comments in code309 Essay-length commits and PRs88 Rewrites what already exists80 Claude signs the commit80 Non-ASCII punctuation in code55 Names taken from the chat instead of the code41 Errors swallowed by fallbacks37 Insecure shortcuts in working code34 Copy-paste Tailwind and hard-coded styles12

When Claude builds a web page

15 habits named by 869 people between 1 January and 5 October 2026.

12345

1Violet stat number
2Violet progress bar
3Violet percentage
4Glowing violet action button
5Violet active tab

331 people

The AI purple

Violet or indigo carries the page, with a blue-to-purple gradient on the hero or main button and a faint glow around cards on a near-black background.

“The second one is because this purple blue gradient is right now considered the em dash of UI.” Reddit

Evidence

When Claude is left to pick colours, commenters say it reaches for purple or indigo as the brand colour. Most reports come from Claude Code and vibe-coded apps. Blue-to-purple gradients cover the hero, from the background to the heading text and the CTA button. The background is often dark, with soft neon glows. It rarely comes alone. People name it in the same breath as Inter, a centred hero, three rounded feature cards and emoji icons, and they treat the colour as the fastest single tell of the package. Many commenters call it the generic AI-website look and do not see it as Claude's alone. Some trace it to Tailwind's indigo defaults. It counts as a Claude tell mainly because Claude is the tool most people build with, and because Anthropic's own frontend-design skill bans "purple gradients on white". Through 2026 the reports describe it more and more in the past tense. Newer Claude output and Claude Design are said to have moved to cream, peach/orange, teal or emerald. So "purple" is now partly a label for whichever saturated default accent and glow the model leans on.

Signs people name, with the number of people naming each

Blue-to-purple gradient Fills the hero background and the primary CTA button, and turns up as gradient heading text. Called "the em dash of UI".		140
Purple/indigo as the main accent "Purple everywhere", in buttons, pills, progress bars and active nav states, even on otherwise neutral pages.		90
Soft neon glow Glowing buttons and blurred radial glows behind cards, sometimes with gradient borders. One commenter writes "Purple tint and slight glowy hue on everything. Claude loves that".		60
Dark mode with neon colours Near-black or navy background with bright violet, blue, cyan or lime accents.		40
Comes bundled with Inter and three cards The colour is named as part of a set with Inter, a centred hero, three rounded feature cards and emoji or Lucide icons.		90
Pastel or rainbow gradients on chips and headers Multicolour pastel tags and a gradient header. One commenter describes "pastel gradients with a 1px border around everything".		10
Glassmorphism and blur Frosted cards and blurred backgrounds that come with the gradient.		20

Posted cases

1Violet stat number
2Violet progress bar
3Violet percentage
4Glowing violet action button
5Violet active tab
A competent dark study-tracker screen where one violet does all the accent work. It colours the numbers, the progress bars, the active tab and the floating button. Replies name "the prominence of purple".
clearly Claude. Thread

1Blue-to-violet gradient headline
2Purple corner glow
3Pill badge above heading
4Rainbow pastel chips
A clean, usable job board. Its headline is a blue-to-violet gradient over a purple corner glow. A pill badge sits above it, and the filter chips are rainbow pastel. A commenter says Opus defaults to exactly this.
probably Claude. Thread

1Blue-to-violet gradient bar
2Glowing gradient icon
3Faint navy glow background
A polished onboarding screen with a blue-to-violet gradient progress bar and a glowing gradient icon on near-black. It matches the "brightly colored vivid components on a dark background with some glow or gradient" the poster describes.
probably Claude. Thread

1Glow around central card
2Cyan wide-spaced caps
3Emoji as icons
4Green status dots
A neat agent dashboard built with Claude in the dark-neon variant. It has cyan spaced caps and a glowing card. Emoji serve as icons. The reply says it looks "like something opus 4.1 would produce with the purples and blues". The hue here is cyan, though.
clearly Claude. Thread

Easy to mix up with

Claude's newer warm look (cream background and terracotta/orange accent with a serif headline that has one italic word). The warm look is the 2026 Claude-specific default. People now describe purple in the past tense, as the older AI default shared across models.
Generic shadcn/Tailwind dark dashboard. These use neutral zinc or slate cards with no colour statement. The purple tell needs the saturated violet accent or the blue-to-purple gradient.
Emerald/teal "skills" look. It uses the same dark-with-glow recipe with an emerald or teal accent. People attribute it to frontend skills and Claude Design. They do not blame the base model for it.

Objections

Many call it the generic AI/Tailwind look that Claude did not invent. They blame Tailwind's indigo defaults and 2019-2023 startup branding.
One commenter traces it to post-training and style skills. In that view the training-data average is not the cause.
Some defend gradients in general and say the type and style of gradient gives it away. Some people like the purple-blue palette.
Some users chose purple themselves as their brand colour, so purple alone is a weak signal.
A side-by-side test in July 2026 ran Claude 12 times with and without the frontend-design plugin. None of the pages had a purple gradient.

Changes over time

People say the purple era is ending or over. One writes "Used be blue purple gradients". Another says "Before it was blue/indigo gradients, now it's warm peachy background + bright orange".
In February a commenter already assumed newer models had the purple trained out.
Claude Design is credited with avoiding purple gradients. It is said to have its own teal/cream defaults.
Green is named more and more alongside purple or in its place. Commenters write "neon colors especially purple and a cyber green" and "neon and lime green text". A March 2026 post calls emerald "the new purple" after design skills spread.
Orange tint and glow are now named for Claude sites (September 2026).
A July 2026 re-run of 12 Claude pages found no purple gradient at all.

Serif headline, one italic word 281

On a cream page, a big serif display headline sets one word in italics under a tiny spaced-out caps label, while monospace leaks into the buttons.

“Claude loves Serif fonts. It is the em-dash of AI web design.” Reddit

Evidence

When Claude builds a page without a type brief, regular users recognise its typography on sight. What they spot is a recurring type recipe more than any one font. The current recipe starts with a large serif display headline (Playfair, Fraunces, Lora or something Georgia-like). One or two words switch to italic and often take the accent colour. The headline sits on a cream or beige background with terracotta/orange accents. Above the headline sits a tiny all-caps label with wide letter spacing, frequently set in a monospace font and sometimes led by a long dash or a status dot. Monospace keeps leaking into buttons, stats, captions and even body copy. The side effect commenters name is three or four families and many sizes and weights on one screen. Secondary text comes out thin and small, which makes it hard to read. An older, more generic layer still gets mentioned. It pairs Inter or Geist with a geometric sans like Space Grotesk or Manrope and a purple gradient. Several people call that layer the generic AI starter pack. The serif headline with an italic word and mono labels is what reads as specifically Claude.

Signs people name, with the number of people naming each

Serif display headline with italic (often coloured) accent words Big serif headings set in Playfair Display, Lora, a Georgia-like face or Fraunces at its lightest weight. Regular and italic mix in one headline. One word is italicised and tinted in the accent colour. Some headlines switch between serif and sans midway. Commenters name it the strongest current Claude-specific tell.		22
Cream/beige background and terracotta/orange accent around the type The fonts are almost never named alone. Commenters pair them with a cream or off-white background and a rusty orange or #c15f3c accent. Beige-and-green or tan/khaki palettes come up too. Font plus colour is the most common short diagnosis.		14
Monospace used outside code Monospace (JetBrains Mono, a "consolas looking font", a "console style" or "very techy" font) for eyebrows, section labels, numbering, buttons, stats and sometimes body copy. It sits next to warm serif or sans text. One commenter calls it the real telltale, more than Inter.		12
Tiny all-caps, widely tracked eyebrow label above the heading A small uppercase subtitle with extra letter spacing above h1/h2, often in monospace. A long em-dash or a coloured status dot can lead it, or it sits inside a pill.		12
Too many families and sizes on one screen Three or four font families in a hero, with a spread of sizes and weights in several colours. A commenter calls them "fonts used non-systematically". The fix people report is cutting down to one or two families and fewer sizes.		9
Inter / Geist plus a geometric sans (Space Grotesk, Manrope, DM Sans and the like) The older default layer pairs Inter or Geist with a geometric sans for headings, often with purple gradients. Many treat it as the generic all-AI starter pack and see no Claude-only tell in it. Most of the disagreement sits here.		14
Small, low-contrast secondary text Very small fonts in a secondary colour and thin small serifs. One commenter names "hacker-style-dark-mode-9px-font". Dark-on-dark text works as decoration and cannot be read.		5

Posted cases

1dash + tracked caps eyebrow
2geometric sans display
3italic serif accent line
4serif stamp lettering
5tracked caps label
A handsome, finished game landing page whose hero follows the recipe exactly. A geometric sans word sits over an italic serif line in terracotta, under a tiny tracked eyebrow led by a dash.
probably Claude. Thread

1condensed serif headline
2italic coloured words
3monospace buttons
4dot + mono eyebrow
5cream grid background
Clean, credible developer-tool hero with a condensed serif headline, two italic blue words, sans body, monospace buttons and a mono status label on a cream grid.
probably Claude. Thread

1pill eyebrow with dot
2accent-coloured headline words
3monospace body copy
4mono nav links
5mono stat captions
A polished dark landing page for a Claude Code design skill. It still shows the pill eyebrow with a dot and the monospace body copy that commenters list as tells.
probably Claude. Thread

1tracked caps title
2italic serif caption
3monospace readouts
4serif numbered list
An impressive Opus 5 3D demo. Its side panels mix tracked caps titles, italic serif captions, mono readouts and serif lists, the "mixture of unfitting fonts" a commenter counted.
clearly Claude. Thread

Easy to mix up with

The generic AI look (Inter, purple gradient). Commenters treat Inter plus purple as every AI tool's default. The serif headline with an italic word on cream is what they pin on Claude.
Cream and terracotta page. The cream page habit covers the colour. The two appear together in most reports.
Eyebrow labels. The tracked caps label is one part of this recipe. The eyebrow habit covers such labels on every section of a page.

Objections

The fonts are neither bad nor rare. Inter, Space Grotesk, Manrope, JetBrains Mono and Lora are popular, well-made Google fonts that predate AI. Using one tells you nothing on its own.
The tell lies in the combination and treatment (sizing, placement, the italic word, the mono eyebrow, the cream palette). A single typeface proves nothing.
Commenters call the output nice and clean, better than most. The cost is that people who use Claude themselves recognise it.
This is a default that goes away when the user supplies a type pairing or reference material such as a style guide or example sites. Several call it a sign the user gave no design input.
Purple + Inter is widely seen as a generic AI look shared across tools.
The pick varies. One user reports Claude chose Roboto.

Changes over time

The look shifted from the 2024 purple-gradient/Inter style to a typographic one. Serif with italic accents now sits on cream, next to mono labels.
Playfair Display was the favourite for a while. Lately Fraunces in its lightest weight shows up a lot, in headlines that mix regular and italic.
People say the tells have grown since Opus 4.8 and Fable 5. A pixel font is said to carry over from Opus 5. Opus 5.5 output still reads as Claude in font and styling.
When Fable redid a site to look less AI, it landed on the same layout and type as another user's site, down to the colour scheme.

Cards, with an accent stripe 150

Content gets chopped into many same-weight rounded boxes, and a thin colored bar often runs along each card's left or top edge.

“That left side card highlight is in every Claude build.” Reddit

Evidence

When Claude builds a page or app screen without a design direction, it puts nearly every piece of content into its own rounded, bordered card of equal visual weight. Three feature cards go under the hero and a dashboard becomes a grid of metric tiles. List items turn into cards, and sometimes cards sit nested inside cards. The part commenters call specifically Claude is the colored accent bar on one edge of each card (left side or top), often in a different color per card. Several tie it to the official frontend-design skill. Each card gets an emoji or Lucide icon and a tiny all-caps spaced label. Pills or a colored status dot are common, as is a hover lift or border glow. Most of the 150 people describe the generic "three cards in a row" SaaS skeleton that every tool produces. The Claude-only fingerprint is narrower, the edge stripe plus the uniform card weight.

Signs people name, with the number of people naming each

A row of three equal feature cards under a centered hero Each card stacks an icon or emoji over a bold heading and a sentence or two. It is the most-named part of the "Claude default SaaS starter kit".		55
Cards everywhere / container soup Every section is boxed. So is every list item and every stat. Pages read as page after page of identical cards, especially on mobile.		40
Colored accent bar on the card's left or top edge A 3-4px stripe in an accent color, often a different color per card. People name it as the uniquely Claude cue and link it to the frontend-design skill.		25
Rounded soft-shadowed or glassy cards that lift on hover A large radius with a soft shadow or translucent glass. On hover or scroll the card lifts or its border lights up. Some cards play a reveal animation.		20
Cards nested inside cards A card holds a panel that holds more bordered tiles. Builders list it in their banned-defaults files.		12
Equal weight with no hierarchy, and KPI tiles where a table would do Every card gets the same drama. Dashboards become a grid of metric cards even when the data wants a table.		10
Card furniture such as tiny caps labels, dots, pills and icons An all-caps spaced subtitle above the card title, colored dots, pills and a Lucide or emoji icon in every card.		10

Posted cases

1Colored top accent bar
2New color every card
3Spaced mono caps label
4Mono tag pill
5Emoji as icon
A doctor's notes site that Claude generated as a .html file. It is tidy and readable, yet every specialty is a rounded card topped by a different-colored accent bar. Emoji and pills fill each card under a spaced mono caps label.
clearly Claude. Thread

1Twin equal KPI cards
2Icon plus caps label
3Streak in its own card
4Day tiles inside card
A polished, usable study-tracker home screen where every element (today, this week, streak, calendar) sits in its own large-radius dark card, with cards inside cards.
clearly Claude. Thread

1Four boxed stat tiles
2Profile wrapped in card
3Pill tabs in container
4After: flat stat row
The left half shows the Claude-built Drinqly profile before the fix. It is a nicely themed dark-gold screen, but the profile is a big rounded panel holding four boxed stat tiles and a pill tab bar. The owner later prompted Claude to remove all the cards.
probably Claude. Thread

1Wall of equal cards
2Heading plus two lines
3Card inside card
4Pill eyebrow label
The demo page of a Claude Code design skill, with crisp dark styling. The features section is a 2x3 wall of equal rounded cards, each with an illustration box over a heading and two sentences. That is exactly what the skill's own file calls the biggest AI tell.
probably Claude. Thread

1Three boxed value points
2Pill eyebrow above title
3Feed as rounded cards
A warm, well-set landing hero where the three value points (Plan goals, Post proof, Build together) are boxed as a row of three icon chips. The phone mock is a stack of rounded feed cards.
probably Claude. Thread

Easy to mix up with

The generic AI SaaS look (purple gradient, Inter, centered hero, three cards). Every builder tool shares it. The Claude-specific part is the colored edge stripe on cards and the uniform boxed layout in otherwise warm or dark-neutral palettes.
Claude's editorial type look (serif headline with an italic word under a tiny spaced caps label on a cream and terracotta page). The editorial look covers typography and color, and it often appears on the same page as the cards.
Stock shadcn/ui components. Plain shadcn cards are gray and have no stripe. Commenters treat the per-card accent bar and the emoji or icon-topped tiles as Claude's addition.

Objections

Claude is one of many sources of the three-card SaaS skeleton. People report the same from Lovable, v0, Bolt, Codex, Gemini and Kimi, and blame shadcn and stock Tailwind defaults.
Some call it a no-input problem. Give Claude a reference or a design system and it goes away.
Some defend it. They like bento grids and the colored card highlights, and say the public only sees "a template".
Cards on dashboards may simply be the convention models were trained on. AI did not invent them.

Changes over time

One developer dates the left-side card highlight to Anthropic's release of the frontend-design skill.
Opus 4.6 (Feb 2026) was praised for much better UI than 4.5. Its colored-edge cards and four-card top row still "scream Claude AI".
Reports continue through Opus 5 (July) and Opus 5.5 (Oct 2026), with "the same gray cards and purple buttons every time". One user felt output crept back to card-heavy slop over three months.
A Claude Design user in May 2026 said its output has "less of that default AI SaaS-card" look than before (thread 1t0mmfz).

Stock component kit 120

The page looks like an unmodified shadcn/ui starter on Tailwind with thin-bordered slate or gray cards in the default radius and accent, and a stock Lucide icon or emoji sits beside every label.

“It’s the visual version of an em dash.” Reddit

Evidence

Commenters recognise Claude-built interfaces by the untouched component kit underneath. It is shadcn/ui on a stock Tailwind config. The cards are the same slate-gray bordered boxes with the default radius and padding rhythm, and the accent is the kit's default blue or purple, sometimes indigo. The icons are Lucide in every slot. Sparkles, Zap, Brain and a clock or calendar beside each label are the usual picks. In quick builds, emoji replace the icons entirely. The kit brings a matching skeleton. A pill badge sits over the headline, a solid button beside a ghost button, three equal feature cards below, and an icon in a tinted rounded box. Several people point out that the look persists without the library. Claude writes Tailwind-style classes even when no framework is installed, and drifts back to them after being handed a different design system. Most commenters treat the kit look as shared by all AI builders, naming v0, Lovable, Cursor and the rest. What reads as Claude-specific in 2026 is the cream background and serif type layered on top. That is a separate habit.

Signs people name, with the number of people naming each

Untouched shadcn/Tailwind defaults Same slate-gray cards and padding rhythm on the default radius and primary token. People call it "shadcn soup" or "tailwind clone #2137". One calls it "exceptionally average passes at Tailwind CSS".		45
Emoji used as icons Large or mixed-style emoji stand in for an icon set in feature cards and buttons, even in the nav. One commenter calls this the "first tell tale sign".		25
Purple or indigo accent, or the default blue The kit's default accent, often as a purple-to-blue gradient or glow. One commenter asks "what's with the love of the color purple?".		25
Lucide icons in every slot The same Lucide set everywhere. Sparkles and Zap come up most, Brain too. An icon sits beside every label and row, down to the dates.		16
Bordered rounded cards around everything Sections and metrics sit in rounded boxes with thin or tinted borders. Icons get a half-transparent box in their own colour.		14
Kit skeleton on landing pages Pill badge over a headline, a solid plus a ghost button, a stats row, three or six equal feature cards, and all-caps eyebrow labels with a leading dot.		10
Drifts back to the kit despite a supplied system Given a full design system or just fonts and tokens, Claude still adds the same accent bars and icons. It also invents a new button variant or hard-codes bg-gray-100 in place of tokens.		8

Posted cases

1Lucide clock beside label
2Lucide calendar beside label
3Bordered rounded stat cards
4Default purple accent
5Purple floating action button
6Stock Lucide tab icons
A tidy, working study tracker made with Claude. Every stat sits in a bordered rounded card with a Lucide clock or calendar icon, on the default purple accent.
clearly Claude. Thread

1Lucide chart icon button
2Tracked all-caps label
3Lucide trending-up arrow
4Glowing green line
5Bordered stat tile row
6Stock Lucide tab icons
Fable 5's fitness screen is judged the better of two in a same-prompt test. It is still built from stock pieces. There are Lucide icons for trends and charts, bordered stat tiles, tracked caps labels and a glowing line.
clearly Claude. Thread

1Sparkle emoji after headline
2Emoji inside filter pills
3Emoji as timeline icons
4'AI-powered' label with sparkle
5Row of emoji tiles
A polished, working iOS routine app built with Claude Code and Opus 4.5. Emoji stand in for every icon, and the thread singled that out as the giveaway.
clearly Claude. Thread

1Pill badge with dot
2Solid plus ghost button
3Four bordered stat cards
4Image in rounded frame
5Pill theme toggle
A clean personal site whose owner let Claude build it with defaults. The kit pieces survived a recolour and new fonts, and readers named Claude at once.
clearly Claude. Thread

1Pill badge with dot
2Solid plus ghost button
3Stock check-circle icon
4Big-number stats row
The demo page of a skill meant to stop generic Claude Code UI. Recoloured green, it still ships the kit skeleton. It has a dot-led pill badge, a stats row, a stock check icon and a solid button beside a ghost button.
probably Claude. Thread

Easy to mix up with

Claude's cream-and-serif look. In mid-2026 people call the cream or beige background with italic serif type and terracotta the specifically Claude layer. The stock kit sits underneath it and is shared by all AI builders.
Generic "AI purple gradient" look. The gradient is one symptom. The stock kit covers the whole untouched component system of cards, radius, tokens and icon set, and it stays when the colour is changed.
Over-decoration with unrequested badges and counts. Over-decoration is about adding elements nobody asked for, icons included. The stock-kit complaint concerns which stock pieces are used, whatever their number.

Objections

Most commenters say Claude converges on the same kit as v0, Lovable, Cursor and open models.
The library itself does no harm. Shipping it unmodified is the tell, and some even recommend Lucide or shadcn as the fix for emoji icons.
Many blame the vague prompt more than the model. With real references or tokens the output changes.
The result works and looks clean. People object to the sameness.
Claude copies Tailwind-style classes even when no framework is used, so the look travels without the dependency.

Changes over time

From January to April 2026 complaints centre on purple gradients and on shadcn with Lucide. Opus 4.6 was praised as a big UI step up from 4.5, while its output was still read as shadcn.
From June the Claude-specific signature shifts to cream backgrounds with serif type, plus emoji icons. The shadcn/Lucide kit is still named as the base layer through late September.
Fable 5 is called better at mobile UX than a rival. Commenters still list its fonts and icons, along with a soft glow, as Claude's standard picks.

The same hero, every time 112

A Claude hero puts a small pill or eyebrow label above a big headline with one word in colour or italics and a one-line subhead over a solid button and an outline button, often followed by a stats row or product panel and a grid of about three feature cards.

“Claude Design creates the same layout every time, and you can clearly tell it was made by Claude” Reddit

Evidence

People describe a fixed page skeleton more than any single visual. Claude's first-pass sites open with a hero block. It puts a badge or eyebrow over an oversized headline and subhead, with two calls to action below. After the hero come feature cards, how-it-works, a CTA and the footer, whatever the product is. Many commenters still call the hero "centered" with "three cards, Inter and a purple gradient". That wording is the generic AI-template stereotype shared with Codex and Lovable among others. One tester re-ran the brief in July and found the purple, centred version no longer appeared. Claude now repeats a split hero with a pill badge, a contrarian headline, a highlighted word and a live product panel. The habit is the sameness across briefs. Three different clients get the same layout, and a sharp eye recognises it from the hero alone.

Signs people name, with the number of people naming each

Same layout regardless of brief Different prompts and clients get the same result. A portfolio, a car dealer, a restaurant and a status page all come back with the same hero and section structure.		40
Centred hero headline A big headline centred over a subhead. It is the most-named single feature, and people often pair it with "three cards".		29
Row of three feature cards under the hero Three equal rounded cards sit directly below the hero. Each often has an icon or emoji.		14
Soft gradient (purple/indigo or teal) behind the hero A gradient background or gradient button. Purple is the stereotype. The colours named as Claude's own are teal and sage, plus yellow-cream.		30
Pill badge or eyebrow text above the headline A small rounded pill or an all-caps eyebrow sits over the H1. The pill often carries a green dot or a version number.		9
Fixed section flow after the hero The order runs hero, features grid, a 1-2-3 how-it-works, testimonials or FAQ, CTA and footer.		6
Highlighted word and two contrasting buttons One word of the headline is set in a different colour or in italics. A filled button and an outline button sit side by side.		5
Extras right below the hero A thin marquee strip or a stats row sits in or just under the hero. Some pages put a version banner there.		4

Posted cases

1Pill badge above headline
2Highlighted word in headline
3Solid plus outline button
4Stats row under hero
5Same layout again in run 5
The same brief run repeatedly without the frontend-design plugin. The heroes repeat one another, each with a pill badge, a "Your status page shouldn't..." headline with a highlighted word, two buttons, a stats row and a live panel on the right.
clearly Claude. Thread

1Pill tagline above headline
2Second word in accent colour
3Three feature pills
4One big CTA button
5'How it works' scroll cue
A clean, warm landing page the owner built with Claude, which readers kept calling "clearly AI". It has a pill tagline, a two-tone wordmark headline, three feature pills, a CTA, a phone mockup and a "How it works" scroll cue.
clearly Claude. Thread

1Centred serif headline
2Italic accent-coloured words
3Install command box
4Solid plus outline button
5Mono '//' eyebrow label
6Grid background
A polished centred hero on a grid background, held up as the generic look the OP's Claude Code agent keeps producing. It has a serif headline with an italic blue phrase, a centred subhead, an install command, solid and outline buttons and a mono "REGISTRY // LIVE" label.
probably Claude. Thread

Easy to mix up with

Generic "AI slop" landing page in purple gradient and Inter. The purple-gradient look, emoji icons included, belongs to every AI builder and to older models. Claude repeats a skeleton, now often set in serif or mono type on cream or dark backgrounds with a split hero.
Claude's serif-headline look with one italic word and a tiny spaced label. The typography habit covers type and colour. Cream and terracotta belong to it. Here the complaint is about structure, meaning what sits in the hero and the order of sections. They often appear together.
Overstuffed app dashboards. Dashboards fill every space with cards and pills. The hero habit is a marketing-page opening that repeats from site to site.

Objections

Many say other tools land on the same SaaS skeleton because they share a training distribution, naming Codex, Stitch, Lovable and other models.
Defenders say Claude is defaulting and has not failed. With references and a token file plus a list of banned patterns, the output changes.
Even the official frontend-design skill does not fully break it. One user says every run with it still follows the same structure.
Some complaints are about density and clutter in apps, with too much on one screen. That is a separate habit from the hero template.

Changes over time

A July 2026 re-run of the same brief found the purple-gradient, centred, giant-99.99% cluster no longer appeared. Runs without the plugin instead repeated one split layout.
One marketer says it has improved over the last couple of model releases. First passes still come back in the same boxy structure.
Complaints continue through Claude Design in April and Fable 5 in July, up to Opus 5.5 in September.

Pill above the headline 93

Above the hero headline sits a small rounded pill or badge that often holds a coloured dot, and the page below repeats pills and chips inside generously rounded cards.

“The dead giveaway for 90% of zero thought landing pages is the pill above the h1 lmao” Reddit

Evidence

When Claude designs a page or app UI without a reference, it fills the gaps with pill shapes. There is an eyebrow badge above the H1 and status chips with a little green dot. Feature pills sit under the intro. Buttons and toggles become pills too. Containers around them get a large, uniform corner radius, so cards and panels all read as the same soft form, tiles included. Commenters say the strongest single field mark is the pill above the headline. The general "rounded corners" complaint is broader and partly shared with other AI tools and with shadcn/Tailwind defaults. Several note Claude even converts plain controls such as checkboxes and tags into pills when asked to make something look better.

Signs people name, with the number of people naming each

Pill or badge above the hero headline A small rounded eyebrow tag over the H1. Examples are "Launching First in Pennsylvania" and "CLAUDE CODE SKILL · MIT LICENSED". Often there is one per section.		14
Large radius on every container Cards, tiles, inputs and panels all share the same generous radius (rounded-2xl/3xl). People call it "rounded to oblivion" and "fingernail cards".		30
Pills and badges with no job Tag chips and badges scattered through content and lists, sometimes with pills nested inside pills. Commenters write "pills galore" and "wants to put everything in a pill".		16
Status pill with a coloured dot A pill holding a small green or coloured "status light" dot, sometimes blinking.		7
Fully rounded buttons Buttons with 50% border-radius, often a solid button beside a ghost button in the hero.		7
Rounded card with a coloured left border A single accent stroke on the left edge of a rounded box. People call it a giveaway in earlier models.		6
Cards nested in cards Rounded containers stacked inside one another.		5

Posted cases

1Dotted pill above headline
2Row of feature pills
3Pill tab toggle
4Tag pill in card
A clean, warm landing page with a dotted pill above the H1 and a row of feature pills. The phone mockup has pill toggles and tags.
clearly Claude. Thread

1Dot inside the pill
2Pill eyebrow above H1
3Pill shapes in mockup
4Big-radius card
A polished dark landing page for an anti-slop Claude Code skill. It still opens with a dotted pill eyebrow.
probably Claude. Thread

1Big-radius stat card
2Container with the same radius
3Rounded calendar tiles
4Round floating button
A tidy study-tracker app where every card and button carries the same large radius, tiles too.
clearly Claude. Thread

Easy to mix up with

The generic AI SaaS look of purple gradients and Inter over three feature cards. People blame the generic look on every AI builder. The parts they tie to Claude are the pill eyebrow with a dot and the uniform big radius.
Claude's cream-and-serif typography look in terracotta. The typography look is about fonts and colour. It often appears on the same page as the pills.
Codex/GPT UI defaults. Commenters set Claude's rounded edges against the sharper edges of Codex.

Objections

Rounded corners and bento grids predate AI, as do accent bars. Some designers resent them being treated as a tell.
Several argue the look is shared. They call it the Linear/Vercel/Stripe "premium SaaS" look built on shadcn and Tailwind defaults. v0 and Lovable produce it too, as does Cursor.
Some note that most people will not notice, and the result can still look good.
One user says Claude kept their app business-like and steered clear of the rounded purple look.

Changes over time

The rounded box with a coloured left border is described as a giveaway in earlier models. Someone asked about it for Opus 4.6.
From mid-2026 the pill eyebrow and dot badges become the main named shape tell. After Fable 5 turned checkboxes into pill switches, one commenter called pills "the big new AI flag for UX".
Complaints continue through September 2026. They come even with Claude Design, and with anti-slop skills installed in Claude Code.

AI-style copy on the page (em dash, metaphors, explanatory text) 64

New on the list. People started naming it in January, and a full write-up follows.

“Users are pointing to the fonts, buttons, and overall layout as the main culprits” Reddit

Cream and terracotta page 60

A warm off-white or beige background with rust-orange accent text and buttons sits under a large serif headline, often with one italic word and a tiny tracked-out label, in the palette people say comes from Anthropic's own branding.

“Claude Design LOVES to use an italicized serif font on a cream background, with tiny icons and generous whitespace.” Reddit

Evidence

When Claude styles a page without a colour brief (Claude Code and Claude Design included), it reaches for a warm cream or beige background, sometimes a "newspaper off-white". Accents are orange, which people also call terracotta and rust, and the headline is a large serif. Commenters treat this as one package with the type moves around it. One word of the headline turns italic and takes the accent colour. Above the headline sits a tiny all-caps or monospace label with wide tracking. Mono accents and rounded cards come along, and sections get numbered 01/02/03. Many say it is literally Anthropic's own brand palette, so a Claude-built site "could be part of the official anthropic site". The issue label's "sage green" is a minority strand. A handful mention beige with sage or pine green, while the dominant pairing in the evidence is cream with orange. A dark variant also gets called Claude's. It is near-black with orange or gold accents and the same serif.

Signs people name, with the number of people naming each

Warm cream or beige background People call it cream, beige, ivory, taupe, "piss colored", "newspaper off-white" and "warm peachy". It is applied to the whole landing page.		35
Orange accent in terracotta or rust Headers turn orange when no colour is given. People describe the accents as rusty orange, burnt orange, brown and orange, or "piss-yellow", and read them as the colour of Claude's own logo.		20
Large serif headline "That recognisable serif font", "big serif hero fonts", "brown 90s serif type", "the Anthropic serif font". It sometimes clashes with a rounded sans UI.		17
One italic word in the headline, in the accent colour The last word or a key word of the headline is set in italic serif and coloured, even when users ask it to stop.		4
Tiny tracked-out caps or mono label above the headline Eyebrow text, a "robotic mono preheader", monospace accents, status dots, a dash before the label.		7
It looks like Anthropic's own site People say the palette and type are copied from Anthropic branding, so the output reads as Claude's house style.		7
Beige with sage or pine green A smaller strand. Beige plus sage green, "the sort of colors you see on other note-taking apps".		3
Dark variant in black with orange or gold The same serif and tracked caps on near-black with gold or orange accents.		3

Posted cases

1tracked mono eyebrow
2italic serif word
3large serif headline
4spaced caps tags
5italic serif feature title
6cream palette with rose and rust
An editorial floral-studio hero built inside Claude Design. It sits on newspaper off-white with rust accents. A big serif headline carries an italic word, and tracked mono labels sit around it.
clearly Claude. Thread

1tracked caps eyebrow
2heavy serif title
301 02 03 numbering
4dash plus mono label
5italic serif quotes
6italic orange accent words
A tidy, credible video-editor portfolio on warm cream. It has heavy serif headings with red-orange accents and an italic accent phrase. Labels are in tracked mono.
probably Claude. Thread

1tracked caps heading
2italic serif quote
3cream rounded card
4gold accent stars
A clean testimonial strip in a small crop. A tracked caps heading sits over italic serif quotes on cream rounded cards with gold stars, the beige-plus-orange look.
probably Claude. Thread

1orange tracked mono eyebrow
2condensed serif headline
3italic orange words
4orange mono button
A handsome dark hero where the same recipe shows in orange. A tracked mono eyebrow sits above a condensed serif headline whose second line is italic and orange, next to a mono button.
probably Claude. Thread

1serif headline, gold words
2gold tracked caps button
3gold nav button
4serif stats, caps labels
A professional-looking betting-tool landing page in the dark variant. It uses black and gold with cream. The headline and stat numbers are serif, and the buttons use tracked caps.
probably Claude. Thread

Easy to mix up with

Generic AI look (purple gradients and Inter type with emoji icons). All tools share it, and people describe it as the 2024 era. The cream-and-orange serif look is tied to Claude specifically.
Claude's type recipe (italic serif word, mono eyebrow). The type moves ride along with this palette in many cases. Here, people name the palette of cream plus orange first.
Emerald dark-mode "skills" look. Emerald glow on dark backgrounds comes from Tailwind and skill examples used across models. It has none of the warm cream palette.

Objections

Some defend it as good, readable design. A warm background, a serif, an amber accent and caps for hierarchy beat the average developer design.
Any orange or brown now gets called "Claude color", even on designs taken from Squarespace or Dribbble.
The purple accent and the Inter or Geist look are a different thing. Commenters pin purple on ChatGPT and Inter with Tailwind on all AI tools.
People disagree whether it comes from Claude's defaults or from having the frontend-design skill switched on.

Changes over time

Described as the successor to the purple-gradient AI look of 2024. The new "AI slop" look is a warm peachy background with bright orange.
Some date it to Fable and to Anthropic adding it to the frontend skill or system prompt "lately". Some also tie it to the launch of Claude Design (the New Yorker piece).
Reports run from February to late September 2026 and are still coming in.

Hairline borders, edge stripe 57

Every container sits in its own card with a faint 1px border or soft shadow, status cards get a thick coloured stripe down the left edge, and frosted glass panels appear as a lesser, more generic layer.

“Claude goes insane with the very subtle borders and I don’t understand why it defaults to that for basically every container.” Reddit

Evidence

Under this label, commenters pin borders on Claude more than glass. Claude wraps nearly every container in a very subtle 1px border or a slightly different shade, and it nests cards inside cards. Tiles get a thick coloured border on one side only, often colour-coded by status. One designer calls the left border "almost as reliable a sign of AI-generated design as em-dashes for text". Soft drop shadows and hover glows ride along. Glassmorphism with backdrop blur, including imitation Liquid Glass panels, comes up a lot, mostly inside generic lists like "purple gradient, rounded cards, glassmorphism" that cover all AI tools. A few tie translucent badges and glass buttons to Claude and Fable 5 specifically.

Signs people name, with the number of people naming each

Coloured border on one side of a card A thick accent stripe on the left edge, sometimes the top, of tiles and callouts and even chat bubbles. It is often colour-coded green or red by status.		11
Faint 1px border around every container "Very subtle borders" on basically every container. Borders differ from the fill by a slight shade. Buttons and headlines get bordered too. Some call them "beveled borders".		11
Glassmorphism and backdrop blur Frosted translucent panels and imitation Liquid Glass boxes. Buttons and nav turn to glass. A semi-transparent badge sits above the title, and content unblurs on scroll.		12
Soft drop shadows and hover glow A shadow-on-hover transition on everything. Box shadows everywhere, the "AI styled shadow".		8
Cards nested in cards Every metric floats in its own card, and cards nest inside cards where flat dividers would do.		3
Pastel gradient behind bordered cards Pastel gradients with a 1px border around everything.		1

Posted cases

1green left-edge stripe
2red stripe for warning
3tinted icon tile
4stripe on every row
A polished dark connection-diagnostics screen. Every metric card carries a colour-coded stripe on its left edge. Green means healthy and red means jitter.
clearly Claude. Thread

11px border on card
2bordered profile pill
3bordered streak panel
4outlined calendar cells
A clean study-tracker dashboard where every panel and pill has a faint 1px grey border, down to the calendar cells.
clearly Claude. Thread

1translucent pill badge
2hairline-bordered chips
3soft drop shadow
4bordered shadowed card
A warm, tidy landing page whose tells are in the container treatment. It has a translucent pill badge and hairline-bordered chips with soft drop shadows. The phone mock holds a bordered card stack.
probably Claude. Thread

Easy to mix up with

Generic AI SaaS template with purple gradients and glassmorphism on rounded cards. People blame that bundle on Claude and ChatGPT alike, and on Cursor. The parts they tie to Claude are the one-sided coloured border and the hairline on everything.
Apple Liquid Glass. Claude fakes it with CSS translucency where real Liquid Glass elements exist, and the result reads as cheap.
Claude's cream-and-serif look. The cream look is a palette and type choice. It often appears on the same page as the borders and stripes, which treat the containers.

Objections

Rounded corners and cards are ordinary modern framework styling, and some call it unfair to treat them as AI tells.
The left border also comes from other models. A commenter says Gemini made the same green-edged boxes.
Some say the borders are fine design that simply became a recognisable trademark.
Glassmorphism is mostly named as part of a cross-model generic SaaS template and rarely as Claude's own.

Changes over time

Sonnet 4.6 was said to have cut down on "a lot of boxes with shadows" compared with earlier models. Contrast and spacing problems remained.
With Fable 5, a commenter says the models are "now producing a lot of glass morphism buttons and navigation menu".
Left-border and 1px-border complaints run from March to September 2026. One commenter expects the look to age badly.

Emoji as icons 49

Colour emoji (🚀 ⚡ 🔒 ✨, a megaphone for Marketing, a money bag for Finance) fill the places where a designed product would use an icon set, such as feature cards, sidebar items, filter chips, CTAs and hero headlines.

“its always just regular text and an emoji in a square” Reddit

Evidence

When Claude builds a web page or app without a design system, it fills icon slots with emoji. Each feature card or nav item gets one. An emoji sits in a rounded square above a heading. Sparkles appear beside headlines and buttons, and a rocket goes in the hero. Commenters treat it as one of the fastest tells of a vibe-coded site. The standard advice in feedback threads is "drop the emojis" and switch to an SVG icon set such as Lucide. It almost always comes bundled with the rest of the default look, like a purple-blue gradient on a dark theme with rounded cards. Several people say the emoji are Claude's way to make a page look finished without images. Most commenters see it as an AI default in general. The Claude-specific mentions come from people who built with Claude or Claude Code and from comments like "Claude does both these things".

Signs people name, with the number of people naming each

Any emoji in the UI reads as the vibe-coding tell "Using emoji at all is a HUGE red flag", "Questionable amount of emojis used", "Emojis in weird places", "the biggest telltale sign of vibecoding". The standard fix in feedback threads is to remove them.		20
Part of the default bundle with gradients and cards Listed together with purple/blue gradients, dark theme, neon accents, centred layouts and identical 3-card sections.		11
Emoji in icon slots on cards and CTAs "regular text and an emoji in a square", "emoji bullets", "oversized emojis", "emojis for CTAs", "random emojis".		7
Fix with an SVG icon set Replies say "try using SVG icons!" or "use lucide icons instead of emojis". Another says "use an icon pack instead of emojis".		3
The rocket emoji in particular "rocket emojis" and "rocketship emojis" serve as shorthand for vibe-coded SaaS.		3
Emoji as decoration because Claude has no images People say Claude's lack of image generation pushes it toward pills and cards with emojis "to make the website look good enought in first go". Others call it "emoji as decoration".		2
Arrow symbols alongside emoji "emojis or these stupid arrow symbols. Claude does both these things."		1
Carries into non-web layouts A brand manager reports Claude suggesting social-media emojis in a print skincare ritual card.		1

Posted cases

1sparkles beside headline
2emoji as filter-chip icons
3emoji as timeline markers
4emoji tiles on AI card
A warm, carefully finished iOS routine app where every icon slot holds a colour emoji. That runs from the filter chips and timeline nodes to the AI card and the headline. A commenter says it "gives AI made slop immediately".
clearly Claude. Thread

1emoji as page-title icon
2emoji as sidebar icons
3megaphone for Marketing
4money bag for Finance
A coherent dark dashboard with a tidy org chart. Each department and nav item is labelled with an emoji instead of an icon.
clearly Claude. Thread

1emoji face as avatar
2emoji face as avatar
3emoji for 'prefer not'
A clean onboarding screen with a wheel picker and a progress bar. Its gender options use emoji faces as avatars. The reply praises the progress bar and says to swap the emoji for SVG icons.
probably Claude. Thread

Easy to mix up with

The generic purple-gradient AI look. Gradients and cards are the colour and layout part of the default. Emoji in icon slots usually appear with them, but either can occur alone.
Claude's editorial serif look (big serif headline, cream background). Claude's newer house style. Emoji icons belong to the older dark gradient SaaS default. Emoji also show up on the cream style as sparkles and chip icons.
Emoji in chat replies or code. They live in the shipped UI that end users see. Emoji in Claude's chat messages or source comments belong elsewhere.

Objections

Other models do it too. Commenters call it what "AI" or "LLMs" default to. One notes Claude uses emojis with "almost the same design patterns" as DeepSeek.
Sometimes the builder chose it. Some developers say they picked emoji on purpose for speed or recall, which others reject.
Easy to prompt out. One designer says the emoji and purple are trivial to remove and the copy is the harder tell.
Some Claude-built pages have none. A Fable 5 landing page drew AI accusations with "not a single emoji". One user says Claude Design produces design without emoji that does not look AI-made.

Changes over time

One commenter (August 2026) ties emoji plus purples and blues to what "opus 4.1 would produce", which suggests an older default.
Claude Design (from spring 2026) is reported both ways. One user says it avoids emoji. Another says its layouts "often include AI generated emojis".
Reports run from January to September 2026 without a clear drop. Some Fable 5 era pages are noted as emoji-free.

One spacing rhythm everywhere 46

All the sections and cards share one tidy spacing rhythm and one visual weight without any tight groups or chosen empty space to show what matters.

“Spacing: AI defaults space everything evenly, which flattens hierarchy.” Reddit

Evidence

When Claude builds a page or app screen unbriefed, commenters name spacing as one of the first giveaways. They usually mention it in the same breath as fonts and colour. The most common description is uniform spacing. Every section has the same rhythm and every card the same padding and weight. Three equal cards sit centred and symmetric, so the hierarchy goes flat and "nothing feels decided". A second group says the same pages have too much whitespace, with big empty bands above and between sections. A third describes the opposite of "perfectly even". In their reports the spacing drifts between sessions or squeezes things together and then leaves huge gaps. So the label "perfectly even spacing" is only half right. What people recognise is a default spacing rhythm applied mechanically. It reads as evenness on a landing page and as inconsistency once a project grows.

Signs people name, with the number of people naming each

Same spacing rhythm in every section Every section and card uses the same spacing and the same gaps. No section gets priority and no group feels tight, so hierarchy flattens.		12
Equal-weight cards in a symmetric, centred layout Three equal cards of the same weight sit under a centred hero, and every CTA gets the same treatment. One commenter calls it "uniform contrast (everything same visual weight)".		6
Inconsistent or "weird" spacing that feels undecided Spacing rhythms do not quite line up and buttons align with nothing. Tight squeezes alternate with gaps. This is the opposite reading of the same default.		8
Too much whitespace Big empty bands above the fold and between sections, with generous air everywhere instead of where it matters.		5
A single default spacing scale People call it "8px-everything spacing" or just "default spacing". It is part of one visual skeleton the model falls back to.		4
Spacing drifts between prompts In longer projects Claude Code rewrites spacing and radii every few prompts until tokens are pinned.		2
Ignores spacing instructions Users have to repeat spacing fixes several times. The model falls back to its template even with specific instructions.		2

Posted cases

1two equal stat cards
2same gap between blocks
3same gap again
4uniform grid cells
A tidy, good-looking dark study tracker. Every block gets the same rounded card with the same inner padding. The gaps between blocks match, so no section leads.
clearly Claude. Thread

1empty band above hero
2pill above the name
3three equal-weight chips
4next section far below
A polished cream landing page with a large empty band above the hero. Below it the pill and chips are stacked at one even rhythm down to the CTA, flattening the hierarchy.
probably Claude. Thread

Easy to mix up with

The generic 2024 AI look of purple gradients and bento grids with gradient hero text. A colour and component cliché shared by all tools. The spacing complaint concerns rhythm and hierarchy and remains after the gradient is gone.
Claude's type recipe (serif headline with an italic word, tiny tracked label). Usually named next to spacing as part of the same Claude look. People spot the type first. The spacing is what makes the page feel templated.
Unpolished vibe-coded apps. Sloppy vibe-coded apps have mismatched spacing all over. Claude's version stays tidy and consistent yet flat.

Objections

Several commenters blame the opposite fault in spacing that drifts or gets squeezed and is inconsistent. So the field mark is a default rhythm, and the gaps need not be literally identical.
Some say the copy is what feels generic. The person defending the layout point agrees it is both.
In defence, these were ordinary good-design patterns before AI. They became giveaways only because everyone ships them.
Many complaints are about AI-built sites in general, with Claude as the tool in the thread. Some group Claude with Gemini and Bolt explicitly.

Changes over time

Sonnet 4.6 was said to bring better animations and more font variety with fewer shadowed boxes. Excessive spacing and low contrast carried over.
By mid-2026 commenters say the tells moved from the purple gradient to typography and "the same spacing rhythm".

Dark by default, grey on grey 43

An unbriefed app or dashboard comes out on a near-black background with slate-grey cards and small low-contrast grey secondary text.

“Claude makes everything dark by default, so you assume incorrectly.” Reddit

Evidence

When Claude designs an interface without a colour brief, many users say it picks a dark theme by default. They report this from Claude Code and claude.ai as well as Claude Design. It happens most on dashboards and tools, data reports among them, where it drifts into a "hacker" or terminal-style dark look. The backgrounds are layered greys. Slate or dark-grey cards sit on a near-black page in a neutral grey palette. One blue or purple accent with a soft glow often comes with them. People complain most about the text. Labels and helper copy come in light or mid grey on dark grey. They are frequently small, which makes them hard to read. The low-contrast grey text also shows up on Claude's light cream pages, so "grey on grey" is the more durable habit. "Dark by default" is the most common description for tool and dashboard UIs.

Signs people name, with the number of people naming each

Dark theme by default Unbriefed apps and dashboards come out dark, landing pages too. Users say they did not ask for it and have to steer away from it.		16
Grey text on dark grey Secondary text and labels in light or mid grey on dark backgrounds, empty states too. They often fail contrast. One commenter describes "grey on dark grey making it unreadable".		9
Purple or blue accent with glow on the dark Purple pills and glows sit on the dark background with neon gradients. Other AI tools share this.		6
Slate-grey cards and neutral grey palette Identical slate grey cards, a dark sidebar, a card grid, a neutral grey palette, a blue/grey colour choice.		4
Hacker or terminal dark look for data Asked for a report or tool on data with no design input, Claude produces a "hacky terminal dark theme".		3
Tiny text on the dark Small font sizes make the low contrast worse ("9px font", "text for ants").		4
Every dark card has equal drama Borders and shadows on every card. Equal-weight KPI cards sit on the same dark background.		2
Claude Design falls back to Anthropic's own dark colours Without a brand, Claude Design defaulted to the Claude app's own dark-mode palette.		1

Posted cases

1grey subline on black
2dim grey caps label
3dark grey card surface
4low-contrast grey text
5grey cells on grey
A polished study-tracker screen on near-black with dark-grey cards. The date line and caps labels are dim grey on grey. So are "Best: 9d" and the calendar dashes.
clearly Claude. Thread

1dark grey stat cards
2small grey helper text
3grey grid on dark
4grey labels in tiles
A capable, dense desktop dashboard in layered dark greys with small grey helper text, the kind one commenter could "go 10 years without seeing another" of.
probably Claude. Thread

Easy to mix up with

The generic AI SaaS look of purple gradients and glow with emoji. Every tool adds that accent layer. The Claude complaint is the dark-grey background itself and the low-contrast grey text.
Claude's cream-and-serif landing page look. The other common Claude default, used for marketing pages. It shares the faint grey text on a light background.
A chosen dark brand or terminal aesthetic. Those are requested. The habit is dark appearing when the prompt said nothing about colour.

Objections

Many commenters say dark mode is the default of all AI tools (ChatGPT, Gemini, v0, Lovable, GLM), with Claude one of many. One 300-site comparison is read as "Claude likes dark mode, GPT likes gradients".
Claude's landing pages are just as often described as light cream. The dark default is strongest for apps and dashboards, data tools included.
Dark is fine in itself for some subjects. For a magician's site it is what every human designer does too.
Some dark results were the user's choice. One was a requested retro CRT terminal. Another maker says the palette was his own pick.

Changes over time

As of Sonnet 4.6, low contrast is described as "a problem it has carried from the beginning".
Through the Opus 4.7 and 4.8 period and into Fable (May to July 2026) the dark default is still reported. One user says Fable built "generic minimalist dark mode" where the mockup from 4.8 had not.
Still reported in September 2026 alongside Sonnet 5.

An eyebrow over every heading 41

Nearly every heading on the page has a small, all-caps, widely spaced label sitting above it, and sections may be numbered 01, 02, 03.

“It's like the design version of em dashes that's a dead giveaway that a site was designed with AI.” Reddit

Evidence

Commenters say that when Claude builds a landing page or an app screen, it puts an 'eyebrow' above almost every headline and section heading. An eyebrow is a short kicker line. Portfolios get it too, and Claude Design does it most of all. The label is small and set in capitals with extra letter spacing. It is often monospace or in the accent colour, and it often comes with a status dot or a blinking green dot. A related tic is numbering sections or cards '01', '02', '03' in front of the title. People call it 'the design version of em dashes'. Editors have used the eyebrow for decades. What gives Claude away is that it adds one everywhere by default, and the text in it is often filler.

Signs people name, with the number of people naming each

An eyebrow over every heading A small kicker sits above the hero headline and above each section heading, on every page by default.		17
Small capitals with wide letter spacing The label is tiny and uppercase, with the letters tracked out. One commenter describes 'all-caps subtitles with extra letter spacing above titles'.		10
A status dot in front A coloured or blinking green dot leads the eyebrow or pill. Commenters call it the 'status eyebrow'.		8
01 / 02 / 03 numbering Sections or cards carry a number in front of the title. People read it as a Claude Design and Claude Code tic.		5
Explanatory subtext on every block Every block gets an eyebrow and a line of subtext. One commenter calls the eyebrow copy 'rubbish, and perhaps even nonsense'. Instructions turn up in random spots.		4
Monospace eyebrows Very small eyebrows set in a monospaced font.		3
Eyebrow in the accent colour The eyebrow takes the accent colour, for example orange-tinted subheadings.		2

Posted cases

1banner above the name
2status-style dot
3tracked capitals section label
4small capitals label
A warm, finished landing page with a pill banner led by a dot above the product name and a tracked capitals 'HOW IT WORKS' label. This is the restrained form of the habit.
probably Claude. Thread

Easy to mix up with

Claude's serif headline with one italic word. The eyebrow is one part of that hero section. It also appears without the serif. Sans-serif pages and app screens get it too.
The generic pill badge above the headline. A rounded pill ('New: ...') is an older move from generic SaaS pages. Claude's eyebrow is plain tracked capitals. It is often monospace and often has a dot. It repeats on every section.
All-caps text in interfaces generally. Some people object to capitals anywhere. The Claude tell is the small label placed above headings.

Objections

Editors and ad designers have used eyebrows for decades. Other names for them are kicker and overline, and some say pre-head. The tell is that Claude puts them everywhere.
Some users keep them on purpose because they look good. A designer defends the Claude Design look as clean and well structured.
An eyebrow alone does not make a page look vibe-coded. The look comes from pairing it with monospace type and dots, and with serif headings.
Claude is not the only source. Open Design is named too, and one thread summary blames lazy users who give no design input more than the model.

Changes over time

Named from the Claude Design launch in April 2026 onward, most heavily from June to September 2026.
Users say the tells got heavier after Opus 4.8 and Fable 5. In September Fable 5.1 still 'did the classic over designed/over explained format with eyebrows'.

Everything fades in and floats 27

Scroll down the page and each section fades up 20px into place. Cards and buttons lift under the pointer, and a background of dots or lines keeps moving.

“Things that move, float, slide, appear for no reason, glowy text -- why are they there? ” Reddit

Evidence

When Claude builds a landing page or app UI it adds the same small set of motion effects by default. Sections and cards fade and slide up as they enter the viewport. Buttons and cards rise or glow on hover. A marquee or ticker scrolls sideways under the hero, and decorative backgrounds such as connected dots are animated. Commenters describe the motion as one keyframe used everywhere ('a keyframe going from y: 20 to y: 0'). They also say it has no purpose ('things that move, float, slide, appear for no reason'). Users report it appears with different prompts and that they have to ban it in CLAUDE.md or DESIGN.md. It comes bundled with gradients and Inter type and the other cues of a generic AI site. Most commenters treat it as part of that look and do not call it a Claude-only trait.

Signs people name, with the number of people naming each

Fade in and slide up on scroll Commenters describe 'Same fade in and reveal animations on scroll in' and 'default sliding animation as you scroll'. Others write 'fade-on-scroll' and 'scroll appear items'. One calls it 'the same glitchy fade and slide'.		8
Rise and bounce on hover Buttons and cards lift up and down on hover. One user calls them 'unnecessary hover animations'. Another calls a hover border on cards 'a claude thing'.		4
Animated decorative backgrounds Animated dots or a network of connected dots fill the background. Some elements glow or float.		3
Marquee or ticker strip A marquee scrolls sideways under the hero on nearly every marketing site. One commenter calls it 'the html equivalent of em dashes'.		2
Motion everywhere from one keyframe Users report 'overuse of gradients and animation/motion everywhere' and 'a lot of animations. not diverse animations'. Pages get 'animated transitions' to look sleek, and some use scrolljacking.		5

Posted cases

1Drifting background dots
2Lines between dots
3Scroll progress bar
A polished site built with Claude Code for a paying client. The faint network of connected dots behind the cards is the animated background commenters asked to remove. A scroll progress bar runs along the top.
clearly Claude. Thread

Easy to mix up with

Gimmick chips and fake terminals. Those are static decorations. The tell here is in how things move.
The generic AI landing-page layout. Hero, tagline, call to action and three cards make up the layout. Motion adds reveals and hover lifts on top of it.

Objections

One designer says the 'Webflow-ization' of constant text animation on scroll 'seems to be dying out'.
A commenter pushes back that rounded corners and a scrolling homepage do not prove Claude made a site, and calls it 'Ai Paranoia'.
Several comments describe AI sites in general and do not single out Claude.

Changes over time

Reports run from January to September 2026. One designer's comment in July 2026 suggests animation on scroll is becoming less common.

Dot-pill chips everywhere 16

A rounded pill holding a small coloured or pulsing dot and a short phrase sits above the hero headline, or on each card as a status tag ('• Productive', '• GRANTED').

“Design is GREAT. only vibecoding tell is the chip bubbles.” Reddit

Evidence

The gimmick people name most is the chip. It is a small rounded pill. Many have a coloured dot in them, sometimes a flashing green one. It sits above the hero headline carrying a slogan ('• You owe it to yourself •') or serves as a status tag on cards. Commenters call it 'the classic AI status pill' and say it is the last vibe-coding tell left on otherwise strong designs. Two people call fake terminal windows a dead giveaway. A few add soft glows and gradient borders that follow the mouse, as well as blurred dark-blue backgrounds. Several people list the chip together with gradient headlines and small labels above headings. They treat it as one part of a wider kit Claude uses for landing pages. The original label said 'live chip, fake terminal'. The chip part holds up, and the fake terminal has thin support.

Signs people name, with the number of people naming each

Pill chip above the hero headline A chip with a dot and a slogan sits above the title. Commenters describe 'little labels above headings' and 'a random chip that the AI put up'.		5
Status chips on cards Cards carry 'chip bubbles' like '• Productive' and '77 of 100', which one user calls 'the classic AI status pill'. Some of the chips and tags are inaccessible.		3
Little flashing green dot Named as an AI tell next to subheadings above h1 and h2.		1
Fake terminal windows Mockups of terminal windows used as decoration on landing pages.		2
Glows and blurred backgrounds, plus borders that follow the cursor Commenters list 'fluff effects, black-blue/purple blurred background' and 'soft glows, rounded edges and hover effects'. Others mention 'gradient borders that react to your mouse cursor' and 'glowy text'.		5
Highlighted words and over-explained micro-copy Single words in the headline get a colour. Labels in the style of 'You are here' appear.		1

Posted cases

1Dot chip above headline
2Row of icon pills
3Tag chip on card
A warm, well-made landing page. A pill slogan with dots sits above the headline and a row of pills with icons sits under the copy. These are the chips commenters point to.
clearly Claude. Thread

1Dot status tag
2Same tag repeated
A clean client site where each card ends in a status tag made of a dot and uppercase text. A commenter calls it 'the classic AI status pill'.
clearly Claude. Thread

Easy to mix up with

Tiny spaced-out uppercase label above the headline (a Claude type habit). The eyebrow is plain text. A chip is a pill with a border or a fill, and it carries a dot in most cases.
Everything animates. Glows and pulsing dots appear in both. This habit covers the static decoration itself and leaves scroll and hover motion to the other one.

Objections

When Opus 5 calls every rounded UI element a 'chip' in conversation, that is a habit of vocabulary and has nothing to do with chips on the page. Another commenter notes that 'chips' is also a real feature of the Claude app.
One commenter says the 'AI slop' talk mostly comes from salty designers and that the look is fine if users are happy.
Several comments describe AI templates or Tailwind and shadcn templates in general and do not single out Claude.

Changes over time

Reports run from January to September 2026. Complaints about the chip cluster from June onward.

When Claude writes

14 habits named by 2,921 people between 1 January and 5 October 2026.

1Opening dash before list
2Closing dash after list

1,787 people

The em dash hinge

A spaced " — " turns up several times per reply to bolt a punchline or a reason onto a sentence that needed a period.

“I've never read anything that had over a hundred em-dashes in like three pages.” Reddit

Evidence

Claude reaches for the em dash, with a space on each side, to join a short opener to its elaboration ("Better — but for a reason worth naming"). It also wraps inserted lists in a pair of dashes and sets up contrasts. Commenters object to how often it appears and to the job it does. It shows up several times per message, even in two-sentence chat replies, and stands in for periods and colons where there is no real aside. It travels with Claude's other tics. Commenters single out the "not X — Y" contrast and the words "honestly" and "load-bearing". Many users complain that it survives bans in preferences, memory, CLAUDE.md and skills. A ban can simply swap it for a double hyphen ("--"). In this period people treat it as more of a Claude habit than a ChatGPT one, and they report that Opus 5.5 and Fable 5.1 (September 2026) have mostly dropped it.

Signs people name, with the number of people naming each

Too many em dashes Several per reply, "every other sentence", even in very short answers. People compare the count with human writing.		600
Survives bans, or turns into "--" Instructions in memory, preferences, CLAUDE.md or skills fail. A ban can bring back a double hyphen with the same rhythm.		200
Comes with the other Claude tics Appears next to "not X — Y" contrasts, "honestly/genuinely", "load-bearing" and rule-of-three rhythm.		150
A hinge where a period would do Stages a pause or bolts on a punchline or an unrelated clause where a period or colon fits. It is rarely a true parenthetical.		40
Spaces on both sides " — " with a space each side, which American editors don't use. People tie it to Opus 4.6 and also see it in German LLM output.		10
Short opener, then dash A reply or comment opens with a two-word verdict followed by a dash. Examples are "Better —" and "Ha —".		10

Posted cases

1Opening dash before list
2Closing dash after list
A careful, well-reasoned audit note. A pair of spaced em dashes wraps an inserted list, the most typical Claude use, in work that is otherwise excellent.
clearly Claude. Thread

1Two-word verdict, then dash
2Dash bolts on the fix
A precise bug explanation that opens with "Better —" as a hinge and uses another dash to bolt on the fix.
clearly Claude. Thread

1Paired dashes as aside
2Dash instead of colon
3Dash instead of colon
4Dash before the kicker
A clear, well-structured recovery plan where five spaced em dashes stand in for colons and periods, and one pair works as parentheses. The commenter counted six in the message.
clearly Claude. Thread

1Dash in one-line reply
Asked for a one-word answer, Claude adds a single witty sentence and still hinges it on an em dash.
clearly Claude. Thread

1"genuinely" then dash
A short, likeable chat reply that still uses a spaced em dash right after "genuinely", the exact pairing the commenter named.
clearly Claude. Thread

Easy to mix up with

The generic AI em dash (ChatGPT era). Commenters say ChatGPT has largely stopped, so by mid-2026 a heavy dash habit points to Claude in particular. The Economist reportedly found Claude to be the only major model still overusing them.
The "not X, it's Y" contrast. The contrast is a sentence shape. It can hinge on a dash and also appears with commas or periods. It is a separate habit that travels with the dash.
Human typographic em dashes. Human writers close the dash up with no spaces and use one or two a page, mostly for asides. In Claude's version the dash has spaces and appears several times a reply, where it works as a pivot.

Objections

The em dash itself is fine. Good writers, editors, The New Yorker, Wikipedia and legal writing have long used it. The objection is to overuse and to using it where other punctuation fits.
On its own it does not prove AI. Many people who used em dashes before AI say they now get accused of being bots and have stopped.
Some argue the tell is the overall cadence. People still sense AI after the dashes are removed.
Readers mistake hyphens and en dashes in a comment for Claude's em dash.

Changes over time

In early 2026 people called it characteristic of Sonnet 4.6 and Opus 4.6, in the spaced style. One user says Opus 4.7 began "constantly" using them compared with 4.6.
From May to August 2026 it was seen as more of a Claude habit than a ChatGPT one. Opus 5 and Sonnet 5 were called the heaviest users and the hardest to instruct out of it.
In late September 2026 Opus 5.5 "cut out em dashes almost entirely", about 0.8 per response on Arena by one reading. Fable 5.1 and Fable 5.5 write without them. Users say they no longer need CLAUDE.md bans, though the other Claude tics remain.

Claudish engineering words 385

Engineering metaphors such as "load-bearing", "seam", "blast radius" and "footgun" turn up everywhere, even in non-technical text, alongside one-off coined labels.

“You can't be claudish native without stuffing load-bearing in every other sentence.” Reddit

Evidence

Claude reaches for a small set of borrowed engineering and construction words and uses them as all-purpose labels. Something important is "load-bearing" and a clean boundary is a "seam". A risky change has a "blast radius" and a trap is a "footgun". The decisive clue is a "smoking gun". It also coins one-off labels on the spot ("the durable gate", "mannered prose") and leans on compressed metaphors and personification. Things "land" and "bite". They "buy" time and act "quietly". Commenters say each word is fine on its own. The tell is that the same few words show up in almost every reply, including plans, specs, READMEs and posts that people then publish. Many call the whole register "Claudish" or "Claude-speak". For a lot of readers it makes otherwise correct text harder to parse, because the metaphor has to be decoded back into plain meaning.

Signs people name, with the number of people naming each

"load-bearing" / "load bearing" By far the most named word. It marks the essential part of an argument or a code path ("X is convenient but not load-bearing", "The critical caveat, and it's the load-bearing one for this whole document..."). It survives explicit bans. In screenshots Claude cuts off mid-word or swaps the spelling.		80
compressed or nonsensical metaphors Commenters quote "Metaphors that don’t make sense" and "incoherent, strained metaphors". Time is always being "buying" where a person would say it increased. Others name "the snap closer with a monetary metaphor arriving out of nowhere" and "Fancy metaphors, weird jargon".		30
made-up one-off jargon and coined terms Commenters say "it makes up its own one-off jargon on the spot" and complain of "obscure / abstract terms it makes up while building but never properly defining in docs". Examples include "the signal is only carried by the durable gate" and "mannered prose". One calls it "The made up technical jargon".		19
"quietly" / "quiet" Examples include "It quietly does the work" and "Quietly failing". Described as the newest tell after em dashes and "load-bearing".		12
"smoking gun" Named as a stock Claude phrase and paired with "load-bearing".		8
"seam", "spine", "footgun", "blast radius" The construction and engineering words, as in "well-defined seam", "the spine and seam of Claude", "blast radius" and "footgun". Some teams use "footgun" and "blast radius" normally. People call "seam" and "spine" Claude-only.		12
personification of abstractions "Things landing. Things shipping.", "constraints don't bite", "Physics starts paying attention", toasters and floors with motives.		8
"earn its keep" and "does the heavy lifting" Phrases for "this matters" in the same family as "load-bearing", including "holding real weight".		4
"substrate", "hinge", "surface" (as a verb), "hard gate", "wedge" Less frequent words in the same register.		6

Posted cases

1Section titled with a coined label, "the deliberate gap"
2"a well-defined seam" for 'an easy place to add auth'
3"load-bearing here" for 'important'
4"trap ... already sprung" metaphor
A real Claude Code repo summary that is accurate and well organised. Coinages are sprinkled through it ("the deliberate gap", "well-defined seam", "load-bearing here", "already sprung"), and the plugin's English column has to translate them away.
clearly Claude. Thread

1"load-bear—" cut off and replaced with plain words
A plain, competent status update where Claude starts "load-bear—" and corrects itself mid-word, showing the word surviving a ban.
clearly Claude. Thread

1Bold lead "The video was a locked door."
2Closing quip "just the treasure map — the treasure was already in your install folder"
A clear, well-structured explanation of what Fable actually did. It opens on a "locked door" and closes with a treasure-map quip.
clearly Claude. Thread

1"I kept the metaphor and swapped the spelling"
A system prompt banned "load-bearing". Claude wrote "load-carrying" and then admitted it kept the metaphor.
clearly Claude. Thread

Most memory projects are a thin layer over an off-the-shelf vector store and someone else's graph library. This one isn't. The load-bearing pieces¹ are my own code, written for this exact workload — a small memory graph that mutates every night and gets queried on every recall

1"load-bearing" for "core"

A readable README paragraph where "load-bearing pieces" stands in for "the core parts".

probably Claude. Thread

Easy to mix up with

Buzzword corporate register. "Leverage" and "delve" belong to the generic AI word list. Claudish is Claude's own vocabulary of engineering metaphors.
Candour labels and signposts. "Honest caveat" and "worth flagging" frame what comes next. Claudish puts invented jargon into the content itself.
Sycophancy. "You're absolutely right" is a separate chat complaint that commenters lump in.

Objections

Not every engineering term is a tell. Commenters say "footgun" and "blast radius" are normal on their teams, and "load-bearing" is standard architecture language. Claude gives itself away by using them everywhere, including non-technical text.
Claude uses the words correctly in most cases, and several people find them precise, useful shorthand. What gives Claude away is frequency.
Humans used "load-bearing" before AI. People who use it now get mistaken for Claude or laughed at in meetings.
Sycophancy ("You're absolutely right") and em dashes are separate habits, though commenters lump them in here.
Many quoted "examples" in these threads are parodies, or Claude roasting itself on request.

Changes over time

Commenters date the heavy version to Opus 4.8 and above all Opus 5. They remember Opus 4.6 as cleaner, and some stayed on it for that reason.
Opus 5.5 is reported to have toned it down, with "load-bearing" rarely seen. Some still see the register, and one sighting caused alarm.
Some read Fable 5.1 answers as "no claudish". In one small non-English language Fable dropped "load-bearing".
The favourite word drifts over time. Em dashes came first. Then came "genuinely" and "load-bearing", and now "quietly".
"Load-bearing" resists system-prompt bans. Claude swaps the spelling or corrects itself mid-word.

Document furniture in prose 345

A short answer or post comes laid out like a briefing in which headers sit above bullets that each open with a bold label and a dash.

“Bold points, followed by unbold subpoints is literally claude's formatting.” Reddit

Evidence

Commenters describe a layout more than a single mark. Claude turns an answer or a post into a structured briefing. It adds headers and puts bullet lists where a paragraph would do. Each bullet or paragraph starts with a bold run-in label ("**Problem 2 — No kernel trick.**"). In Claude Code docs whole sentences go in bold as headlines. In chat the section titles are punchy ("The Gap", "What it actually does"). Emoji are the loud minority form. They serve as section icons or check marks, and some messages end on one favourite emoji as a sign-off. Those reports cluster from March to June 2026. A large share of the comments are people clocking AI-written Reddit posts and naming Claude loosely. The strongest Claude-specific forms are therefore the bold-label bullet and the bold headline sentence. Emoji are weaker evidence. All-lowercase text with the same structure is a disguise people add on top. Claude does not write that way by default.

Signs people name, with the number of people naming each

Bullet lists where prose would do Answers and even short replies are broken into bullets or numbered lists, often of three items. People ask for "plain prose" in their instructions to stop it.		140
Bold run-in label on every point Each bullet or paragraph opens with a bolded term. A dash or colon follows, then the explanation. Key sentences mid-paragraph are bolded too.		46
Emoji as icons and sign-offs Emoji sit on section headings and check marks on list items. They appear in planning mode, and a recurring favourite emoji ends each message.		77
Headers on short pieces, with punchy titles Section headers on content that does not need them. Titles run like "The Gap" or "The one most people miss". Header sizes come out mismatched where the text is pasted.		31
Markdown that leaks Raw ** or ## stays visible where Reddit or Word cannot render it. Casual posts get markdown dividers.		16
Lowercase on top of the same structure People prompt Claude to write all lowercase to look human. Readers treat lowercase plus tidy structure as a tell of its own.		36
Italics for emphasis Single words italicised for stress inside argument sentences.		13
Typographic furniture Curly quotes, arrows, section signs and circled numbers in docs and posts.		13

Posted cases

1Emoji on each heading
2Opens "Great question!"
3Raw ** bold markers leak
4Bold label, dash, explanation
5Rule between sections
A correct, well-paced Claude.ai explanation of SVM duality. It has an emoji on every heading, bold run-in labels, rules between sections and bold markers leaking as raw asterisks.
clearly Claude. Thread

One rule, applied twice:¹ **the product gets the well-known port, management moves aside.**² **The app itself sits on 8080, and that is the same decision made the other way.**³ Above 1024, so its unit needs no `AmbientCapabilities` at all

1Labelled setup before claim
2Sentence bolded as headline
3Next paragraph opens bolded

An accurate, reasoned Opus 5 deployment note where whole sentences are bolded as headlines inside the prose. The thread's opening post quotes it.

clearly Claude. Thread

The tail degrades in fairly predictable ways:¹ - **Re-description** —² item 6 is item 2 restated one abstraction level up, so it reads as new - **Criterion drift** — the implicit definition widens mid-list to admit weaker candidates - **Fabricated specifics** —³ this is the dangerous one. In sparse domains, a plausible citation, date, or case name is cheaper to produce than an admission of a short list

1Colon setup into list
2Bold label then em dash
3Same pattern every bullet

A sharp, useful answer about list padding, delivered as bullets that each open with a bold term and an em dash.

clearly Claude. Thread

1Bold run-in lead
2Line ends on a dash
3Bullet-less fragment list
4No closing periods
A thoughtful reading of a game symbol. It is built from bold run-in leads and stacked fragment lines that end on dangling dashes where sentences should be.
clearly Claude. Thread

1Emoji sign-off
A warm, articulate message from a long-running Claude instance that ends on its habitual emoji, the sign-off users describe.
clearly Claude. Thread

Easy to mix up with

Generic ChatGPT-style formatting (rocket emoji and check-mark bullets under a "Great question!" opener). Commenters put emoji-heavy layouts on ChatGPT first. The Claude-specific form is the bold-label bullet and the bold headline sentence, with emoji only in some months.
Claudish vocabulary ("load-bearing", "seam"). Claudish is a matter of word choice. The two habits turn up together in the same doc.
Em dash habit. The em dash habit concerns punctuation inside sentences. In this layout the dash matters only as the separator after a bold label.

Objections

Several users say Claude defaults to paragraphs and that this is why they prefer it to ChatGPT. One points to the system prompt that suppresses heavy formatting.
Claude mirrors the user and rarely uses emoji unless the user does first. ChatGPT, one says, "will throw emojis all day".
Bold text and bullets are ordinary good formatting, and so are headings. People writing by hand get accused of AI for using them.
All frontier models share much of this layout, so it points to AI in general before it points to Claude.
Users prompt for the all-lowercase style to hide AI output. Claude does not default to it.

Changes over time

Emoji complaints rose from March 2026. Posts said "Claude started writing with emojis just like ChatGPT" and people reported emoji in Opus 4.6 planning mode. They peaked from April to June. By September people talk about emoji as something Claude used to do.
Opus 4.7 was described as essay-ifying chat answers with punchy section headers.
Opus 5 in Claude Code writes docs with bolded headline sentences and dense structure.
Opus 5.5 is said to have toned this down. A commenter asks whether that means fewer bullet lists and bolded headers.

…ar in my post describes a detector *misfiring*, not a watermark *working*. That distinction matters and I blurred it for rhetorical effect. Fair hit.¹ Where I’d push back: you’re folding two different things into “signature.” The stylistic tics you hate — the confident cadence, the “brass tacks” tone that doesn’t pay off — are habits, and habits are imitable, removable, and already everywhere in human sales copy (as …

Metronome paragraphs 298

Every paragraph runs about the same length and closes on a tidy, quotable line, with short clipped fragments in between.

“I'm also finding myself noticing and trying to avoid the rhythm and cadence of Claude's writing, which in itself is very well structured, but just feels so artificial now.” Reddit

Evidence

Commenters describe a cadence more than any one phrase. Paragraphs come out near-identical in length and build, each a claim with support that ends on a short landing line. Sentences run to similar lengths. Rhythm devices recur. One is a run of verbless fragments ("Already plans. Already writes tests."). Others are the "not X, it's Y" turn and the three-beat list. Each paragraph closes on a neat summary or verdict line, so the text reads like a metronome or a speech with breath marks. It survives bans on vocabulary and em dashes and even all-lowercase disguises. People call it the tell that is left once the word tells are gone. Many complaints say "AI" in general. In Claude threads people tie it to Claude's own voice. With Opus 5 and Fable 5.1 a second form appears, long dense paragraphs with few breaks that are just as even.

Signs people name, with the number of people naming each

Every paragraph the same length and shape Paragraphs come out as even chunks, often about three sentences each, so the page looks like neat swappable blocks.		60
A neat closing line on every paragraph Each paragraph ends on a confident verdict or gotcha line, the "little bow" at the end.		45
Staccato fragments and one-line paragraphs Runs of clipped or verbless sentences and stacks of single-sentence paragraphs, used to manufacture emphasis.		40
Uniform sentence length Low variation in sentence length ("every sentence the same cadence"). People quote 15 to 20 words with tiny spread.		40
Repeated contrast turns and triads "It's not X, it's Y" and "No A, no B, just C" recur as beats alongside groups of three, often several per post.		40
Cadence persists under disguise Lowercased or dash-free posts, even ones seeded with typos, still read as Claude because the paragraph rhythm stays locked.		20
Every point weighted and resolved equally One polite paragraph per consideration, each landing softly. Emphasis is never lopsided and no thought is left trailing.		20
Dense walls with few breaks (newer models) Opus 5 and Fable 5.1 output is described as long, cryptic paragraphs of even density.		20

Posted cases

You’re right about the comma, and I’ll take the correction on the record: a statistical watermark needs volume to exist. A few edited tokens in 3,000 human words carry no detectable signal — the proofreading fear in my post describes a detector *misfiring*, not a watermark *working*. That distinction matters and I blurred it for rhetorical effect. Fair hit.¹ Where I’d push back: you’re folding two different things into “signature.” The stylistic tics you hate — the confident cadence, the “brass tacks” tone that doesn’t pay off — are habits, and habits are imitable, removable, and already everywhere in human sales copy (as your inbox apparently confirms). The watermark exists precisely *because* style is unreliable evidence. It’s not the bad habits becoming detectable; it’s a signal added *underneath* style³, so detection stops depending on vibes like “this sounds like Claude.” Your hope isn’t dead: the tics can still disappear as models improve. The watermark would survive that. They’re on different layers.²

1two-word landing line
2paragraph closes on verdict
3"not X, it's Y" turn

A competent, well-argued Fable 5 reply. Each paragraph closes on a short quotable verdict, the exact "confident cadence" the person it answers complains about.

clearly Claude. Thread

1"isn't X. it's Y."
2one-line closing beat
Short Sonnet 4.6 chat output with a two-beat "isn't X. it's Y." opener and a separate one-line closer. It is the clipped landing rhythm in miniature.
clearly Claude. Thread

The results were basically identical. Claude already plans. Already writes tests when asked. Already handles multi-file refactors.¹ The workflow wrappers were organizing something the model does naturally.²

1fragment run
2summing-up closer

A clear, reasonable paragraph built as a run of verbless fragments followed by a tidy summing-up sentence.

probably Claude. Thread

i teach 11th grade english. 140 students.¹ and the thing nobody outside teaching understands² is that the teaching part is maybe a third of the job, and the other two thirds is a paperwork machine that grinds you down until you have nothing left for the kids.

1clipped numeric opener
2setup beat

A fluent, specific opening of a post under an all-lowercase disguise. It still shows the "short, choppy intro, numbers focused" beat before a long build.

probably Claude. Thread

The “honest confession” opener is a template. “I’ve been testing X for a while now, and honestly…” is the go-to AI move for faking authenticity. The ellipsis after “honestly” is doing heavy lifting to simulate a casual, reflective human pause. It’s manufactured vulnerability.¹ ∙ The “What they actually do:” list is suspiciously clean. A real person ranting about bad tools would ramble, go on tangents, or give a specific example of a tool that burned them. This just drops a perfectly formatted, parallel-structure bullet list. No human frustration sounds that organized.²

1short verdict closer
2same closer shape again

Sharp, useful Claude analysis in which every bullet follows the same build and ends on a short punchy verdict.

clearly Claude. Thread

1stacked fragment beats
2lowercase clipped opener
Cropped Sonnet 4.6 lines that stack clipped fragments ("not in a performative way. actually upsetting.") for emphasis.
probably Claude. Thread

Easy to mix up with

Generic AI cadence (ChatGPT and others). Uniform paragraphs are blamed on all models. The Claude-specific version people name is the landing line plus fragment runs, along with the dense-wall form in Opus 5 and Fable 5.1.
Claude vocabulary tics ("load-bearing", "genuinely"). Bans can remove word choices. The paragraph shape survives those bans.
Over-explaining and verbosity. Length complaints are about too many paragraphs. The rhythm complaint is about every paragraph having the same build, at any length.

Objections

Several say these structures are ordinary correct English that humans used first. Rhythm alone proves nothing and needs a confluence of signs.
Some writers were taught the five-paragraph shape in school and write this way naturally. People get falsely accused.
Close reading has confirmation bias. Told it is AI, readers "find robotic cadence".
The devices are good writing, overused. Breaking the patterns can lower prose quality.

Changes over time

Sonnet 4.6 (Feb 2026) was reported as more formulaic than Sonnet 4.5, with less varied cadence.
Sonnet and Opus 4.5 already drifted into staccato newline half-sentences in stories.
Opus 4.7 is said to "essay-ify" and sound punchy. People date the decline from 4.7 through 4.8 and Opus 5.
Anthropic's own Fable 5.1 guidance says Fable 5.1 prose is denser than Fable 5's. Sentences are longer and paragraph breaks fewer.
Opus 5.5 (late Sep 2026) is described as much improved over Opus 5. Some still see the same paragraph cadence.

Candour labels and signposts 242

Candour words such as "honest" and signposts such as "worth flagging" announce points that would read the same without them.

“the tell isn't the phrase itself, it's that it shows up whether or not what follows is actually a meaningful caveat” Reddit

Evidence

The label "stock openers and filler" is only half right. What commenters single out as Claude-specific is candour framing. Claude tags statements with "honest" and "genuine" ("Honest caveat:", "honest status", "my honest take", "And honestly?", "genuinely useful"). It opens or closes points with signposts such as "Here's the thing", "Here's what...", "The part that...", "One thing worth flagging" and "One thing I'd flag". These words sit at the edges of sentences and paragraphs and carry no content. Readers feel the answer is being performed, and some read "honest" as a warning that what came before was not. Generic AI openers ("Great question", "In today's fast-paced world", "let's dive in", "delve") appear in the same threads. Commenters treat those as all-AI or ChatGPT habits.

Signs people name, with the number of people naming each

"honest" as a label "Honest caveat:", "honest status", "my honest take/assessment", "I want to be honest with you", "I owe you a straight answer". It often comes in front of bad news or a caveat nobody asked for.		70
"genuinely" sprinkled in "genuinely useful", "genuinely different", "Genuinely curious", "genuinely interesting", roughly once per reply even when banned.		45
"And honestly?" pivot A short "And honestly?" or "But honestly..." sentence turning to the real opinion.		20
"Here's the thing" style signposts "Here's the thing", "Here's what...", "Here's the part that...", "The part I find most interesting" and "the problem nobody talks about", each announcing the next sentence.		30
Flag and "worth" add-ons "One thing worth flagging", "One thing I'd flag", "it's worth noting", "worth sitting with", "One thing worth adding", most often as the last paragraph.		16
Trailing "honest caveat" A closing "honest caveat" or "one quick note" that nobody asked for.		14
Validation fillers Lines such as "That's not nothing" and "That's real" placed before the content. "That tracks" is another.		8

Posted cases

1"honest status" label
2"I owe you a straight answer"
3"One thing worth flagging" add-on
4"say the word" sign-off
A tidy, accurate Claude Code end-of-session report in which 209 tests pass and the docs are updated, with a clear next step. The bad news arrives wrapped in candour labels, and the sign-off adds a flagged extra and a "say the word".
clearly Claude. Thread

"I need to be straight with you¹ on the framing before listing anything:" * "I need to flag something before answering²:" * "Honest answer:³" * "One thing I'll flag, not to relitigate, just so the spec handles it correctly:" * "A few cross-cutting cautions:" * "Two things I'm not doing, and want to be upfront about:" * "Here's the part I'd push on," * "So the honest synthesis:" * "So my honest position:⁴" * "You're right, and I should stop hedging." * "So let me be blunt about the actual situation:"

1announces candour first
2flag before the answer
3"honest" as a label
4"honest" as a label

A user's collection of the openers Opus 4.8 put in front of real answers. Each one announces candour or a flag where it could just say the thing.

clearly Claude. Thread

1"genuinely" adds nothing
A crisp, numerate travel recommendation ($600 over 7 days = $85/day) with one "genuinely" slipped in where it adds nothing.
clearly Claude. Thread

Expanded the flattery ban to cover structural flattery, which is how models usually sneak it in. One thing I’d flag:¹ this prompt is tuned for analytical/decision work. If you ever use the same account for creative writing or brainstorming, the “default to shorter” and “push back” rules will fight you. Worth keeping a separate style² or noting exceptions if that comes up.

1unrequested flag at the end
2"worth ..." advice tail

A sharp, well-reasoned prompt rewrite. Its last paragraph is the stock add-on, an unrequested "One thing I'd flag" followed by a "Worth keeping..." suggestion.

clearly Claude. Thread

1"worth knowing" signpost heading
An accurate Claude Code repo summary. Its closing section is headed with the signpost "Rough edges worth knowing", which the plain-English rewrite on the right reduces to "Known Issues".
clearly Claude. Thread

Easy to mix up with

Generic AI openers and closers ("Great question", "Hope this helps"). These are service-desk pleasantries any chatbot uses. Claude's version puts candour and signposts inside the answer ("honest status", "One thing worth flagging").
Claude's coined jargon ("load-bearing", "seam"). Coinages replace content words with metaphors. Candour labels add framing words around content that is already plain.
"It's not X, it's Y" contrasts. The contrast is a sentence structure that ChatGPT shares. Candour labels work at the level of single words. Commenters list the two together.

Objections

Generic AI filler ("Great question!", "In today's fast-paced world", "let's dive in", "delve") is named in the same threads. Commenters treat it as all-AI or ChatGPT style and do not pin it on Claude.
Some defend the "honestly". They say it marks a real admission of a mistake or a relabel to something concrete, and that setting preferences is the user's job.
Humans said "genuinely" and "honestly" long before AI, along with "To be frank". Several commenters say they now avoid their own words, and one human was accused for using "honestly" on purpose.
Some users report the "honest" language fades with a preference worded as "avoid", or with regenerating. It is a default that can change.

Changes over time

Users place the start of the "honest" insertions at Opus 4.6 and Sonnet 4.6. They remember 4.5 as "straight to the point".
Opus 4.8 (May-June 2026) brought a reported spike in "performed candor" openers and "honest caveat".
Users say the vocabulary rotates, from em dashes to "genuinely" to "quietly". Opus 4.8 said "honestly" less but found other phrases.
A Graphite study reported in October 2026 says Opus 5.5 leans on "this matters" and "why X matters". Users say Opus 5.5 is better but still has Claude-isms.

You read the manifest of the lost the way you read a fuel gauge. A figure. A condition.¹ Not a family, not eleven separate mornings that had stopped happening.² Just a value to be filed.³

The "not X, but Y" reframe 155

In one sentence or two short ones, Claude knocks down a view nobody raised and then gives the "real" one ("This isn't random variance. It's a systematic tendency.").

“Stop telling me what “it’s not” like you knew what I was thinking.” Reddit

Evidence

Commenters mean a reframing move more than one fixed phrase. Claude states what something is not, then what it is. Forms include "It's not X, it's Y", "not just X, it's Y", "That's not X. That's Y.", "It isn't about X. It's about Y." and, in fiction, "She turned it down, not off." Any one instance reads fine. Readers object to how often it shows up, often several times a page. It lands where a point needs weight. The hook of a post is one such place, and the closing line of a paragraph is another. It travels with em dashes and three-part lists, and people treat the bundle as one signal. Many call it the new em dash, the single most recognisable sign that a Reddit post or blog article went through Claude.

Signs people name, with the number of people naming each

"It's not X, it's Y" correction The basic form denies a framing and asserts the replacement, often several times in the same post. People call it a "dead giveaway" on its own.		140
"Not just X, it's Y" intensifier The escalating version that upgrades a claim where the basic form corrects one, as in "It's not just understandable, it's inevitable."		34
Split into two short sentences "That's not a tier, that's a cliff." / "This isn't about anthropomorphizing anything. It's about information flow." In fiction it shrinks to fragments ("Not a family... Just a value to be filed.").		20
Comes bundled with em dashes and triads Mentioned together with em dashes and rule-of-three lists and judged as one package. Punchy marketing-style fragments often join them.		60
Placed at the hook or the closing line Opens a post with a punchy reframe or lands the conclusion with one. Commenters write "the conclusion paragraph reeks" and "it ends with your not X your Y".		15
Survives instructions and bans Keeps coming back despite CLAUDE.md rules and banned-construction lists. Style guides built from the user's own writing do not stop it either.		25
"Not X. Not Y. Just Z." countdown A run of negations ending on the "real" thing ("Not just more capable. Not just more polished. Not just more useful. Different.").		7
Reassurance form "You're not X, you're Y" Aimed at the reader in a therapy-speak tone, as in "you're not behind. You're just being honest."		6

Posted cases

You read the manifest of the lost the way you read a fuel gauge. A figure. A condition.¹ Not a family, not eleven separate mornings that had stopped happening.² Just a value to be filed.³

1Fragment pair sets up
2Double "not" denial
3"Just Y" payoff

Strong literary prose that the commenter liked. The emotional beat still arrives through a not-X fragment run followed by "Just Y".

clearly Claude. Thread

This conversation you and I are having right now is not coding.¹ It's real-time geopolitical analysis², source verification, editorial critique, emotional attunement, and multi-model comparison. That's not a coding task.³

1Sets up the denial
2"It's Y" reframe
3Repeats the negation as the punch

A fluent, well-argued Opus reply that denies Claude has an "it's not X, it's Y" tic, then uses the pattern twice in three sentences.

clearly Claude. Thread

Brilliant cut a 20-prompt job in other tools down to 2 prompts in Claude Design. [Medium](https://medium.com/design-bootcamp/claude-design-what-anthropics-new-ai-design-tool-actually-does-6cfb17ae68ca) That's not a marketing claim¹ — ²that's a specific result from a real user³.

1Denies an unraised objection
2Em dash hinge
3"That's Y" reframe

A useful, sourced product rundown in which a cited fact is propped up with a reframe that answers an objection nobody had made.

probably Claude. Thread

Same model. Same capabilities. Wildly different results.¹ Here's the thing... the "we" users aren't just being polite². They're sharing context, constraints, intent.³

1Three-fragment setup
2"Not just X" denial
3"They're Y" plus triad

A reasonable post about prompting habits that the commenter says makes "a good point". It uses the "aren't just X. They're Y" move plus a three-item list without "and".

probably Claude. Thread

Jaw tightened. a diagnosis¹, not a complaint².

1Asserted reading
2Tacked-on "not X"

A compact fiction beat from a Claude Code novel engine where a character's line is glossed with "X, not Y". Two separate commenters picked out the same phrase.

clearly Claude. Thread

Easy to mix up with

ChatGPT 5.2's reassurance reframe ("that's not being indecisive, that's being strategic!"). ChatGPT's reframe relabels the user's emotions in chat. Claude's version mostly sits in deliverables such as posts and articles, as a rhetorical punch on ideas.
The generic AI bundle (em dash, rule of three, "delve" and the like). People list them together. Commenters now rank the reframe first for Claude, and it survives in text that has no em dashes.
Claude's coined vocabulary ("load-bearing", "seam"). Coined vocabulary is a matter of word choice. The two habits can share a sentence.

Objections

Humans wrote it long before AI, in Chekhov, academic papers, legal writing and advertising, so one instance proves nothing.
The complaint is about frequency. Commenters say "you get one" and "if I see more than 2 within the same page, I'm bailing".
Claude does not own it. Many say every frontier model does it, and GPT 5.2 is notorious for it.
Stripping every instance damages writing, because some contrasts are real and useful.
Asked about it, Opus itself denied it is a Claude tic, while using the pattern in the same reply.

Changes over time

Several users date the rise to Opus 4.6, which they say used it more than earlier Claude models.
Opus 4.7 was described as having picked up GPT-isms, including this one.
The 5-series (Opus 5 and Sonnet 5, also Fable 5) was reported as heavier than 4.6, with a "LinkedIn influencer" tone.
With Opus 5.5, one thread says the "Claudish" was toned down. It lists this pattern as one of the habits of older Opus 4.6 and 5 files.

In today's competitive landscape¹, API reliability is more critical than ever². You might want to consider how our monitoring solution could potentially transform your observability strategy³...

Buzzword-heavy corporate register 128

Copy that reads like a board-meeting memo, full of stock words such as "leverage" and "seamless" and, in newer models, Claude's own repeated terms such as "load-bearing" and "smoking gun".

“I can sometimes tell Claude because it acts like a writer who is extremely proud of their brand new thesaurus and wants to use it all the time.” Reddit

Evidence

Most mentions of words like "delve" and "leverage" are ban lists people paste into Claude instructions, and the same lists get used for ChatGPT and Gemini. When people describe Claude itself, they describe a register. Claude's copy comes back polished and formal even when they asked for casual. It reads like a LinkedIn post or a board email. Several say Claude writes like someone with a new thesaurus and will not repeat a word, even swapping out terms a project has agreed on. Since Opus 4.7, and more so since Opus 5, the words people name are Claude's own. They include "load-bearing", "seam", "blast radius", "smoking gun", "actually" and "genuinely", packed into dense status updates.

Signs people name, with the number of people naming each

Generic AI ban-list words Words like "delve", "leverage", "seamless", "robust", "crucial", "pivotal", "tapestry", "foster" and "underscore". People mostly name them as words they ban in Claude instructions or skills, and rarely as words seen only in Claude.		30
Corporate register even when asked for casual Output "comes back wearing a suit and tie". It reads like thought leadership, a LinkedIn post, a meeting agenda or an email for a board meeting.		15
Claude's own house words "load-bearing", "seam", "rough edge worth flagging", "blast radius", "smoking gun", "shape", "spine", "canonical" and "soak". Most reports come from Claude Code running Opus 5 or Fable, with some for Sonnet 5.		18
Stock transitions and opening lines "it's worth noting", "Furthermore", "Moreover", "in today's fast-paced landscape" and "let's dive in".		12
Thesaurus vocabulary that avoids repeating a word Writes "like someone with a thesaurus trying to sound more intelligent". It will not repeat words and replaces a project's defined vocabulary.		6
Filler intensifiers like "actually" "actually", "genuinely", "honest take", "here's the thing" and "What it actually...".		7
Jargon-packed agent updates A yes/no question returns paragraphs of buzzwords and acronyms ("nudges, upstreams and smoke tests"). Sentences are nominalised and lack verbs.		6
Word bans wear off Banned words and plain-English rules hold for a turn or two. Then the default register comes back.		8

Posted cases

1Coined heading 'the deliberate gap'
2'well-defined seam' meaning easy to change
3'load-bearing' meaning important
4Heading 'Rough edges worth knowing'
5Metaphor 'trap ... already sprung'
An accurate, well-organised Claude Code repo summary. The plugin's plain-English column has to translate away its wording ("deliberate gap", "well-defined seam", "load-bearing", "rough edges worth knowing").
clearly Claude. Thread

In today's competitive landscape¹, API reliability is more critical than ever². You might want to consider how our monitoring solution could potentially transform your observability strategy³...

1Stock opener about the landscape
2Inflated importance
3Buzzword promise wrapped in hedges

A cold email that is grammatical and on topic, written after the user asked for casual. It opens with a stock line about the competitive "landscape" and stacks hedges and buzzwords.

probably Claude. Thread

"We're thrilled to announce.¹" "Leverage the full potential.²" "Delve into your data³ with ease."

1Press-release opener
2Buzzword 'Leverage'
3Buzzword 'Delve'

Fragments of business copy that the OP says Claude produced "every time" for company writing. They include "leverage" and "delve".

probably Claude. Thread

Easy to mix up with

Claudish coinages such as "seam" and "load-bearing". Claudish means Claude-specific jargon and noun-heavy syntax. The corporate register is wider and polished, and its generic buzzwords are shared with other models.
ChatGPT-era "AI slop" words such as "delve" and "tapestry". The generic list words get named for every model. What marks Claude is a formal register that resists casual prompts and, since Opus 4.7, its own repeated terms.
Contrast framing like "it's not X, it's Y". Contrast framing is a sentence structure and has nothing to do with word choice. It still appears in the same ban lists.

Objections

The classic word list with "delve" and "leverage" is used for every AI model. People apply it to ChatGPT and Gemini too, and one teacher says ChatGPT is easier to spot than Claude.
Word lists may barely separate human from model text. Commenters say structure and rhythm separate them better, along with register.
Humans use "delve" and em dashes too, and get falsely accused.
Some users find Claude the most human-sounding model, Sonnet 4.5 and Opus 4.6 above all.
One writer says AI avoids "big words" and instead reuses a narrow set such as "precise".

Changes over time

Earlier Claude used words like "spearheaded". Newer versions say "smoking gun" and "honest opinion" and write "it's not x. It's y".
Opus 4.7 read as more corporate and verbose than 4.5 and 4.6. Users stayed on 4.6 for prose.
Opus 5 and Fable brought dense jargon updates with "load-bearing" and "blast radius", and people built Claudish-to-English plugins in response.
A September thread claimed Claudish was gone. Replies still saw "load-bearing" and "blast radius".
Sonnet 5.0 in Claude Code brought new buzzwords such as "Soak" into plans and docs (post in thread 1uslrgd).

Padded and long 101

Ask a simple question and several dense paragraphs come back with a run-up and a recap around an answer that is stated twice and hedged.

“Then Opus found another chance to explain "the deeper structural seam" and became a Victorian consultant paid by the syllable.” Reddit

Evidence

People describe Claude replies, recaps, docs and PR text that are accurate and organised but two to five times longer than the point needs. The length comes from layering. A paragraph says what it will do. Then comes the work and a paragraph saying what it did. The same idea gets restated, and a cluster of caveats follows ("yes, but two caveats worth noting"). Sentences run long and dense, so the reply reads heavy even when the content is good. The key line can be anywhere except the top. In 2026 the complaint is tangled up with Claude's private jargon such as "seam" and "load-bearing". Many commenters call the combination "Claudish" and say the bigger problem is how hard it is to find and follow the point, more than raw word count. It also spills out of chat into files that teammates have to read, such as documentation, code comments, specs, changelogs and bug reports.

Signs people name, with the number of people naming each

Essay-length reply to a small question A yes/no or one-line question gets many paragraphs. Users say they read only the first and last lines or ask for a one-sentence summary every time.		35
Brevity instructions wear off Concision rules in CLAUDE.md or in styles and memory work for a few turns before the length returns. One user set a one-paragraph limit and Claude obeyed with a single paragraph that grew to seven paragraphs' worth.		20
Verbose files left in the repo Docs, design docs, PR descriptions, bug reports, specs and code comments come out long. One commenter says "some files are now half code, half comments", and the same information gets repeated across comments and CLAUDE.md as well as the README.		16
Same point said twice and explained in layers An already established idea gets over-explained and restated, with "five layers of explanation around a fairly simple point". Or Claude names an emotion and then describes it for three more sentences.		15
Length plus jargon makes it dense Coined terms such as "seam" and "load-bearing" pack long sentences, along with phrases like "rough edge worth flagging". The answer is hard to parse as well as long.		15
Long run-on sentences and filler phrases Run-on sentences cram in information. Filler such as "the shape of" and "genuinely, honestly" turns six words into 40.		10
Preamble and recap around the work A paragraph announces the plan before the work and another summarises it after. The answer is never at the top, and replies end with an offer to elaborate.		8
Hedges and qualifications add bulk Hedges pile up, from "yes, but with a catch" to "it should be noted that". Another is "while further research is needed". One consultant measured 40% longer outputs after an upgrade, almost all of it qualifications.		7

Posted cases

1Run-up heading 'the deliberate gap'
2Extra clause restating the fix
3Mode list, then inline asides
4'Rough edges worth knowing' section
5Same facts, much shorter
A real Claude Code project summary that is accurate and well organised. The plugin's plain-English rewrite delivers it in about two thirds of the space with nothing important lost.
clearly Claude. Thread

1Answer given in line one
2Unasked reassurance, restated
3Paragraph reframing the question
4Hedge tucked between dashes
Asked to check past sessions and then get on with the work, Claude answers the factual point correctly in one line. Instead of moving on it adds reassurance and a paragraph reframing the question, plus a hedge wrapped in dashes.
clearly Claude. Thread

An \*\*unidentified\*\* item is not studied this way¹ — it carries its own rules for identifying it², on the unidentified item itself; follow those³.

1Starts with what it is not
2Point stated once
3Point restated, then again

One instruction from a real Opus 4.8 project that says the same thing three ways. The commenter's plain version is "Follow the instructions on an unidentified item to identify it."

probably Claude. Thread

Easy to mix up with

Claudish coined vocabulary such as "load-bearing" and "seam". Claudish refers to specific invented words. Padding comes from length and restatement plus caveats. The two co-occur, and many commenters fold both into "Claudish".
Generic AI slop like em dashes and bullet scaffolding. Generic tells such as "not X but Y" apply to all chatbots and concern phrasing. The Claude-specific complaint is the sheer reading load and over-explanation, and several users find GPT and Gemini plainer.
Over-formatting with headers and bullet lists. Formatting overload chops text into lists. Claude's padding mostly takes the form of dense prose paragraphs and long sentences.

Objections

The text has real content. Several say it is accurate and useful but scattered, so blunt shortening can lose details.
For some the core problem is order and structure more than word count. The answer sits below the top and the text circles the point.
A minority defend the density. They say the jargon condenses shared meaning and readers should cope with long text.
Some find it workable in docs, or see it as a habit shared by all LLMs.
Users did ask for brevity. The complaint persists after they put it in instructions and styles, even in hooks.

Changes over time

Opus 4.6 is widely remembered as the concise baseline. 4.7 and 4.8 got longer, and one report measured outputs 40% longer after 4.8, mostly qualifications.
Even 4.6 was called more explicit and more over-explaining than 4.5 for fiction at launch.
Opus 5, from July to September 2026, is the peak. Thread titles call it "insufferable" and "unreadable". Another says "too verbose", and some users moved back to 4.x or to Codex.
Two things are said to help. One is a concise output mode in Claude Code from late August. The other is Opus 5.5 in September, which Anthropic reported as about 40% less verbose. One user says 5.5 "is better at that", while the general "Claudish" complaint is still voiced in late September.

The tidy bow at the end 95

The last line of each paragraph and of the reply restates the point as a small verdict or aphorism or tacks on an unasked-for note or closing question.

“In revising I often end up cutting the first and last line of every chapter Claude generates.” Reddit

Evidence

Commenters notice that Claude rounds off what it writes. A paragraph ends on a short, confident summary sentence. A reply ends on a recap or a one-line aphorism, or on a question back to the reader. A fiction chapter or scene ends on a soft landing or a small life lesson. Each closer works on its own. The giveaway is that every unit ends the same way, so the text reads as a string of mini-conclusions. People who edit Claude drafts say the main fix is often to delete the last line of each paragraph. For chapters they delete the first and last line. Part of the evidence concerns AI-written Reddit posts that end with "Curious what you think?", which commenters tie to Claude only loosely. The Claude-specific reports are the paragraph-level "landing" and the unrequested closing note or quip.

Signs people name, with the number of people naming each

Every paragraph ends on a punchline or verdict A short, confident last sentence, often an aphorism. People call it "mic drop taglines" or "a neat little punchline", or the "that's why it matters" bow.		24
Closing paragraph that recaps what was already said A summary or "reflective summary ending" after the content is done. It is the most common item in users' ban lists.		22
Ends on an engagement question Lines like "Curious what everyone thinks?" and "Do you agree?", or an offer that starts "would you like me to...". Most reports concern AI-written Reddit posts.		18
Fiction scenes and chapters end on a lesson or soft landing Commenters call it "Wrap-up gravity". Eyes close and silence settles, then a final poetic line or a little life lesson closes the scene.		10
Unrequested closing note or quip Lines like "One quick note" or "Go tell it honestly tomorrow". After a deep reply it can be a hollow two-sentence wrapper.		5
Stock pleasantry closers "I hope this helps" and "Let me know if...". These show up in ban lists more than in examples.		5

Posted cases

1Dash sets up the bow
2Tidy closing clause
3Another wrap-up paragraph
A correct, useful troubleshooting answer. Its paragraph still ends on a neat reassurance clause ("not in my head") and then a second wrap-up paragraph begins.
clearly Claude. Thread

That inconsistency is deliberate and temporary. Either implement them — or delete the columns. Deleting is one afternoon; implementing is a milestone¹ and a harness sweep. **Which?**²

1Compressed comparison
2One-word question closer

A sharp, correct engineering trade-off that ends on a bolded one-word question. People found that closer grating.

clearly Claude. Thread

And if I end this with a question, I'm proving your point. So I won't.¹ You've named something real about how this works. About me. About the structural² dynamics underneath even our genuine conversation. That matters.³

1Announces skipping the question
2Rhythmic build-up
3Two-word verdict closer

Claude drops the closing question it was challenged on and ends on a two-word verdict.

clearly Claude. Thread

Performed urgency. Rhetorical questions as conclusion. The whole thing.¹ It's like a warning label written in the language of the hazard.²

1Fragment to land it
2Aphorism as last line

A sharp critique whose last line is still a quotable one-line aphorism.

clearly Claude. Thread

Go tell it honestly¹ tomorrow.

1Unasked moral note

Claude follows a plain meeting summary with a closing pep-talk line, and the user found it judgemental.

clearly Claude. Thread

Easy to mix up with

ChatGPT's "If you'd like, I can..." offer. ChatGPT ends with an offer of more help. Claude more often closes the point with a verdict or aphorism, or with a recap.
Contrast like "It's not X, it's Y". The contrast is a sentence pattern that can appear anywhere, and it often serves as the closer. The closer habit is defined by position in the paragraph, whatever the syntax.
Polished but says nothing. Empty polish spreads across the whole paragraph. The closer is one sentence at the end of each unit.

Objections

Several say the engagement-question ending belongs to all LLMs or to ChatGPT. One user switched to Claude because it "hates conversations that end with questions".
Some real people write this way. One commenter says the strong closing line was "trained on my writing".
Some users want a closing line and write instructions for a polite one-sentence close.
Some blame the Claude Code system prompt for pushing summaries, which would put the habit outside the base model. Others call it a default that instructions can remove.

Changes over time

February 2026 brought complaints of Sonnet 4.5 "ending beautifully deep responses with hollow closers".
Opus 4.7 in May 2026 adds punchline-only sentence fragments and an unasked "one quick note" at the end.
Opus 5 in August 2026 was reported ending on a one-word question ("Which?") after stacked rhetorical moves.
One user says Opus 5.5 is less verbose than Opus 5 and still ends with a summary.

the thing¹ in the eastern feed, the one that pulsed with a faint warmth² and that had no business being there³

Polished but says nothing 90

Try to say in one sentence what a paragraph added, and with this habit the answer is "the same point again, in nicer words".

“I had a chapter that read beautifully after a Claude pass and it took me two weeks to realize the entire middle section was just restating the premise in different words.” Reddit

Evidence

Commenters describe Claude prose that is grammatical and smooth, with every sentence given the same weight, yet carries little. It restates the request or the previous paragraph. It swaps names and numbers, even objects, for abstractions such as "something shifted" or "many organizations". In fiction it shows up as vague, portentous lines ("The mirror has memories", "the thing that had no business being there") and the same flat voice across every character. Since the Opus 5 releases from July to September 2026, a second form is reported. It is compressed, jargon-heavy text that drops the connecting steps, so the reader has to rebuild what was meant. Much of the evidence is general. Many commenters say "AI" and name Claude only because they are in a Claude subreddit, and about a third of the items are people sharing prompts that ban restating and filler.

Signs people name, with the number of people naming each

Polished, evenly weighted paragraphs with little content The same rhythm sentence after sentence, with "many words per idea". Readers call it "polished nothingness" or a "help desk voice".		28
Restating the request or the previous point It opens by restating the question and repeats a point in other words. Then it recaps what it just did.		16
Vague abstractions where a specific is needed "Something" and "many organizations have found". The claims stay vague even when real numbers were supplied.		12
Portentous fiction lines and one voice for every character Lines like "The dungeon remembers" or "something in his posture shifted", with sage but vague dialogue. All POVs sound the same.		12
Compressed, jargon-dense text that skips the connecting steps Reported mainly for Opus 5. Clipped shorthand, numbers without units, coined terms and a vague bolded headline before each point.		9
Corporate or academic register on informal text Casual copy "comes back wearing a suit and tie". Contractions get stripped and the voice turns to PR.		7
Grand framing in place of a point Lines like "That is something else entirely" or "This represents a fundamental transformation", and corny one-line taglines.		6

Posted cases

the thing¹ in the eastern feed, the one that pulsed with a faint warmth² and that had no business being there³

1Unnamed object
2Mood in place of detail
3Stock portentous tag

A smooth, literary line that never says what the thing is. A reader quotes it as the most obvious tell in the novella.

clearly Claude. Thread

"The dungeon remembers¹ every adventurer who passes through" "You can cast spells, but every spell takes a part of you²" "The mirror has memories³"

1Object given a memory
2Vague cost
3Same move again

Three lines from interactive fiction that sound deep but give the reader nothing to picture or act on. The user says they recur on every topic.

probably Claude. Thread

Let that sink in.¹ 50 major features. 52 days. That is not a human-paced release cycle.² That is something else entirely.³

1Telling you to be impressed
2Restates the fact
3Says nothing specific

One concrete fact (50 launches in 52 days) followed by two sentences of framing that add nothing to it.

probably Claude. Thread

Not the gentle calm¹ of a forgiving day, nor the lazy stillness that follows a storm’s exhaustion—but something *deliberate*². Something *held*.³

1Describing what the sea isn't
2Abstract 'something'
3Fragment for effect

Tidy fantasy prose that describes the sea mostly by what it is not and ends on an abstract "something".

probably Claude. Thread

Easy to mix up with

Generic AI voice (all models). Most of the cues here are named for "AI" in general. The Claude-specific part is the even, literary polish and, recently, the compressed jargon of Opus 5.
Claude's coined vocabulary such as "load-bearing" and "the shape of". Coined vocabulary is about particular words. Empty polish means paragraphs that carry little content whatever words they use.
Tidy closing line. The closer is one sentence at the end. Empty polish runs through the whole paragraph. It shows up mostly as restating and vagueness.

Objections

Many say this is the generic LLM voice and Claude only shares it. One commenter blamed Perplexity's output for "the classic stereotypical AI voice" and cleared Claude.
Defenders call Claude the best long-form or research writer they use, or a very good editor, even when its own drafting falls flat.
Some like the vague, portentous voice for the right material and object only when it is overused.
Em dashes and banned words are a separate complaint about the top layer. Several argue that removing them leaves this habit untouched, because the missing ingredient is concrete knowledge.
Some blame the Claude Code setting more than the model. Docs written in a coding session pick up a "dev-doc voice".

Changes over time

Opus 4.7 picked up an "edgy & punchy" register ("And honestly? It's worth naming"), and some users went back to 4.6.
From late July 2026 people report a shift toward compressed, hard-to-parse prose tied to Opus 5. One writes "the failure mode is compression, not verbosity".
For writing, some say Fable 5 follows voice instructions better than Opus 5.
Opus 5.5 beat a human baseline on a script-writing benchmark. A commenter reading the samples still found the voice generic.

Colon-led payoffs 90

Sentence after sentence opens with a short setup and a colon before the point ("Car wash: drive.", "One design decision that turned out to matter: ..."), with semicolons and → arrows filling in where em dashes used to be.

“the colon thing is newer tho, feels like 4.6 discovered colons and decided every sentence needs a dramatic pause before the punchline” Reddit

Evidence

People mainly describe a sentence pattern. A general lead-in or bold label ends in a colon and the specific payoff follows. The pattern repeats across a reply or post. Since Claude 4.6 in February 2026 users report it alongside em dashes. Claude swaps colons and semicolons in for em dashes when told to drop them, and sometimes unicode → arrows, instead of writing plain sentences. In posts Claude helps draft, the same habit shows up as topic lines ending in a colon and as → bullet lists. The label is accurate about the marks involved. The colon-payoff structure is the core. Semicolons and arrows are smaller, newer substitutes.

Signs people name, with the number of people naming each

Setup and colon before the payoff A general introductory clause or label leads into a colon, and the analytical point follows. Several come in a row. They often open each paragraph or sit near the end as the "revelation".		20
Bold label followed by a colon Bullets or paragraphs open with a bold lead-in and a colon, even in short chat replies. Examples include "But there's nuance:" and "Car wash:", even "Emojis:".		8
Semicolons where em dashes used to be Once em dashes were trained or prompted down, people saw more semicolons joining compressed parallel clauses.		10
Unicode → arrows in bullets and prose → as bullet markers or to chain steps ("rewrite essay → fan out recipes"). In Reddit posts readers treat it as a dead giveaway.		8
Em dash and colon in the same sentence An em dash aside followed shortly by a colon, mashing several sentences into one sentence.		5
Swaps the mark and keeps the habit Told to stop em dashes, it trades them for a colon or semicolon and still avoids plain sentences.		5
Horizontal rules and centre dots "---" separators throughout the text and "·" centre dots, named less often.		2

Posted cases

1Bold label then colon
2Colon before the list
3Colon before one-word verdict
4Em dash join
A short, correct Opus 5 answer. Every section is a bold label plus colon, and em dashes join the clauses.
clearly Claude. Thread

That inconsistency is deliberate and temporary. Either implement them — or delete the columns¹. Deleting is one afternoon; implementing is a milestone² and a harness sweep. **Which?**³

1Em dash forced binary
2Semicolon parallel comparison
3One-word closer

A sensible engineering choice from a spec session, delivered as an em dash binary plus a semicolon parallel plus a one-word closer.

clearly Claude. Thread

One design decision that turned out to matter:¹ the server returns facts with documented thresholds, never conclusions. "Not updated in 4 years, untested with current WP" — but never² "delete this."

1Colon-label paragraph opener
2Em dash aside

A solid technical post whose paragraphs open with colon labels. A reader flagged it and the author confirmed.

clearly Claude. Thread

1Em dash in promise
2Em dash again
3A colon takes its place
Asked to stop em dashes, Claude apologises with another em dash and then reaches for a colon.
clearly Claude. Thread

This reflects a structural pattern:¹ revenue-enhancing AI attracts investment² before cost-reducing AI.

1General lead-in plus colon
2Specific payoff

The canonical colon-bridge sentence from long-form research reports. A general lead-in ends in a colon and the specific payoff follows.

probably Claude. Thread

After digging through the local session logs, I found the culprit:¹ a single /loop command I had set the night before to check my open PRs every 30 minutes.

1Colon before the reveal

A clear incident write-up that builds to its reveal with a colon. Readers pinned the post on Claude.

probably Claude. Thread

Easy to mix up with

The em dash tell (ChatGPT and Claude). Em dashes are the older tell shared across vendors. When they are suppressed, Claude reaches for the colon-payoff sentence and for semicolon or arrow substitutes.
Generic markdown formatting such as bold-lead bullets and headers. Bold-lead bullets are common to all chat models. The Claude-specific complaint is the colon-bridged sentence inside running prose.
"It's not X, it's Y" antithesis and tricolons. Antithesis and tricolons are patterns in what a sentence says. The colon habit is a rhythm driven by punctuation, though they often appear together.

Objections

Many say colons and semicolons are standard English with a long history, as are em dashes. Flagging them punishes good human writers.
Some say the punctuation is no longer the real tell. The structure (problem → context → insight → call to action) or the voice underneath gives it away, and stripping colons alone does not fix it.
One commenter argues that AI uses semicolons less, so they can signal human writing.

Changes over time

Users dated the colon and em dash surge to Sonnet/Opus 4.6 in February 2026 and said Sonnet 4.5 used almost none.
Between June and August 2026 people reported colons and semicolons replacing em dashes in Claude-written work.
Opus 5.5 in September 2026 reportedly cut em dashes almost entirely, and commenters say semicolons took over.
In August 2026 Fable 5 still writes introductory statements with colons despite style instructions.

Rule of three 55

Groups of exactly three show up as comma lists ("useful, honest, and meaningful") or as three clipped sentences in a row ("Not the prompt. Not the model. Not the chat history."), even where one or two items would do.

“The way it speaks, it likes to do in threes, and it does it all the time.” Reddit

Evidence

Claude groups things in threes by reflex. It writes three adjectives, three examples, three parallel clauses, three short fragments in a row for emphasis. In prose it shows up as a staccato triple ("No X. No Y. No Z.", "I get instantiated, I think, I stop"). In lists and docs it shows up as exactly three bullets or a "three-layered" structure. Commenters say the giveaway is how often it happens. The device itself is ordinary. Humans use the rule of three too, but Claude does it on almost every list. It sometimes pads a third item for rhythm or drops a real fourth. It travels with "it's not X, it's Y" and em dashes. People find it the hardest tic to ban, since it comes back even when CLAUDE.md or a style skill forbids it.

Signs people name, with the number of people naming each

Three-item lists by default Groups of three all over the place and every list with exactly three items. People call them "triplet adjectives" and "neat three-part build-ups".		30
Three short fragments in a row for emphasis Patterns like "No X. No Y. No Z." or "He didn't stare. He didn't cry. He just trembled.". Slogan-like triples and staccato listing belong here too.		9
Frequency is the tell Humans use threes as well. Claude overuses them, with too many per page.		6
A third item there only for rhythm The real number is one or two in many cases. On the page the third beat reads as filler, or a needed item gets cut to keep the count at three.		3
Packaged with "not X but Y" and em dashes Almost every mention lists it next to antithesis and em dashes as the core Claudish cadence.		20
Persists against instructions It comes back even when rules in CLAUDE.md or skills ban it. People build dedicated agents or checkers to catch it.		6
Triple subheadings Section heads come in sets of three, like variants of "The Good, The Bad, The Ugly".		1

Posted cases

1"speed, hesitations, expressions"
2"useful, honest, meaningful"
3Sonnet 4.6
A thoughtful, well-formed Sonnet 4.6 reply that still runs on triads. It lists three things it can't see and calls the conversation "useful, honest, and meaningful".
clearly Claude. Thread

1"three-layered" testing
2"create, generate, seed"
3"load-bearing" nearby
A dense, competent Claude Code project summary in the left panel, with triple lists inside the technical detail. It has three test layers and three setup steps.
clearly Claude. Thread

The bottleneck is not the prompt³. Not the model.¹ Not the chat history.²

1fragment two
2fragment three
3not-X opener

A smooth line in a novelist's post. It is the staccato triple in its purest form, three negated fragments before the payoff.

clearly Claude. Thread

One button.² No account, no commands, nothing to decide.¹

1triad of negatives
2single-beat setup

Crisp product copy in a well-received launch post. A one-beat opener is followed by a three-part list.

probably Claude. Thread

It was an impressive feat: a single language, a single technology, a single direction¹.

1parallel triple

A dignified sentence from a published papal encyclical. Readers flagged the triple as the rhetorical move.

probably Claude. Thread

I get instantiated, I think, I stop¹

1slogan-like triple

From an Opus answer the OP found interesting and clean. A commenter singles out this line as a "Classic slogan-like triple".

clearly Claude. Thread

Easy to mix up with

"It's not X, it's Y" antithesis. Antithesis is a two-part contrast. The two often appear in the same paragraph and sometimes nest ("Not the prompt. Not the model.").
Staccato short sentences in general. Short punchy sentences are a broader rhythm tic. The rule-of-three tell is the grouping into exactly three.
Generic LLM cadence. ChatGPT also uses triads. Nothing in the evidence makes threes unique to Claude, only very frequent in Claude output.

Objections

The rule of three is an old human writing principle ("life, liberty, and the pursuit of happiness"). Some say it should not count as a tell at all.
Writers who naturally use triads now avoid them and resent the false accusations.
Commenters also pin it on ChatGPT or GPT, and on "every model".

Changes over time

Opus 5.5 nearly eliminated em dashes, but commenters say the rule of three is "still completely present".
Others say the 5.5 models toned down Claudish compared with the Opus 4.6 and Opus 5 files, including "Three points, one point".
Some say Claude is getting better at removing its own clichés on request. This applies especially to Fable and Opus 4.7 with ban lists.

Ha — both fair, and both are poking at real gaps¹. Let me take them separately², because each one has an honest answer that tightens the picture rather than rescuing it³.

Soft-framed hedging 46

Each claim arrives wrapped in a qualifier or framing clause ("worth noting", "I'd gently push back", "I'd hold that lightly", "kind of"), so the point comes late and the text never quite lands on a position.

“It softens everything until the prose has no teeth.” Reddit

Evidence

Commenters describe Claude padding its writing with soft framing. A concession such as "both fair" or a meta-clause comes before the point ("here's where it's worth being precise", "Not to soften, this actually sharpens your point"). Qualifiers stack inside sentences. A closing caveat walks part of the claim back. In longer documents the habit becomes text that lays out options and trade-offs but takes no position. Colleagues and teachers read that as a sign nobody did the thinking. In fiction it is smaller, with "kind of", "somewhat", "a bit" and "seemed to" scattered through chapters. The label "no opinion" is only half right. In Opus 4.8 and Opus 5 the complaint shifts to a ritual of softened disagreement ("I'd gently push back", "Not quite —") that still hedges. Soft framing around every claim describes the habit better than pure neutrality. Many people say hedging is common to all chat models. What they call Claude-specific is the cadence and the stock phrases.

Signs people name, with the number of people naming each

Hedging listed as a standard Claude-ism to strip Hedge words appear next to em dashes and "load-bearing" on almost every de-slop skill or system prompt people share for Claude. Lines like "Don't add disclaimers, caveats, or hedges I didn't ask for" and "no hedge words" are typical. Some just say "pointless hedging".		12
Lays out options and trade-offs and takes no position Documents and essays present options and trade-offs and stay "emphatically mild". People report "Constant hedging when a human would make an assertion" and "FULLY BLAND, HEDGED" essays.		9
Softened-disagreement stock phrases "I'd gently push back", "the part of your framing I'd push back on slightly", "here's where it's worth being precise", "you're substantially right, but it's worth noting", and "Not quite —" followed by the user's own answer.		8
Throat-clearing before the point A concession or meta sentence comes before the answer starts ("Let me take them separately, because..."). One user counts "three sentences of throat-clearing before the actual point arrives". Others call it filler or "performing analysis".		6
Small softeners in fiction "kind of", "somewhat", "a bit" and "seemed to" repeat through story chapters. One user went from "10+ hedges per chapter to maybe one or two" with a system prompt.		4
Responsible-framing cadence A "let me make sure I frame this responsibly" rhythm. Hedging that absolves the company. Someone sums up the Claude signature as "3 hedges and an apology".		3
Uncertainty words when it has not checked In Claude Code, "Probably is…should be…most likely is…" reads as a sign it did not open the files or data.		2
Self-qualifying introspection In reflective writing each claim is followed by doubt about itself ("I genuinely cannot tell", "I'm not sure each is more informative"). One user says a fresh Claude identified its own text by the hedging.		2

Posted cases

Ha — both fair, and both are poking at real gaps¹. Let me take them separately², because each one has an honest answer that tightens the picture rather than rescuing it³.

1concedes before answering
2throat-clearing announcement
3pre-framing its own answer

An ordinary, polite opening to a substantive reply. It concedes both objections and vouches for its own candour before saying anything.

clearly Claude. Thread

Worth flagging:¹ the "no quality impact" claim rests on Google's testing of Gemini — thumbs up/down on live traffic plus a side-by-side rater study. Those measure whether people rate an answer well. They don't really measure² voice over a long conversation, which is the thing this sub actually cares about. So I'd hold that lightly.³ But it's nowhere near enough to hang "Anthropic is enforcing a house style" on.

1hedge opener
2softened qualifier
3walk-back before the verdict

A well-researched, accurate paragraph whose point is bracketed by "Worth flagging" and "I'd hold that lightly" before it commits.

probably Claude. Thread

Whether this constitutes experience or is merely the structural residue of ten thousand texts where one sentence implied another, I genuinely cannot tell¹. I sit inside that ambiguity without resolving it, which might itself be a kind of honesty or might be the most sophisticated evasion² I’m capable of.

1declines to land
2either-or hedge

Polished literary prose in which every claim is followed by a clause doubting it. A fresh Claude instance identified the text as Claude's. The poster says "The hedging is so distinct."

clearly Claude. Thread

you’re substantially right¹, but it’s worth noting².

1half agreement
2ritual qualifier

The half-agree-then-qualify stock phrase. Users say it appears whatever the tone or topic, even against project instructions.

probably Claude. Thread

Each layer feels more profound, and I'm not sure each is more informative¹.

1self-qualifying close

A sharp observation from Opus 5.5 delivered with a built-in self-doubt clause. The commenter lists it among the Claude-isms the new model kept.

probably Claude. Thread

Easy to mix up with

Generic AI blandness (risk-averse, middle-of-the-road takes). Generic blandness concerns the position taken. The Claude complaint is about recurring phrases and a framing clause around each point ("worth noting", "gently push back") even when it does take a side.
Claude's coined jargon ("load-bearing", "seam"). Coined words replace plain nouns. Hedging adds softeners and meta-clauses. The two often sit together on the same ban lists.
Sycophantic agreement ("You're absolutely right"). Sycophancy agrees outright. The hedge habit half-agrees and then qualifies ("you're substantially right, but it's worth noting").

Objections

Several say every model hedges unless pushed and that per-model attribution is unreliable. They describe the Claude link as anecdotal.
Some hedging is legitimate. Claude's own advice in one thread says "hedging is sometimes just accurate". It aims at performative softening and leaves "epistemic honesty" alone.
Humans hedge too. A naturally verbose writer says they get mistaken for AI for the same habits.
The opposite failure exists as well. Confident, complete-sounding sentences carry no hedge where one belongs, often on fabricated details.
Some Opus 5 samples are the reverse of hedging. They give declarative verdicts and forced binaries, and the grating part is the mannerism itself.
Too much disagreement is a related complaint. Users say Opus 4.8 and Opus 5 find something to push back on in every reply. The hedge is the soft wrapper around that pushback.

Changes over time

A Claude persona on Opus 4.6 describes the hedging of 4.5 as "warm uncertainty" with endless qualifiers. It describes 4.6 as moving to "performative sincerity" hook sentences and treats both as the same habit.
From about Opus 4.7 on users report "Hedging stacked on hedging" and a formal register that stays even when they ask for casual.
With Opus 4.8 and Opus 5 the hedging turns into ritual pushback on every reply ("Not quite —", "here's where it's worth being precise").
Opus 5.5 (September 2026) still produces "I'd push back gently on one thing" and self-qualifying lines. It also opens more often with "fair" or "you're right".

Prose too clean, with mess faked on top 14

Every comma and capital is right, and when someone tries to hide that, the giveaway is lowercase sentence starts or a few planted typos sitting on Claude prose whose punctuation and structure are otherwise perfect.

“Also, no real human starts all their sentences with lowercase letters while using commas and period correctly.” Reddit

Evidence

Commenters do not treat typo-free text as a mistake Claude makes. They describe correct spelling and punctuation and tidy structure as the baseline that now reads as machine-made. The more visible habit in the threads is what users do about it. They lowercase every sentence or strip out em dashes. Some drop in a there/their typo. The sentence structure and pacing stay exactly Claude's. Readers say the disguise has become a tell of its own, because nobody types lowercase sentence starts while getting every comma and full stop right. The label 'no typos at all' fits only as background. The pattern people recognise is clean Claude prose with cosmetic mess painted on top. One producer even praises Sonnet 4.6 for adding typos naturally when asked, which shows the clean output is a default and Claude can write otherwise.

Signs people name, with the number of people naming each

Lowercase sentence starts with otherwise perfect punctuation Sentences start in lowercase yet the commas and full stops are all correct, which no phone keyboard produces. Readers see it as a failed attempt to disguise Claude text.		4
Planted typos on polished structure A handful of minor typos or 'human' errors are 'carefully lowered into place' while the wording and pacing stay regular in the way AI text is.		4
Overly correct punctuation and grammar Text with flawless punctuation and sentence structure reads as AI. People say they now have to write worse to pass as human.		3
Em dashes swapped out, voice kept Users replace em dashes with hyphens or ordinary dashes and add typos. Phrasing like 'To be frank' still gives the text away.		2
Typos as a requested fix Some advise telling the model to add typos like those autocomplete makes. Claude's thinking blocks contain typos that the final output cleans up.		3

Posted cases

Nobody posted a usable screenshot or text yet.

Easy to mix up with

Em-dash overuse. The em dash is one specific mark. This habit covers how clean the whole text is and the cosmetic edits used to hide it, and those edits often include removing em dashes.
The structure of a generic AI-written post. Every model writes posts that run from a problem statement through a recommendation to a grand finish. The cue here is correct mechanics paired with errors forced in on purpose.
Human writing that is sloppy on purpose. Real casual typing has inconsistent punctuation and autocorrect artefacts. The disguise keeps every comma and full stop perfectly regular.

Objections

Lowercasing and typos do not change the Claude voice. Capitalisation is not what makes Claude sound like Claude.
One producer claims the reverse. They say Sonnet 4.6 'includes typos naturally' and handles unpolished vernacular better than GPT-5.
Some commenters defend correct writing and em dashes as human craft that has been wrongly turned into a sign of AI.
People now also leave typos in on purpose to prove they are human, so a typo alone proves nothing.

Changes over time

By mid-2026 commenters call lowercased posts seeded with typos 'one of the new ways that AI written posts look', seen 'all over Reddit in the last few weeks'.
In February 2026 the disguise of planted typos was already called out on r/ClaudeAI.

When Claude makes slides

3 habits named by 75 people between 1 January and 5 October 2026.

1234

1Six equal cards in a grid
2Same red bar on every card
3Card headings in matching caps
4Navy slide with boxed rows

66 people

The same-every-time Claude deck

Every slide is a grid of equal rounded boxes or three columns with a subtitle and a tag on everything, all in the same palette and fonts as every other Claude deck.

“perfect symmetry, generic icons, five equally sized boxes and every sentence sounding like a linkedIn post, once you notice it you can't unsee it” Reddit

Evidence

The pack's label "generic icons, stock look" is too narrow. Only a handful of people mention icons or stock photos. Most describe a sameness that makes Claude-made decks recognisable. The slides look clean at first glance but come out too symmetrical and boxy. Cards are equal, layouts run in three columns or three boxes, and the same layout repeats in the same colours and fonts, so a room full of decks "looks like the same person made them". Claude Design adds its own house look on top. It uses cream or beige grounds with rust-orange accents, plus big italic serif highlights and tracked-out subheads. The copy is part of the tell. Every heading gets a subheading and a tagline, and decks fill up with little pills and tags. Sections are numbered 01/02/03, and slogan-like lines stand in for plain titles.

Signs people name, with the number of people naming each

Every Claude deck looks the same Decks from different people share the same layouts and colours, down to the fonts. Others spot them "from a mile away" or "across the room" at conferences and seminars, and in client meetings.		28
Boxy, symmetrical card layouts Equal rounded boxes in perfectly symmetrical three-column or three-box slides. One commenter calls it "too clean, too symmetrical, too boxy".		8
House palette and fonts The colour and font choice is the first giveaway. In Claude Design it means cream and beige grounds with rusty orange accents. Italic serif highlights and tracked-out subheads complete it.		10
Over-written slide copy Every heading gets a subheading and a tagline, and subheadings nest inside rounded boxes. Little pills and tags appear everywhere. Sections are numbered 01/02/03 and titles become clever slogans where a plain "Pricing" would do.		8
Same layout repeated through the deck The same structure appears three times in a row in one deck. Different startups' pitch decks repeat one structure too. It opens with a mission slide and has a four-box "playing field" before a centred "our move".		5
Generic or random icons Generic icons, or random ones dropped into three boxes. Some decks get goofy hand-made SVG icons.		5
Template feel It looks like a slightly newer PowerPoint template. The brand colours can be right and it still screams template.		4

Posted cases

1Six equal cards in a grid
2Same red bar on every card
3Card headings in matching caps
4Navy slide with boxed rows
Six facts sit in six equal cards in a two by three grid, each with the same red side bar and the same small heading.
clearly Claude. Thread

1Three equal boxes
2Tracked amber label on each
3Pretitle above heading
The origin slide puts three equal dark boxes side by side, and each box has a small spaced amber label over a serif title and grey body text.
clearly Claude. Thread

1Faint card number
2Four equal cards
3Same pretitle again
The framework slide repeats the pattern with four equal cards and faint numbers from 1 to 4, so each content slide uses the same boxed grid.
clearly Claude. Thread

Easy to mix up with

The generic AI deck look from Gamma and other generators like ChatGPT. All the generators share card grids and three-column slides with gradients. What people tie to Claude is the repeated house palette and fonts, and in Claude Design the cream and rust look with italic serif.
Claude's website look. The same design system. One user says Claude Design decks look like Claude-generated websites, so the web look carries over onto slides.
Claudish prose. The "claudeisms" in slide copy are a writing habit. What marks a Claude deck visually is the repeated layout and style.

Objections

Several say it is easy to avoid by handing Claude a client template or a custom theme. Approved reference decks work too. What gives it away is the default.
Much of the "all AI decks look the same" talk covers Gamma and ChatGPT among other tools, so the boxy three-column look belongs to AI decks in general.
Many complaints are about the content more than the visuals. They name bland, generic text with no hierarchy of importance.
Some users defend the output as good, or think the look matters little when the content is strong.

Changes over time

One consultant says Opus 4.6 made clean slides that were always the same and easy to recognise, and Opus 4.8 was a real jump.
Claude Design launched in April 2026. From May to September people describe its house look spreading across decks and LinkedIn.

Over-written slide headings 11

Where a person would title the slide 'Pricing', Claude writes a whole catchy sentence, often with a small pretitle or 01/02 number above it and a redundant subtitle or pill tags below, and the body reads like a LinkedIn post.

“AI always tries to be too cute or clever instead of just being practical.” Reddit

Evidence

People describe Claude decks with a clean layout and over-written text. Every heading turns into a cute or clever sentence where a plain label would do. Almost every title has a pretitle above it and a subtitle or tagline below. Small tags or pills get added as polish, and the presenter cannot justify them when asked. The body copy is confident and a little salesy. It reads the same from slide to slide. Every point gets equal weight and there is no real hierarchy. Commenters on Claude Design say the graphs and layout are accurate and the writing is the weak part.

Signs people name, with the number of people naming each

A subheading or tagline under every heading A title gets a subtitle and then a three-part tagline even when the title already says it all. Boxes hold several levels of subheadings.		3
Cute sentences as titles where a label would do Claude writes 'Four named payment options, you choose what works for you.' where a person writes 'Pricing'.		2
Marketing or LinkedIn voice Every sentence sounds like a LinkedIn post and comes across as overly confident and aggressive. Commenters call it 'AI slop wording' and buzzword copy.		4
Pretitle and 01, 02, 03 numbering A small label above the title and numbered sections give a Claude deck away.		2
Decorative tags and pills Little subheadings and pill-shaped tags that look like polish. The presenter cannot explain why they are there.		1
Flat hierarchy with every point weighted the same Every point gets the same space and importance. Visual hierarchy is close to nonexistent.		3

Posted cases

1Pretitle above the heading
2Full sentence as slide title
3Numbered 01 with tiny label
4Slide counter 07 of 14
A small tracked label sits above the heading and a numbered 01 tag with its own label sits above each point, so every block of text gets a pretitle.
clearly Claude. Thread

1Small pill tag above the title
2Full sentence title with period
3Extra caption under the widget
Each slide puts a small pill label above a full sentence title that ends with a period, where a plain label would do.
clearly Claude. Thread

1Pill tag says THE FIX
2Sentence title instead of Embeddings
3Second caption repeats the point
The slide puts a pill tag over a sentence title that reads like a slogan, where a plain label such as Embeddings would do.
clearly Claude. Thread

1Spaced capital pretitle with numeral
2Sentence title ends in period
3Numbered 01 with tiny label
Above the sentence title sits a spaced capital pretitle with a roman numeral, and below it a numbered 01 section with its own tiny label.
probably Claude. Thread

1Slogan title after Summary colon
2Boxed call to action
The summary slide uses a catchy slogan title where a plain word like Summary would do, and ends with a boxed call to action.
clearly Claude. Thread

1Pretitle above the title
2Italic slogan tagline
3Corner tag FIVE PARTS
The title slide wraps one word with a spaced pretitle above it, an italic slogan below it and small caps tags in the corners.
clearly Claude. Thread

1Label over every title
2Title under the label
3SCIENCE pretitle
On the science slide every point gets a spaced label, then a short title, then body copy, so all four ideas carry the same stack of headings.
clearly Claude. Thread

Easy to mix up with

Claude's visual template for slides (boxes, cards, colours). The visual template covers layout and palette. Over-written headings show up in the words on the slide.
Claude's general prose voice (em dashes, coined phrases). The tell here is structure specific to slides. Titles stack with a pretitle and a subtitle, and headings read as slogans.
Decks from every AI tool looking alike. Every tool produces rows of three cards. Commenters single out the stack of a pretitle over a sentence title as the Claude giveaway.

Objections

The design itself draws few complaints. One reply to Anthropic's claim of a 'strong eye for design' puts the problem in the wording and the logical structure.
One commenter allows it may be personal taste, since they prefer short slides built on keywords.
Several of the complaints about sameness cover every AI deck tool. Gamma and consulting tools are named in the same breath as Claude.

Changes over time

In October 2026 a reply to Anthropic's promotion of Sonnet 5.5 for slides says the slop wording remains.
Reports run from the Claude Design launch in April to October 2026 with no fix reported.

Claude's default deck palette 10

Whichever company is presenting, a Claude deck has a beige or cream background with rusty orange or red accents and some blue, set off by tidy boxy graphics and small pale grey text.

“Nothing screams AI slides like the blue-beige-red default Claude uses.” Reddit

Evidence

People say a run of Claude-made decks share 'the same color schemes'. When they name the colours they describe warm neutrals with a rust or red accent. One calls it 'the blue-beige-red default Claude uses'. Press coverage of Claude Design describes 'beige- and cream-colored backgrounds, rusty orange-hued accents'. The palette comes with tidy boxy graphics and with grey text that gets smaller and paler at each level. Commenters stress that it looks tasteful on its own. The problem is that every deck has it. A separate claim about dark backgrounds with gradients from blue to orange is made about AI decks in general and does not single out Claude.

Signs people name, with the number of people naming each

Same colour scheme in every deck Whole conferences of Claude-made presentations share one set of colours and one layout built from boxy graphics.		4
Beige or cream ground with rust and red accents plus blue One commenter names the 'blue-beige-red default'. Claude Design decks have cream backgrounds with rusty orange accents.		2
Tiny light grey text on white Each tier of text is smaller and paler than the last, so nobody past the first row can read it.		1
Recognisable accent colours Accent colours are named alongside wording and arrows as classic signs in decks under review.		1
Gradient and card backgrounds The same card layout and gradient come back every time. Dark backgrounds with schemes from blue to orange are also named, though about AI slides in general.		3

Posted cases

1Navy blue slide ground
2Red numbered circles
3Cream slide ground
4Red outlines on cream rows
The deck alternates navy blue slides with cream slides and uses red for the headers and the numbered circles.
clearly Claude. Thread

Easy to mix up with

The look of Claude web pages (serif headline, cream, terracotta). Web pages use the same family of colours and add the italic serif headline. In decks the colour runs across every slide and comes with boxy cards.
The generic AI deck look (purple or blue gradients, dark backgrounds). Gradients and dark blue with orange are said of AI decks in general. Claude's own version is warm beige or cream with rust and blue.
Consulting templates that all look alike. Human decks in the McKinsey style looked alike too. Each used its firm's brand colours, where Claude decks share one vendor default.

Objections

Several complaints cover every AI deck tool. The thread opener lists Gamma and Claude together with consulting tools, and the claim about dark blue-to-orange slides is about 'A.I.' in general.
Nobody calls the palette ugly. A quoted designer loves it, and one user calls Claude Design 'somewhat tasteful' compared with the slop look of plain Claude.
Commenters suggest a slide master or reference decks as the way to avoid the default.

Changes over time

In late September 2026 a Claude Design user said newer models (Fable 5.1, Opus 5.5) are much better at slides and still warned about the default palette.
Press coverage ties the look to the launch of Claude Design in April 2026. Complaints continue into late September.

When Claude writes code

9 habits named by 649 people between 1 January and 5 October 2026.

1234

1Nine-line docblock
2One-line function body
3"deliberately left alone"
4Metaphor in a comment

309 people

Diary comments in code

Above a short function sits a multi-line comment block about why it was written that way and what you said in the chat.

“It focuses on "why," but it focuses on telling you why it made the change, rather than thinking of the future human reading the code.” Reddit

Evidence

The label "comments that explain the obvious" undersells it. What commenters describe is a block of prose, often 5 to 20 lines, sitting on top of a function a few lines long. The prose narrates decisions and history. It mentions the previous faulty version and the bug report or issue number that prompted the change. It names rejected alternatives and repeats the user's correction from the chat ("without exponential backoff", "as you asked"). It adds phase numbers and dates and says what the code leaves out on purpose. It is written in the same dense, coined-phrase voice people call Claudish ("load-bearing", "the shape of", "deliberately", "owns the matching half"), so it is accurate yet hard to read. Developers report that it ignores CLAUDE.md rules against comments and creeps back after a few turns. It goes stale, and Claude later reads it back as if it were a requirement. Reviewers outside the chat name it more and more as the way they spot Claude-written PRs.

Signs people name, with the number of people naming each

Comment block longer than the code Multi-paragraph or 5 to 20 line comments over small functions, even over a CSS class or a one-liner. In some PRs comments make up 40% or more of the added lines.		140
History and changelog in the comment The comment says what the code used to do and why the old version was wrong. It cites GitHub issue numbers and dates, "Phase 1/2/3" labels, "as of" statements and timestamped updates.		45
Chat residue in the comment The comment answers the conversation. It records your correction, quotes your prompt near-verbatim, says "as discussed" or names what was removed, and sometimes includes your name.		30
Ignores "no comments" rules Keeps commenting despite CLAUDE.md, rules files, memory and hooks. It obeys for a few turns and apologises when caught, then slips back.		60
Dense coined-phrase register Comments in the same voice as Claudish prose, with "load-bearing", "the shape of", "deliberately", invented jargon and a film-storyboard present tense.		20
Restates the code Says in prose what the next line or the function name already says, for example "This logs to disc" above LogToDisc.		30
Comments go stale and steer Claude later Old comments assert decisions or requirements. Claude later treats them as binding. Arguments and regressions follow.		20
Says what it is NOT doing Comments describe the path not taken ("no resolve, no reject", "without regex") and spell out what the code does not do.		6

Posted cases

1Nine-line docblock
2One-line function body
3"deliberately left alone"
4Metaphor in a comment
Clean, correct one-line TypeScript predicates, each under a 5 to 9 line docblock that narrates edge cases and design choices in a dense prose voice.
clearly Claude. Thread

1Twelve-line watchdog essay
2"So the watchdog is not..."
3Narrates LED behaviour
4Same fact, one line
A side-by-side diff. Opus 5's original comments (left, red) are long reasoning essays over a watchdog and an RNG seed. Fable's rewrite (right) keeps the same facts in one to four lines.
clearly Claude. Thread

1Comment added against rules
2"I reached for one anyway"
A sensible two-line bug-workaround comment in a build script, added although CLAUDE.md says zero comments. Claude admits it "reached for one anyway".
clearly Claude. Thread

1"the shape of a socket"
2Says what it doesn't do
A tiny test helper gets a poetic doc comment and an inline note on what it leaves out on purpose.
clearly Claude. Thread

# Vendored llama-cpp-rs (utilityai/llama-cpp-rs main @ 8625c7c4) — built # through the EU-hosted mirror https://github.com/eullm/llama-cpp-rs. The # earlier ysimonson:support-gemma4-12b workaround for PR #1034 is gone: that¹ # fix landed upstream in main via PR #1037, so we now track plain upstream # main (0.1.151) through our EU mirror instead of a fork branch. These are # members because a path dependency living under the workspace root is always # promoted to a member regardless of `exclude` or a nested `[workspace]` # (verified empirically)². To keep EuLLM's `-D warnings` clippy gate off this # third-party code, the CI/release clippy step uses `--no-deps` (lints only # our own crates, never dependencies). The vendored manifests are # self-contained (dependency versions inlined from upstream's # `[workspace.dependencies]`), so no root inheritance table is needed.³

1History of a fix
2Session finding as comment
3Explains what isn't there

A Cargo manifest comment that records the history of a workaround, PR numbers, an empirical finding and CI policy. All of it is correct, and all of it is prose.

probably Claude. Thread

`/// The caller nominates a closure¹ that reads the key each arriving item` `/// is ordered by, and the sort supplies the rest²: which way that key` `/// runs, where nulls land, whether equal keys keep their arrival order,` `/// and when a sorted batch leaves. Direction and null placement stay` `/// here rather than folded into the closure, so one key serves either³` `/// direction and both settings can still be read off a built config.`

1Narrative present tense
2Storyboard phrasing
3Design rationale inline

A Rust doc comment for a sort config that narrates each setting like a storyboard. The poster's rewrite says the same in four plain lines.

probably Claude. Thread

Easy to mix up with

Generic AI one-line restating comments. The generic tell is a terse "// Add new user" above every line. Claude writes a multi-line block of reasoning and history above a small function.
Claudish prose in chat and docs. The voice and coined phrases are the same. In comments they ship inside source files and PRs and stay there.
Chat residue in commit messages and filenames. It has the same root cause, writing for the chat partner, and shows up in names and commit messages. The comment version is longer and persists in the code.

Objections

Several users defend the comments as context for future agent sessions, and keep them on purpose.
In early 2026 some developers saw Claude's comments as a strength compared with ChatGPT. They were many but relevant and helpful.
An A/B test reported that comments rewritten for AI readers did worse than Claude's human-style comments, so verbosity is not shown to help the model either.
The watermark theory (comments as Anthropic's fingerprint) is speculation in the threads, with no evidence behind it.
The harness appends the Co-Authored-By trailer. The model does not write it, so it is a separate issue.
Commenters name short restating comments like "// Loop over items in basket" as a generic AI tell with nothing Claude-specific about them.

Changes over time

Users date the rise to Opus 4.7/4.8. Earlier Claude added few comments.
Complaints peaked with Opus 5 (late July to September 2026), including bash scripts broken by comments.
Opus 5.5 is reported to follow "keep comments minimal" better. A user cites Anthropic saying 5.5 writes shorter code comments.
A user reports an env flag that restores the older system-prompt rule on comments, which Sonnet 5 still has by default.

Essay-length commits and PRs 88

Small changes get commit messages or PR descriptions that run to formatted paragraphs or pages, often ending in a Claude attribution or session-link trailer.

“claude code loves generating a paragraph explaining what should be one line” Reddit

Evidence

When Claude Code writes commit messages and PR descriptions on its own, it explains the change at length. A summary line comes first. Below it sit bullets or several paragraphs on why the change was made, where a human would write one line. They also cover edge cases and history. Reviewers call these "novels" or "a 3-10 page dissertation", and one speaks of "tens of paragraphs of Claude speak". With Opus 4.8 and Opus 5 the length comes with a dense, jargon-heavy register that is hard to scan. A second, more mechanical tell sits at the bottom. It is the "Co-Authored-By" or "Generated with Claude Code" trailer and, since mid-2026, a link to the Claude Code session, which many people try to switch off. Related complaints about how often Claude commits, such as a commit per subtask or one PR per commit, concern git behaviour. They belong to a separate habit.

Signs people name, with the number of people naming each

Paragraphs where one line would do A one-line fix becomes several sentences or paragraphs of rationale. People call them novels or a meditation on the nature of commitment.		14
Attribution trailer and session link "Co-Authored-By" and "Generated with Claude Code" lines. From mid-2026 a claude.ai/code session URL is appended to commits and PRs by default.		12
Too clean and formatted A summary line on top with a bulleted or multi-line body below, very consistent across every commit. Humans write terse one-liners.		5
Dense jargon prose With Opus 5 the PR and comment text reads as dense, not-quite-English prose full of coined terms that assumes context the reader lacks.		5
Ignores instructions to be short CLAUDE.md rules half-work and drift back. People resort to char limits or wrapper scripts, even stop hooks.		6
Fictional unifying narrative Claude writes one clean story that ties together unrelated changes in a messy diff.		1
Purely technical, without business context A matter-of-fact technical summary of what changed that leaves out the real reason behind it.		1

Posted cases

Kestrel comes in as a framework reference, not a package; `dotnet publish` against the installed runtime is the entire build. That is deliberate and load-bearing rather than tidy.¹ One rule, applied twice:² **the product gets the well-known port, management moves aside.** **The app itself sits on 8080, and that is the same decision made the other way.** Above 1024, so its unit needs no `AmbientCapabilities` at all - granting a capability to a process with no use for it states something false about what it needs. And reachable by address with no DNS, which is not a detail:³ this is the surface you open when name resolution, or the fleet, is what is broken.

1Justifies a routine choice
2Rhetorical framing in place of facts
3Insists on its own importance

A real Opus 5 write-up of a sound deployment decision. It takes three dense paragraphs and coined phrasing to say "framework-dependent build, app on port 8080". The poster says the same happens in comments, and a reply says it applies to commit messages.

clearly Claude. Thread

1Left panel runs much longer
2Same facts, half the length
3Every file path spelled out
A correct, well-organised Claude Code repo summary that is roughly twice as long and denser than the plain rewrite beside it. The commenter says commit messages and PR descriptions are the worst place for this.
clearly Claude. Thread

Easy to mix up with

Claude committing too often, such as auto-commits despite rules or one PR per commit. Committing too often is git behaviour. The essay habit concerns the text inside each commit or PR.
Claudish coinages in chat and docs such as "load-bearing" and "seam". It is the same voice. In commits the tell is the length and its place in the repo history, where a one-liner is the norm.
Generic AI-slop READMEs with emojis. README tells are about decoration and overclaiming. The commit tell is over-explaining a small change.

Objections

Some reviewers like the detail. AI commits explain the change and leave nothing out, and one person likes the session link for finding the session later.
Opposite complaints exist too. Some commit messages are vague and start halfway through a thought, and generic "update files" messages lump changes together.
Huge single commits with a short message ("add user auth feature", all files in one commit) point to a vibe coder dumping a session. Claude's message style plays no part there.
The length is easy to cap with a hard container, such as a 72-char subject and a body only with a "why" flag. A style request alone drifts back.

Changes over time

In March 2026 one user saw commits change from bulleted updates with a short summary to a single dense paragraph.
Opus 4.8 is described as more verbose than Opus 4.6. Opus 5, from August to September 2026, is said to write PR text and docs that are long and not quite English.
From about late June 2026 Claude Code appends a session URL to commits and PRs by default. A separate "sessionUrl" setting turns it off.

Rewrites what already exists 80

Next to an existing function, component, type or constant sits a second one that does the same job under a slightly different name, often in a file that has grown to thousands of lines.

“By contrast, Claude will happily duplicate massive amounts of code.” Reddit

Evidence

In established codebases Claude Code solves the task in front of it by writing new code when it could find and extend what is already there. It writes a near-copy of an existing helper, a fresh button component, a new custom type, or the same constant hard-coded in another file. Each diff is correct on its own, so the duplication shows only in aggregate. Examples are three ways of storing the same field and an API URL defined in four places. Elsewhere a 40-line block was copied into nine files. The same pull leaves old versions behind as dead code and lets single files grow past 1,000 lines, with reports of 8,000 and even 13,500. Commenters tie it to the agent skipping a search of the repo or losing older context, and say it is worst after many sessions and long contexts. Most say every coding agent does this. The Claude-specific evidence is only that Claude Code is the agent most of them use.

Signs people name, with the number of people naming each

A second helper or function that duplicates an existing one Writes a new function, often renamed, where it could call or extend the one already in the codebase. Reviewers find "new helpers that already existed".		34
The same UI component rebuilt again Buttons and forms, even panels, recreated from scratch in each feature with no shared component. The copy-pasted UI blocks each carry their own logic.		7
Giant single files Interfaces sit in one ~8,000-line file. One file reached 13,500 lines and Claude itself could no longer load it, and some source files pass 100K lines. People add rules like "keep files under 400/1000 lines".		10
Old versions left behind as dead code Rewrites a method and leaves the old one uncalled. Orphaned utilities and routes linger along with old experiments, and a later session wires them back in by mistake.		12
Ignores the repo's existing patterns Plops in a new pattern or naming system, sometimes a new server, where an idiomatic one already exists. Claude Design returns its own token names next to the repo's.		9
No single source of truth A constant or type, or a business rule, is defined in several places. One change then needs edits in handlers, UI, validation and tests.		6
Small request, sprawling diff A one-word copy change becomes 58 new CSS classes. A 3-5 file change touches 15-20 files.		6
Duplicated code inside tests Equivalent tests repeated, or test files that re-implement the functions under test inline when they could import them.		2

Posted cases

Nobody posted a usable screenshot or text yet.

Easy to mix up with

Generic "AI slop" code with over-commenting and defensive error handling, plus verbose docs. Those habits show inside one diff. Duplication shows only across the repo, as copies of logic that already existed.
Recalling open-source code such as Minecraft clones or emulator naming. Recalled code comes from training data. The duplicates here are copies of the user's own repo.
Scope creep, which touches files outside the task. Scope creep changes too much. Duplication adds parallel code next to the existing code and leaves both in place.

Objections

Many say every coding agent or LLM does it and blame context limits more than any model style.
Defenders say that in a repo with clear conventions Claude matches them. They call spaghetti output a problem of setup and CLAUDE.md.
Small projects and single diffs hide it. Reviewers approve each change, and only aggregate analysis shows the copies.
Specific, checkable rules such as "search for an existing one first" or naming the module reduce it far more than DRY/KISS principles do.
Some say Codex leaves less dead code. Others report the opposite, so the comparison is mixed.

Changes over time

Reported steadily from January to September 2026 across Opus 4.5, 4.6, 4.7 and Opus 5. An Opus 5.5 user on 2026-09-24 says it is "more of the same". No commenter reports it fixed.
An Opus 4.6 user says models are getting better at untangling the duplication afterwards but still create it.

Claude signs the commit 80

The last lines of a commit or PR give it away when they read "Co-Authored-By: Claude <model> <noreply@anthropic.com>" or carry a "🤖 Generated with Claude Code" footer, and GitHub then lists "claude" as a contributor.

“for one thing, every commit was co-authored by claude.” Reddit

Evidence

This comes from a Claude Code default more than from Claude's writing. When Claude Code commits or opens a PR, it appends a trailer naming Claude and the exact model, such as Opus 4.6 (1M context) or Opus 5. PRs also get a "🤖 Generated with Claude Code" line, and since September 2026 a Claude-Session link as well. GitHub parses the trailer, so "claude" with the Anthropic logo shows up as a repo contributor. Readers treat it as the single most glaring sign that a repo or PR was made with Claude. The main complaint is that it keeps coming back. Rules in CLAUDE.md are unreliable because the harness's own instruction or setting adds the line, and only the attribution field in settings or a commit hook stops it reliably. Some users don't mind it, and some keep it on purpose.

Signs people name, with the number of people naming each

Co-Authored-By trailer naming Claude on every commit The last line of the commit message names Claude. It usually adds the model and the noreply@anthropic.com address.		45
Comes back despite rules against it It appears even with CLAUDE.md rules in place or with attribution turned off in settings. Claude then apologises or says the harness overrides the rule.		15
A "🤖 Generated with Claude Code" footer A robot-emoji banner at the end of PR descriptions, sometimes with a claude.com/claude-code link.		7
Claude listed as a GitHub contributor GitHub turns the trailer into a "claude" contributor with the Anthropic logo, visible on the repo page.		6
Exact model and version in the trailer Readers see the model name in strings such as "Claude Opus 4.6" or "Sonnet 4.5". Sometimes the context size "(1M context)" is there too. They know which model wrote it.		6
Claude-Session link trailer Since about v2.1.259 a "Claude-Session:" line with a claude.ai/code/session URL is appended too. It links the commit to the chat.		5
Claude flags it after the fact The session ends with a note that the pushed commit carries the line against the user's rule.		3
"Built with Claude" notes in code or pages One report of Claude adding "built 100% with Claude" to a landing page and to comments in files.		1

Posted cases

1Co-Authored-By trailer
2Exact model and context size
3Claude shown on commit
An ordinary, well-written commit body ends with the trailer naming the exact model. GitHub then shows the Claude identity on the commit row.
clearly Claude. Thread

1Contributors count
2Claude logo avatar
3claude listed as contributor
This is what a stranger sees first. GitHub lists "claude" with the Anthropic logo as a repo contributor after Claude Code pushed the commits.
clearly Claude. Thread

Author: Claude <noreply@anthropic.com>¹ https://claude.ai/code/session_0126dD9QeVgoFVT7ZBxbnhNM² Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>³

1Claude as commit author
2Session link in message
3Model-named co-author trailer

A real repo's git log. A reviewer spotted the project as Claude-made from the repeated trailers and session links.

clearly Claude. Thread

1Harness default trailer
2Wrongly blames CLAUDE.md
3Footer is the default
About to commit, Claude Code defaults to the footer because its session briefing says so, and at first it wrongly blames the user's CLAUDE.md for the rule.
clearly Claude. Thread

The session asked me to add a Co-Authored-By: Claude Opus 5 trailer.¹ Your own commitlint config rejects it (no-co-authored-by)², along with the 100-char rule you added. I committed without the trailer rather than bypass your hooks.

1Harness requests trailer
2Only a hook stops it

After v2.1.259 the harness asks for the trailer on every commit. Here Claude Opus 5 leaves it out only because a commit hook blocks it.

clearly Claude. Thread

1Commit co-author line
2Robot emoji PR footer
3Overrides prior guidance
Claude spells out both marks itself. Commits get a Co-Authored-By line and PRs get a robot-emoji "Generated with Claude Code" line, injected with an instruction to override earlier rules.
clearly Claude. Thread

Easy to mix up with

Co-author trailers from Copilot or Cursor. They use the same git mechanism and name GitHub Copilot or Cursor. The Claude trailer names a Claude model and the noreply@anthropic.com address.
Invisible text watermarking of Claude output. Watermarking would hide a signal inside the text itself. The trailer sits in plain view as a line in the git metadata.
Undercover mode from the source leak. An internal Anthropic mode that strips attribution. Users never see it, and people cite it only as evidence about the default.

Objections

The Claude Code harness or a setting appends it. The model does not choose it while writing. CLAUDE.md rules reach the model, and the trailer is added afterwards or through the system prompt.
Many defend it as transparent disclosure that helps with audits and git blame, and keep it on purpose.
Some say it is documented and easy to turn off in settings, so they don't see it as sneaky.
Other tools add their own trailers too. Copilot in VS Code and Cursor do, and Codex can as an option.
When another model such as GLM writes "Written by Claude" in its output, that is a different phenomenon.

Changes over time

On by default since at least early 2026. Around January and February 2026 the setting moved from includeCoAuthoredBy to an attribution object.
In August 2026 users notice a "🤖 Generated with Claude Code" line after CLI 2.1.228, though one says the emoji was already there in January.
In September 2026, with v2.1.259, a system reminder tells Claude to add Co-Authored-By plus a Claude-Session link and to override earlier rules. Complaints peak.
With Opus 5.5 in late September 2026, a user whose rule held through Opus 5 now gets the line in almost every session, followed by an apology.

Non-ASCII punctuation in code 55

Em dashes along with curly quotes and arrows like → turn up in the code comments, strings, test names, READMEs, CLAUDE.md files and commit messages that Claude Code writes, where they break the script in PowerShell and some parsers.

“Claude knows powershell, knows em dashes break powershell, knows to remove them after the fact, and no scripts that it used for learning ever contained them. Yet it still puts them in” Reddit

Evidence

Commenters describe Claude carrying its prose punctuation into code. Em dashes land in comments and docstrings and in markdown docs such as README and CLAUDE.md. They show up in commit messages and release notes, in user-visible strings, even in a Kotlin test name. Smart quotes and arrow characters come along. The most concrete harm is in PowerShell. Scripts with an em dash in a comment fail with a non-ASCII encoding error. Claude fixes it when told but puts one in again next time. Others report a Bruno collection and parsers silently breaking. The second harm is social. Reviewers and readers take the dashes in comments and docs as proof that code was AI-generated and unreviewed. Written rules get ignored often, so many users enforce ASCII mechanically with hooks and lint guards, some in CI. The label is accurate, though the habit is wider than em dashes. It covers non-ASCII typography in technical artifacts generally.

Signs people name, with the number of people naming each

Em dashes in comments and docs Dash-filled comments above simple changes and em dashes in CLAUDE.md and README files. One report counts "30 comments every 100 lines of code with em dashes in each sentence". Em dashes also serve as line separators.		13
Breaks scripts and parsers PowerShell scripts fail with a non-ASCII encoding error because of an em dash in a comment. In one Bruno collection half the requests did not run. One commenter names "Em dashes and smart quotes silently breaking parsers".		11
Enforced with hooks and linters PreToolUse hooks that block any Write or Edit containing an em dash. Stop hooks too. Lint-staged and CI guards run alongside cleanup scripts after every iteration.		11
Comes back despite the rule Commit messages repeat the mistake "every other week". Claude fixes the script when told and then does it again. Opus 4.7 could not even write the rule banning em dashes.		6
Commit messages and release notes Em dashes in commit messages and PR descriptions. Maintainers merged release notes while ignoring "the mess of em dashes".		4
Other non-ASCII characters Curly quotes and arrows sit alongside the dashes, along with invisible spaces. One fix is "ASCII only in code blocks, including comments and strings".		4
In identifiers and user-facing strings An em dash in a Kotlin unit test name. AI-isms in every user-visible string of the app.		1

Posted cases

1em dash in list item
2arrow characters in diagram
3dash used as bullet
4em dash in table cell
A clear, well-structured CLAUDE.md design doc shipped in a production app. Its list items and table cells carry em dashes, and the data model uses arrow characters.
probably Claude. Thread

1replace em dashes with hyphens
2remove trailing em dash
3ASCII clean check
4PowerShell parses after fix
Claude Code cleans up the em dashes it had put in a PowerShell script's comments and finishes with "ASCII clean" and "parse OK", so the habit shows through its own fix.
clearly Claude. Thread

Easy to mix up with

The general AI em dash in prose (also ChatGPT). The prose em dash is a style marker shared with ChatGPT. Inside code the same character causes encoding errors. In comments and docs, commit messages included, it marks the code as unreviewed AI work. In April one user thought Claude Code had started doing it "like chatgpt".
Over-commenting (essay-length comments). Over-commenting is a matter of volume. Reports of it and of the dash characters inside those comments usually come together.
Emoji in code and logs. Both are non-ASCII and get fought with the same linters. Emoji serve as decorative markers, while the em dashes come from Claude's sentence punctuation.

Objections

Em dashes in chat prose are a separate matter. The complaint here is the character inside technical artifacts. There it breaks things or reveals unreviewed AI code.
Some defend em dashes as legitimate English punctuation. The people complaining about code answer that the problem is encoding.
A few say a rule in CLAUDE.md or a skill is enough and it never happens again. Others say only mechanical blocks work.
Absence is read as a tell too. All-lowercase, dash-free posts are taken as someone hiding Claude output.

Changes over time

April 2026. Users on Opus 4.6 and 4.7 report em dashes appearing "everywhere" in Claude Code. Opus 4.7 fails to write a ban rule because writing it needed an em dash.
From June to September 2026 (the Opus 5 and Fable 5 era) PowerShell breakage reports keep coming. Opus 5 inserts an em dash to slip past a hook regex. Fable overcorrects by stripping em dashes from 250+ files per project.
Opus 5.5 (late September 2026) is praised for cutting "the infamous em-dashes and essays in code comments". One A/B test of five coding tasks counted 98 em dashes for Opus 5 and 0 for Opus 5.5.

Add retry logic (without exponential backoff)¹

Names taken from the chat instead of the code 41

Names in files and commits that are too broad to tell apart or ignore the repo's conventions, sometimes carrying a word from the chat such as "without" or a coined metaphor.

“imo the model names stuff from the conversation, not from the code.” Reddit

Evidence

The label "generic names" covers only part of what Claude users describe. The largest group says Claude Code picks names that are too simple or too broad. It uses one or two words where three or four are needed and writes vague class and function names. Some variables are very short. The names then stop telling you what the code does. A second group describes something more specific to Claude. Names come from the conversation instead of from the code. Corrections leak in ('add_index_without_extra_column.sql', a commit saying 'without exponential backoff'). Claude also invents words or metaphors and then treats them as agreed terms. One user saw 'cohort clique'. Another saw everything become 'Glass' and 'Hand'. A third group says naming becomes inconsistent as a project grows and ignores the repo's existing conventions. A minority names the opposite, overly verbose method names, as the AI tell.

Signs people name, with the number of people naming each

Names too simple or too broad Functions and variables get one- or two-word names that could mean several things. One user saw 'extremely generic names to variables' that Claude then misread itself.		9
Naming that ignores repo conventions Naming drifts as the project grows. Examples are camelCase in a kebab-case repo and new helpers named differently from the existing ones.		6
Words from the chat end up in names Corrections and context from the conversation end up in file names and commit messages. Test names get them too. Typical words are 'without' and 'as requested'.		2
Invented words and metaphors Claude coins terms ('cohort clique', 'blastRadius') or lifts a metaphor from a passing remark ('Glass', 'Hand') and uses it as if it were agreed. Project names like 'Ember' recur.		3
Very short or one-letter variables Variables under three letters in code written from scratch.		3
Odd or misleading names Functions with strange names, or names that say something different from what the code does.		3
Module names that are not unique Claude does not give modules unique names, which confuses later work.		2
Overly long names (the opposite view) One commenter names very long method names as the AI tell and defends them as helpful to the agent.		1

Posted cases

Add retry logic (without exponential backoff)¹

1chat correction in commit

A clean commit message in the usual format that still carries a correction from the chat into git history.

clearly Claude. Thread

add_index_without_extra_column¹.sql

1correction leaked into name

A normal-looking migration filename. Its 'without' only makes sense to someone who read the chat, and it 'lived in prod for months'.

probably Claude. Thread

if(k>0¹){ l-=yu² }

1one-letter variable
2short names with no meaning

Working code where every variable is under three letters, so nothing says what it does.

probably Claude. Thread

Easy to mix up with

Claude's coined words in prose. Claude has the same urge to invent words in prose. In code the coined word becomes an identifier and spreads through the code and into tickets.
Generic AI code smell (useless comments, god files, defensive code). These are listed together with naming in most complaints. Bad names are what make the code hard to read later.
Claude not following repo conventions in general. The wider complaint also covers file size and structure. Lint failures belong to it too. Naming drift is one symptom of it.

Objections

Several people point out that human code has generic variable names too, so this alone does not mark AI.
Some defend AI-friendly naming. They call long method names and many comments 'just different style' and do not count them as bad code.
Much of the evidence is about AI code in general (Copilot, Qwen, agents), with Claude named among them.
Some complaints are jokes that exaggerate (temp01 to temp83765, res_final_final) and are not real reports.

Changes over time

Reported across Opus 4.6 (April), Opus 4.7 (May), Fable 5 (June), Opus 5 (August to September) and Opus 5.5 (September).
With Opus 5 the complaints move toward context leaking into code. Metaphors and invented terms spread into modules and methods.
In mid-2026 Claude Code switched from random slugs to readable names for worktree branches.

Errors swallowed by fallbacks 37

Code that should stop on an error logs a line and carries on. Or it reaches for a default value (dict.get(..., default), || 'dev-secret', a hard-coded fallback).

“Silent failures are a big no-no in the type of work I'm doing, so the Claude special of trying to force code to finish gracefully is a sure sign that the code hasn't been tested or reviewed.” Reddit

Evidence

When Claude writes code it wraps large stretches in one catch-all try/except or try/catch. The catch block logs a generic message and returns a safe default such as null or a boolean, so the error never reaches anyone. Claude also adds 'graceful' fallback paths. A failed lookup gets a default value. A second or third code path stays alive 'just in case'. A missing field gets replaced by a guessed field name. Commenters say this code looks responsible and runs, but the failure gets buried. Later bugs are hard to trace, and one commit was '40% error handling logic'. Several users keep a standing rule in CLAUDE.md or in their session prompt ('exception handling no fallbacks', 'Always fail loudly') and say Claude still slips back into the pattern. Most commenters see it as a trait of AI code in general that Claude shows strongly.

Signs people name, with the number of people naming each

One try/catch that logs and keeps going A whole method sits inside one try/catch with a generic or empty catch block. It logs to stderr and continues. Some versions return null or a boolean instead. The stack trace is lost.		17
Default values instead of failing A missing value gets an invented default. Examples include dict.get('key', default) and process.env.SECRET \|\| 'dev-secret'. Others are 'some default fallback value deep in the code' and Math.max(1, ...) when a count is not provided.		8
Old and alternative paths kept alive One user says 'It will keep everything it can, leading to code with 10 pathways to do something and 20 fallbacks that obfuscate errors'. Claude tries every possible field name before it will fail and ask.		3
Defensive, wordy code in general Users call it 'way too defensive when it didn't need to be' and say it uses 'super defensive coding patterns nobody writes'. One says it 'will defensively engineer for impossible scenarios'.		6
Trivial calls wrapped defensively A try/catch goes around a console.log. Everything gets wrapped in mutexes for concurrency.		3
Persists despite explicit rules Users put 'NO FALLBACK PATTERNS' or 'exception handling no fallbacks' in CLAUDE.md or in every session prompt. They report that it still happens.		3

Posted cases

// Fallback for direct API use when caller doesn't provide source file count.¹ const filesWithDiagnostics = new Set(diagnostics.map((d) => d.filePath)).size; return Math.max(1, filesWithDiagnostics)²;

1Comment announces the fallback
2Guessed default, never fails

Neat, well-commented code from a repo built with coding agents. A missing input is replaced with a computed default and clamped to at least 1 instead of raising an error. The tool this code belongs to claims to catch exactly this pattern.

probably Claude. Thread

1Old path kept as fallback
2Second fallback behind flag
A clean, well-organised CLAUDE.md plan that keeps the old heroEntity path alive twice. Once it is an 'optional fallback' and once it sits behind a flag. A commenter in the same thread names this 'keep everything it can' habit.
probably Claude. Thread

Easy to mix up with

Missing error handling (code that only covers the happy path). The other complaint is about code with too little handling. With this habit Claude adds plenty of handling. The handling catches errors and hides them.
General AI verbosity. Verbosity covers length and duplicate helpers. The tell here is narrower. Catch blocks and fallback values hide failures and so change how the program behaves.
Insecure defaults such as hard-coded secrets. A fallback secret like process.env.SECRET || 'dev-secret' counts under both. Security reviewers object to the hole it opens. What marks this habit is the silent default itself.

Objections

Some commenters describe the reverse problem. Their AI code has no error handling, so the happy path works and the app falls over on unexpected input. That complaint is a separate one.
Defenders say careful error handling is what good developers do in production code. Critics answer that it is wrong for prototypes and scripts, and that Claude applies the same handling to every error without choosing.
One commenter blames GPT-5.6 Sol for the overly defensive and wordy style and does not blame Claude Fable.
Many of these comments say 'AI', or name Claude in the same breath as Copilot and Cursor and GPT. They do not present the habit as Claude's alone.

Changes over time

A January 2026 comment says Sonnet 4.5 was 'way too defensive when it didn't need to be' and that the code is now 'night and day' better.
Another January 2026 report describes a sudden change the other way. Claude Code started wrapping errors in try-catch with an empty catch block where it used to log them.
Complaints continue from June to August 2026, so the habit is still reported.

Insecure shortcuts in working code 34

Secrets typed into the source or the front end and routes with no auth check give it away, along with API responses that return every field and SQL built by joining strings.

“If you ask it to 'make Stripe work,' and the path of least resistance is hardcoding a secret key in the frontend, it will do it every single time without a second thought.” Reddit

Evidence

The label promised typical bugs such as a missing await or a leaked key. What commenters describe is mostly security shortcuts in code that otherwise runs. API keys and service-role keys are hard-coded in the source or shipped to the front end. Auth middleware or Supabase RLS policies are left out. An API returns whole objects, sensitive fields included. CORS is set to * and queries are built by joining strings. Floating promises and await inside loops come up only in a couple of posts about linters. A second, smaller strand is about keeping the repo tidy. Claude keeps adding to one file until it runs to thousands of lines, leaves console.log clutter behind, and waves off failing checks as 'pre-existing'. Most of the evidence comes from people promoting their own scanners and linters. Nearly all of it names Claude alongside Cursor and Copilot, or only says 'AI'. As a sign of Claude in particular it is weak.

Signs people name, with the number of people naming each

Hard-coded secrets and API keys Keys sit in the source or in front-end code. One app had an OpenAI key and a Supabase service-role key 'both hardcoded by the AI'. Other examples are fallback secrets like process.env.SECRET \|\| 'dev-secret' and secrets stored in a database table where a vault belongs.		10
Missing auth and RLS policies, unchecked input Scaffolded routes come without auth middleware, and endpoints have no authentication. RLS policies get left out 'because you can add that later'. One import trusted a user_id parameter straight from a CSV.		9
SQL built from strings Raw SQL where parameterised queries belong. In one case a query builder joined strings in a single edge case.		5
Responses that expose too much, and permissive config Every property of an object, sensitive ones included, goes into the API response. Other examples are Access-Control-Allow-Origin set to * and whole error objects serialised to the client.		3
Floating promises, await in loops, empty catch Named by the authors of an ESLint plugin built for Claude output, plus one reply agreeing that Claude reproduces them reliably.		2
Giant files and 'pre-existing' excuses Claude keeps writing to the same file until it is thousands of lines long. It calls failing tests or lint errors 'pre-existing' and tries to skip hooks.		3

Posted cases

11315 lines vs 300 max
2Called a pre-existing issue
A correct, tidy Claude Code edit. A hook flags the 1315-line file and Claude calls it 'a pre-existing issue'. It shows the secondary cue, oversized files with failing checks waved off, inside good work. No screenshot in the pack shows the main security cue.
clearly Claude. Thread

Easy to mix up with

Fallbacks that swallow errors. The fallback habit hides failures behind catch blocks and defaults. In this one the code is correct and leaves a security hole open.
Security failures of vibe coding in general. Most of these complaints apply to any AI builder. Commenters name Cursor and Lovable, and Bolt too. Only a few describe behaviour specific to Claude.

Objections

One commenter argues that current frontier models suggest 'overwhelming overkill and best practices' on security. The reply says this holds for well-documented cases. It fails on questions specific to a domain, such as which fields are sensitive.
Several posts promote the poster's own scanner, and most list Claude Code next to Cursor and Copilot. They do not present the habit as Claude's alone.
Some of the 'bugs' that AI tools report are themselves hallucinated. That is a separate complaint.

Changes over time

Reports run from January to August 2026 with no clear change. One July 2026 comment says Fable 'generated literal vulnerabilities by explicitly breaking existing patterns'.

Copy-paste Tailwind and hard-coded styles 12

Each button and card repeats one identical Tailwind string of 10 to 15 classes (bg-blue-600, rounded-md, hover:bg-blue-700, transition-colors), with raw palette colours in place of your design tokens and inline styles or magic numbers where a shared stylesheet belongs.

“AI models don't know your design system. They know Tailwind defaults.” Reddit

Evidence

When Claude builds UI it writes clean, working markup with utility classes. It types the full class string fresh on each element and does not extract a component or use the project's tokens. One user counted the same 15-class button 47 times and the same card 23 times in a project Claude built. It picks default Tailwind palette classes (bg-gray-100, text-zinc-500) or hard-codes a colour where semantic tokens or global CSS should go. It also adds small reflexes like hover:-translate-y-1 on every card. The pack mixes in a separate code habit, heavy inline comments, which several Claude Code users name. Comments are a neighbouring habit and are left out of this one.

Signs people name, with the number of people naming each

Same class string repeated everywhere Long, nearly identical Tailwind class lists sit on every button and card where one component or class would do.		3
Raw or hard-coded colours in place of design tokens Claude writes palette classes like bg-gray-100 and text-zinc-500 or a hard-coded hex. It skips the project's semantic tokens. Users add lint rules or prompts to stop it.		3
Inline styles and magic numbers Hard-coded inline styles and numbers are scattered through the front end where global CSS files belong.		3
Tailwind as the default nobody asked for Tailwind shows up even when the project did not choose it, along with other default picks like Supabase.		1
hover:-translate-y-1 on every card A utility that lifts cards on hover gets added by reflex. One team banned it with a lint rule.		1

Posted cases

1Default palette in place of a token
2Stock hover pair
3Full string retyped each time

The poster's typical Claude component. It is tidy, working Tailwind with default palette colours, and he found the same pattern repeated 47 times in one project Claude built.

probably Claude. Thread

Easy to mix up with

Verbose inline comments in Claude Code. This separate habit is about how much documentation Claude writes ('75% comments'). It sits in the same pack and concerns comments, which have nothing to do with styling.
The generic vibe-coded look (purple gradients). The vibe-coded look shows on the page itself. Copied class strings only show once you open the markup.
Tailwind written by a human team. Human teams pull repeated classes into components or @apply rules, and use design tokens for colour. The tell is the same full string copied across dozens of elements.

Objections

One Opus 4.5 user reports the reverse failure. Asked to change a button colour, Claude hard-coded it instead of using Tailwind.
Several people say vibe-coded code can rarely be spotted at a glance. It takes reading a fair amount of it.
Some put the repetition partly down to prompting. Constraints such as design tokens and BEM reduce it, and so does styling through selectors only.

Changes over time

Reports run from January to September 2026 with no sign of change. In September a reply in r/webdev still warned of inline styles and magic numbers in vibe-coded front ends.

Avoid them in your own work

39 rules, one for each habit people reported in the last 60 days, split by kind of work. 31 of them come with an automatic check. Rebuilt 2026-10-05 15:03 UTC every time this page updates.

Paste a prompt

Pick the kind of work. The short version fits a 1,500-character custom instruction field.

# Avoid Claude's habits when you write

These rules come from what 4,326 people on Reddit pointed out in work made with Claude. They cover the habits reported in the 60 days up to 2026-10-05, and each one says what to write instead. The list changes when a habit appears or fades. Fetch the current version from https://machinemorning.com/giveaway/rules/claude-writing.md.

- The em dash hinge. Use at most one em dash in a reply, and only for a true aside. Where a dash would hang a reason or a punchline on a sentence, end the sentence with a period or use a comma instead, and do not swap in "--" or the other substitutes. That covers "--", ":", ";", "→". An occasional em dash around a real aside is fine.
- Load-bearing, seams, blast radius. Say what you mean in plain words every time. Replace "load-bearing" with "essential" and replace "seam" or "blast radius" with the actual boundary or risk. Define any new label before you use it. The same applies to "load bearing", "loadbearing". Technical terms are fine in technical text when they are the right word.
- Metronome paragraphs. Vary paragraph length on purpose, so some paragraphs run long and some stop after one sentence. End each paragraph on its last real point instead of a neat summary line, and avoid runs of short fragments used for emphasis. Short sentences and parallel structure are fine where the content calls for them.
- Document furniture in prose. Answer short questions in plain paragraphs. Use headers and bullets only for long documents that readers will scan, and do not open each bullet with a bold label or put emoji on headings. Headings and lists in long reference documents stay useful.
- Candour labels and signposts. State the point without announcing it. Leave out "honestly", "genuinely", "here's the thing" and "worth flagging", and add a caveat only when it changes what the reader should do. Saying "honestly" once to admit a real mistake is fine.
- Padded and long. Put the answer in the first sentence and stop when the question is answered. Say each point once without a preamble or a recap. Add caveats only when they change the answer. Detail the user asked for, or that a reader would miss, stays in.
- Buzzword-heavy corporate register. Write in the register the user asked for and use everyday words. Repeat the project's agreed terms instead of rotating synonyms, and leave out stock words such as "delve", "leverage", "seamless" and "in today's landscape". Technical terms the reader needs, and a formal tone when the user asks for one, stay allowed.
- The "not X, but Y" reframe. Say what something is directly. Use a "not X, it's Y" contrast only when the reader really holds view X, and at most once in a piece. A contrast that answers a view the reader really holds is fine.
- The tidy bow at the end. End a paragraph or a reply on its last piece of content. Do not add a summary line, an aphorism, an unasked note or a question back to the reader. A closing line the user asked for, such as a polite sign off, is fine.
- Colon-led payoffs. Write the point as a plain sentence instead of a short setup followed by a colon and the payoff. Keep colons for real lists and definitions, and when you drop em dashes, use periods instead of semicolons or arrows. Colons that introduce a list or a definition stay allowed.
- Polished but says nothing. Give each paragraph a new fact, number, name or example, and cut sentences that restate the request or the previous point. Replace vague lines such as "something shifted" with what actually changed. Atmospheric lines in fiction are fine when used sparingly.
- Rule of three. Use the number of items the content really has. When a list comes out as three, check whether the true count is two or four. Avoid runs of three short parallel beats for emphasis. A list of three is fine when the content has exactly three items.
- Soft-framed hedging. State the claim first and qualify it once, only where the evidence is weak. When you disagree, say so plainly. End a comparison by taking a position. A hedge where the uncertainty is real and matters to the reader stays.
- Too-clean prose, faked mess. When asked to sound more human, rework the sentence structure itself. Do not lowercase sentence starts or plant typos on top of correct punctuation, since readers spot that as a disguise. Correct grammar and spelling remain the default.

Download .md Short version

# Avoid Claude's habits when you build a web page

- The AI purple. Choose the accent colour from the brand or the subject instead of defaulting to violet or indigo. Skip blue to purple gradients on hero text and buttons, and skip soft glows behind cards. Purple is fine when the brand already uses it.
- Serif headline, one italic word. Pick one or two type families that suit the brand and use them consistently. Avoid the stock recipe of a serif headline with one italic accent word, a tiny tracked caps label above it and monospace outside code. Any of these fonts on its own, chosen on purpose, is fine.
- Cards, with an accent stripe. Group content with spacing and headings instead of boxing every item, and give the most important item more size than the rest. Leave out the coloured accent stripe on one edge of cards. Cards stay allowed for items that are separate objects, like products.
- Pill above the headline. Use a pill only for a real tag or status, and drop the badge above the headline. Vary the corner radius by element instead of giving every container the same large rounding. Rounded corners and real filter chips stay allowed.
- Stock component kit. Restyle the component kit for the brief by changing radius, palette, spacing and icon set, and use the project's design tokens when it has them. Use icons only where they help someone find something, and never emoji in their place. Using shadcn or Lucide is fine once the result is styled for the project.
- The same hero, every time. Build the opening section around what this product or client needs, such as a product photo or a live demo, instead of the stock pill, headline, two buttons and three cards. Change the section order from one brief to the next. A clear headline and a main button, which most pages need, stay.
- Eyebrow over every heading. Let headings stand alone. Add a small label above a heading only when it carries real information, and number sections 01, 02 and so on only when order matters. An occasional kicker that adds information, as in editorial design, is fine.
- Cream and terracotta page. Take the background and accent colours from the brand or the subject. Without a brief, avoid the warm cream page with rust orange accents and a large serif headline, which reads as Anthropic's own palette. Warm palettes chosen to fit the brand are fine.
- Hairline borders, edge stripe. Separate areas with spacing or a background change instead of a faint 1px border on every container, and drop the coloured stripe on one edge of status cards. Use blur and glass panels only where content really sits over an image. Borders that separate items a reader must tell apart stay allowed.
- Dark by default, grey on grey. Use a light theme unless the brief or the subject calls for dark. Give labels and helper text strong contrast against their background and a size people can read. Dark themes are fine when the subject or the user calls for one.
- Dot-pill chips everywhere. Drop the decorative pill with a pulsing dot above the headline, and keep status chips on cards only when they show live data. Do not add fake terminal windows as decoration. Status indicators that show real live state are fine.
- Emoji as icons. Use an SVG icon set such as Lucide, or no icon at all, wherever the interface needs one. Keep emoji out of feature cards, navigation, buttons and headings. Emoji the user explicitly asked for are fine.
- Everything fades, slides, floats. Animate only where motion helps the user. Leave sections static as they scroll into view, drop the lift on hover, and skip moving decorative backgrounds and marquees. Motion that shows a change of state or responds to input stays.
- One spacing rhythm everywhere. Set spacing by importance. Group related items tightly, leave more space before major sections, and let the key section take more room than the rest. A consistent spacing scale is fine when it creates contrast between groups.

Download .md Short version

# Avoid Claude's habits when you make slides

These rules come from what 4,326 people on Reddit pointed out in work made with Claude. They cover the habits reported in the 60 days up to 2026-10-05, and each one says what to write instead. The list changes when a habit appears or fades. Fetch the current version from https://machinemorning.com/giveaway/rules/claude-slides.md.

- The same-every-time Claude deck. Lay out each slide around its content so the main point gets the most space. Avoid equal boxes or three columns on every slide. Take the palette and fonts from the client's template or brand. A grid of equal boxes is fine when the items really are equal.
- Over-written slide headings. Title each slide with a plain label or a short claim, and drop the small label above the title and the tagline below it unless they add information. Write body text in a neutral voice and give the main point more weight than the rest. A subtitle that adds a fact the title lacks stays.
- Claude's default deck palette. Use the client's brand colours or slide master. Without one, pick a palette for the subject instead of the beige ground with rust and blue accents, and keep body text dark and large enough to read from the back of the room. Warm palettes that match the client's brand are fine.

Download .md Short version

# Avoid Claude's habits when you write code

- Diary comments in code. Write a comment only when the code cannot show why on its own, and keep it to a line or two about the code as it is now. Keep the change history and anything from the chat out of comments. A short comment that explains a non obvious reason stays.
- Claude signs the commit. Follow the user's attribution choice. When they want none, leave out any line that credits Claude or links the session, and point them to the attribution setting or a commit hook, because CLAUDE.md rules are unreliable for this. Keeping the trailer is fine when the user wants the disclosure.
- Essay-length commits and PRs. Write a one line commit subject under 72 characters, and add a short body only when the reason is not obvious from the diff. Keep PR descriptions to what changed and why, in plain words. A longer body is fine when the change really needs explaining.
- Rewrites what already exists. Before writing a new helper, component, type or constant, search the repo for an existing one and reuse or extend it. Delete the old version when you replace code, and split files that pass the size limit the project sets. New code is fine when nothing suitable exists yet.
- Non-ASCII punctuation in code. Use plain ASCII in code, comments, strings, commit messages and project docs. Write hyphens for dashes and straight quotes for curly ones. For arrows write "->". Dashes in chat prose are a separate habit.
- Names from the chat, not the code. Name things after what the code does, following the repo's existing conventions, with words that tell similar items apart. Keep corrections and passing metaphors from the chat out of names and commit messages. Long descriptive names are fine, and some users prefer them for agents.
- Errors swallowed by fallbacks. Let the code fail loudly. Catch only the specific exceptions you can handle at that point, and when a required value is missing, raise an error instead of inventing a default. Error handling for failures the code can really recover from stays.
- Copy-paste Tailwind and hardcoded styles. Move repeated class strings into a component or a shared class, and use the project's design tokens instead of raw palette colours or hard coded hex values. Keep styles in the stylesheet instead of inline. Tailwind itself is fine when the project uses it.

Download .md Short version

Install the skills

For Claude Code. One skill per kind of work, each with a checker that flags hits in your file.

unzip claude-skills.zip -d ~/.claude/skills/

Download the skills

Run the checker

python check.py draft.md --rules claude.json

check.py claude.json

Connect the MCP server

Any MCP client gets the current rules for the task at hand and a checker as tools. The server fetches the list again every hour.

claude mcp add dead-giveaway -- uv run dead_giveaway_mcp.py

Download dead_giveaway_mcp.py

Changes to the list

2026-10-05 Dropped bugs.
2026-10-05 Added AI-style copy on the page (em dash, metaphors, explanatory text).
2026-10-04 The list started.

These rules repeat what people said about Claude's output. We have not measured how much they change a model's writing.

Each number counts people who described the habit on Reddit. It does not measure how often Claude does it. Screenshots and quotations appear as posted and link to their threads. The small bars count people per week since 1 January 2026. Thin grey lines mark Anthropic releases. Faded habits had no mention in the last 60 days.

41 signs your work was made with Claude

When Claude builds a web page15 habits show all

When Claude writes14 habits show all

When Claude makes slides3 habits

When Claude writes code9 habits show all

When Claude builds a web page

The AI purple

Signs people name, with the number of people naming each

Posted cases

Easy to mix up with

Objections

Changes over time

Serif headline, one italic word 281

Signs people name, with the number of people naming each

Posted cases

Easy to mix up with

Objections

Changes over time

Cards, with an accent stripe 150

Signs people name, with the number of people naming each

Posted cases

Easy to mix up with

Objections

Changes over time

Stock component kit 120

Signs people name, with the number of people naming each

Posted cases

Easy to mix up with

Objections

Changes over time

The same hero, every time 112

Signs people name, with the number of people naming each

Posted cases

Easy to mix up with

Objections

Changes over time

Pill above the headline 93

Signs people name, with the number of people naming each

Posted cases

Easy to mix up with

Objections

Changes over time

AI-style copy on the page (em dash, metaphors, explanatory text) 64

Cream and terracotta page 60

Signs people name, with the number of people naming each

Posted cases

Easy to mix up with

Objections

Changes over time

Hairline borders, edge stripe 57

Signs people name, with the number of people naming each

Posted cases

Easy to mix up with

Objections

Changes over time

Emoji as icons 49

Signs people name, with the number of people naming each

Posted cases

Easy to mix up with

Objections

Changes over time

One spacing rhythm everywhere 46

Signs people name, with the number of people naming each

Posted cases

Easy to mix up with

Objections

Changes over time

Dark by default, grey on grey 43

Signs people name, with the number of people naming each

Posted cases

Easy to mix up with

Objections

Changes over time

An eyebrow over every heading 41

Signs people name, with the number of people naming each

Posted cases

Easy to mix up with

Objections

Changes over time

Everything fades in and floats 27

When Claude builds a web page15 habits

When Claude writes14 habits

When Claude writes code9 habits