Dead Giveaway
newest comment read · rebuilt daily

Field guide · Claude (Anthropic) · Reddit comments from 1 January to 5 October 2026

41 signs your work was made with Claude

Updated live from what Reddit points out. Get the rules to avoid them.

Made with Claude, this page shows 6 of these habits. · See it without them

4,326 people described them between 1 January and 5 October 2026, each with a real screenshot or pasted output where one was posted. The most named: The em dash hinge, by 1,787 people.

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.

1 · When Claude builds a web page

15 habits, 869 people since 1 January 2026. Bars use one scale within this section; pale rows were not mentioned in the last 60 days.

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

Real Claude output posted on Reddit, shown for The AI purple. Numbers mark what commenters pointed at.

People naming each habit

The AI purple331Serif headline, one italic word281Cards, with an accent stripe150Stock component kit120The same hero, every time112Pill above the headline93AI-style copy on the page (em dash, metaphors, explanatory text)64Cream and terracotta page60Hairline borders, edge stripe57Emoji as icons49One spacing rhythm everywhere46Dark by default, grey on grey43Eyebrow over every heading41Everything fades, slides, floats27Dot-pill chips everywhere16
1234

The AI purple

331

Look for violet or indigo carrying the page: a blue-to-purple gradient on the hero, headline or main button, purple pills and active states, 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.”open comment

Not to be confused with Claude's newer warm look · Generic shadcn/Tailwind dark dashboard · Emerald/teal 'skills' look

Open the evidence

When Claude (mostly Claude Code and vibe-coded apps) is left to pick colours, commenters say it reaches for purple or indigo as the brand colour and for blue-to-purple gradients on hero sections, heading text and CTA buttons, often on a dark background with soft neon glows. It rarely comes alone: people name it in the same breath as Inter, a centered hero, three rounded feature cards and emoji icons, and they treat the colour as the fastest single tell of the package. Many commenters say it is the generic AI-website look rather than something only Claude does, and some trace it to Tailwind's indigo defaults; it is Claude-specific 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 increasingly 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 plus glow the model leans on.

How people spot it · people naming each sign
Blue-to-purple gradientOn the hero background, gradient-filled heading text or the primary CTA button; called 'the em dash of UI'.≈140
Purple/indigo as the main accent'Purple everywhere': purple buttons, pills, progress bars, active nav states, even on otherwise neutral pages.≈90
Soft neon glowGlowing buttons, blurred radial glows behind cards, gradient borders; 'Purple tint and slight glowy hue on everything. Claude loves that'.≈60
Dark mode with neon coloursNear-black or navy background with bright violet, blue, cyan or lime accents.≈40
Comes bundled with Inter, centered hero, three cardsThe colour is named as part of a set: Inter font, centered hero, three rounded feature cards, emoji or Lucide icons.≈90
Pastel or rainbow gradients on chips and headersMulticolour pastel tags and a gradient header; 'pastel gradients with a 1px border around everything'.≈10
Glassmorphism and blurFrosted cards and blurred backgrounds that come with the gradient.≈20
Real cases, as posted
12345
  1. 1Violet stat number
  2. 2Violet progress bar
  3. 3Violet percentage
  4. 4Glowing violet action button
  5. 5Violet active tab

A competent dark study-tracker screen where one violet does all the accent work: numbers, progress bars, active tab and the floating button; replies name 'the prominence of purple'.

clearly Claude: OP says 'my app created with Claude' and 'This specific style was created by Clyde' · open thread

1234
  1. 1Blue-to-violet gradient headline
  2. 2Purple corner glow
  3. 3Pill badge above heading
  4. 4Rainbow pastel chips

A clean, usable job board whose headline is a blue-to-violet gradient over a purple corner glow, with a pill badge above and rainbow pastel filter chips; a commenter says Opus defaults to exactly this.

probably Claude: attribution is the commenter's ('claude models especially opus like to default to rainbox theme with that specific gradient header'); OP does not name the tool · open thread

123
  1. 1Blue-to-violet gradient bar
  2. 2Glowing gradient icon
  3. 3Faint navy glow background

A polished onboarding screen: a blue-to-violet gradient progress bar and a glowing gradient icon on near-black, exactly the 'brightly colored vivid components on a dark background with some glow or gradient' the poster describes.

probably Claude: the poster built it with 'Lovable and Claude Code' and does not say which made this screen · open thread

1234
  1. 1Glow around central card
  2. 2Cyan wide-spaced caps
  3. 3Emoji as icons
  4. 4Green status dots

A neat agent dashboard built with Claude in the dark-neon variant: cyan spaced caps, glowing card, emoji icons; the reply says it looks 'like something opus 4.1 would produce with the purples and blues', though the hue here is cyan rather than violet.

clearly Claude: OP says the interface was built 'using Claude'; the model guess (Opus 4.1) is the commenter's · open thread

Easily confused with
  • Claude's newer warm look (cream background, terracotta/orange, serif with one italic word). That is the 2026 Claude-specific default; purple is the older, cross-model AI default that people now describe in the past tense.
  • Generic shadcn/Tailwind dark dashboard. Neutral zinc/slate cards with no colour statement; the purple tell needs the saturated violet accent or blue-to-purple gradient.
  • Emerald/teal 'skills' look. Same dark-with-glow recipe but the accent is emerald or teal, attributed to frontend skills and Claude Design rather than to the base model.
What it is not
  • Many say it is the generic AI/Tailwind look, not Claude's own: Tailwind indigo defaults and 2019-2023 startup branding are blamed.
  • One commenter argues it comes from post-training and style skills, not from the training-data average.
  • Gradients themselves are defended; the type and style of gradient is what gives it away, and some people genuinely 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 found no purple gradient in any of 12 Claude runs, with or without the frontend-design plugin.
Over time
  • People say the purple era is ending or over: 'Used be blue purple gradients', '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 knowing not to use purple gradients, but is said to have its own teal/cream defaults.
  • Green is increasingly named with or instead of purple: 'neon colors especially purple and a cyber green', '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.
12345

Serif headline, one italic word

281

Look for a big serif display headline with one word in italics (often coloured), a tiny spaced-out caps label above it, and monospace leaking into buttons.

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

Not to be confused with The generic AI look · Cream and terracotta page · Eyebrow labels

Open the evidence

When Claude (claude.ai, Claude Code, Claude Design) builds a page without a type brief, regular users recognise its typography on sight: not one font but a recurring type recipe. The current recipe is a large serif display headline (Playfair, Fraunces, Lora, Georgia-like) with one or two words switched to italic and often coloured in the accent colour, sitting on a cream or beige background with terracotta/orange accents. Above the headline sits a tiny all-caps, widely letter-spaced label, frequently set in a monospace font (sometimes led by a long dash or a status dot), and 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, plus small, thin or low-contrast secondary text. An older, more generic layer (Inter or Geist plus a geometric sans like Space Grotesk/Manrope, purple gradient) is still mentioned, but several people say that is the generic AI starter pack, whereas the serif-italic-plus-mono move is what reads as specifically Claude.

How people spot it · people naming each sign
Serif display headline with italic (often coloured) accent wordsBig serif headings (Playfair Display, Fraunces in its lightest weight, Lora, Georgia-like), mixing regular and italic in one headline, with one word italicised and tinted in the accent colour; also serif-and-sans switching mid-headline. Named as the strongest current Claude-specific tell.≈22
Cream/beige background and terracotta/orange accent around the typeThe fonts are almost never named alone: commenters pair them with the cream/off-white background, rusty orange or #c15f3c accent, beige-and-green or tan/khaki palette. Font plus colour is the most common short diagnosis.≈14
Monospace used outside codeMonospace (JetBrains Mono, a 'consolas looking font', a 'console style' or 'very techy' font) for eyebrows, section labels, numbering, buttons, stats and sometimes body copy, sitting next to warm serif/sans text. One commenter calls it the real telltale, more than Inter.≈12
Tiny all-caps, widely tracked eyebrow label above the headingSmall uppercase subtitle with extra letter spacing above h1/h2, often monospace, sometimes preceded by a long em-dash or a coloured status dot, or set inside a pill.≈12
Too many families, sizes and weights on one screenThree or four font families in a hero, many sizes, weights and colours, '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)The older default layer: Inter body, Space Grotesk or Manrope headings, Geist, often with purple gradients. Many treat it as the generic all-AI starter pack rather than a Claude-only tell, and this is where most disagreement sits.≈14
Small, thin or low-contrast secondary textVery small fonts in a secondary colour, thin small serifs, 'hacker-style-dark-mode-9px-font', dark-on-dark text that is decoration rather than readable.≈5
Real cases, as posted
12345
  1. 1dash + tracked caps eyebrow
  2. 2geometric sans display
  3. 3italic serif accent line
  4. 4serif stamp lettering
  5. 5tracked caps label

A handsome, finished game landing page whose hero is the exact recipe: geometric sans word, italic serif line in terracotta, tiny tracked eyebrow led by a dash.

probably Claude · open thread

12345
  1. 1condensed serif headline
  2. 2italic coloured words
  3. 3monospace buttons
  4. 4dot + mono eyebrow
  5. 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 · open thread

12345
  1. 1pill eyebrow with dot
  2. 2accent-coloured headline words
  3. 3monospace body copy
  4. 4mono nav links
  5. 5mono stat captions

A polished dark landing page for a Claude Code design skill that still shows the pill eyebrow with a dot and monospace body copy that commenters list as tells.

probably Claude · open thread

1234
  1. 1tracked caps title
  2. 2italic serif caption
  3. 3monospace readouts
  4. 4serif numbered list

Impressive Opus 5 3D demo whose side panels mix tracked caps titles, italic serif captions, mono readouts and serif lists, the 'mixture of unfitting fonts' a commenter counted.

clearly Claude · open thread

Easily confused with
  • The generic AI look (Inter, purple gradient). Commenters treat Inter plus purple as every AI tool's default; the serif-with-italic-word headline on cream is what they pin on Claude.
  • Cream and terracotta page. That habit is the colour; this one is the type. They usually appear together.
  • Eyebrow labels. The tracked caps label is one part of this recipe; the eyebrow habit covers it on every section, not only the headline.
What it is not
  • The fonts are not bad or rare; Inter, Space Grotesk, Manrope, JetBrains Mono, Lora are popular, well-made Google fonts that predate AI. Using one tells you nothing on its own.
  • It is the combination and treatment (sizing, placement, italic word, mono eyebrow, cream palette), not a single typeface.
  • It is not ugliness: commenters call the output nice, clean, better than most; the cost is recognisability among people who use Claude themselves.
  • It is a default, not a limit: with a named type pairing, a style guide or reference sites it goes away; several call it a sign the user gave no design input.
  • Purple + Inter is widely seen as a generic AI look shared across tools, not specifically Claude.
  • Not always the same pick: one user reports Claude chose Roboto.
Over time
  • Shift from the 2024 purple-gradient/Inter look to a typographic look: serif with italic accents, cream background, mono labels.
  • Playfair Display was the favourite for a while; lately Fraunces in its lightest weight shows up a lot, with regular+italic mixed headlines.
  • Tells said to 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.
  • Fable redoing a site to look less AI landed on the same layout, font and colour scheme as another user's site.
12345

Cards, with an accent stripe

150

Look for content chopped into many same-weight rounded boxes (a row of three icon-heading-blurb cards, a grid of KPI tiles, cards inside cards), and especially a thin colored bar along a card's left or top edge.

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

Not to be confused with The generic AI SaaS look · Claude's editorial type look · Stock shadcn/ui components

Open the 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 under the hero, a grid of metric tiles on a dashboard, list items as cards, and sometimes cards nested inside cards. The part commenters call specifically Claude, rather than generic AI, is the colored accent bar on one edge of each card (left side or top), often in a different colour per card; several tie it to the official frontend-design skill. Cards also tend to carry the same small furniture: an emoji or Lucide icon, a tiny all-caps spaced label, pills or a colored status dot, and 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.

How people spot it · people naming each sign
A row of three equal feature cards under a centered heroEach card is an icon or emoji, a bold heading and one or two sentences; the most-named part of the 'Claude default SaaS starter kit'.≈55
Cards everywhere / container soupEvery section, list item and stat is boxed; pages read as page after page of identical cards, especially on mobile.≈40
Colored accent bar on the card's left or top edgeA 3-4px stripe in an accent colour, often a different colour per card; the cue people name as uniquely Claude and link to the frontend-design skill.≈25
Rounded, softly shadowed or glassy cards with hover liftLarge radius, soft shadow or translucent glass, plus a lift, border highlight or reveal animation on hover or scroll.≈20
Cards nested inside cardsA card holding a panel holding more bordered tiles; builders list it in their banned-defaults files.≈12
Equal weight, no hierarchy; KPI tiles where a table would doEvery card gets the same drama; dashboards become a grid of metric cards even when the data wants a table.≈10
Card furniture: tiny caps labels, dots, pills, iconsAn all-caps spaced subtitle above the card title, colored dots, pills and a Lucide or emoji icon in every card.≈10
Real cases, as posted
12345
  1. 1Colored top accent bar
  2. 2New colour every card
  3. 3Spaced mono caps label
  4. 4Mono tag pill
  5. 5Emoji as icon

A doctor's notes site that Claude generated as a .html file: tidy and readable, but every specialty is a rounded card topped by a different-coloured accent bar, with an emoji, a spaced mono caps label and pills.

clearly Claude: OP says Claude dropped the .html file; the thread summary calls it the classic 'Claude Special' with 'signature colorful accent bars on the cards', and oc7qsgu names 'The colored edges (top or left) of the cards'. · open thread

1234
  1. 1Twin equal KPI cards
  2. 2Icon plus caps label
  3. 3Streak in its own card
  4. 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: OP posts it as 'a snippet of my app created with Claude'; the reply says it has "that 'I've seen this exact card design 1000 times' vibe". · open thread

1234
  1. 1Four boxed stat tiles
  2. 2Profile wrapped in card
  3. 3Pill tabs in container
  4. 4After: flat stat row

Left half is the Claude-built Drinqly profile before the fix: 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 it to remove all the cards.

probably Claude: OP built the app with Claude and says the fix was prompting it to remove 'all of the cards' after 'AI slop' comments; the before image is the unsteered output. · open thread

1234
  1. 1Wall of equal cards
  2. 2Heading plus two lines
  3. 3Card inside card
  4. 4Pill eyebrow label

The demo page of a Claude Code design skill: crisp dark styling, yet the features section is a 2x3 wall of equal rounded cards, each with an illustration box, a heading and two sentences, exactly what the skill's own file calls the biggest AI tell.

probably Claude: the page belongs to a skill that runs inside Claude Code and the thread treats it as one-shot Claude output ('one-shot output is the product', oyg8yov); the commenter quotes the skill's own rule against 'a wall of feature cards'. · open thread

123
  1. 1Three boxed value points
  2. 2Pill eyebrow above title
  3. 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, and the phone mock is a stack of rounded feed cards.

probably Claude: OP says 'I used claude to improve and build on my previous versions'; the reply calls out 'the three cards (plan goals, post proof, build together)'. · open thread

Easily confused with
  • The generic AI SaaS look (purple gradient, Inter, centered hero, three cards). Shared by every builder tool; 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 italic word, tiny spaced caps label, cream and terracotta). That habit is about typography and colour; this one is about layout: how content is boxed. They often appear together on the same page.
  • Stock shadcn/ui components. Plain shadcn cards are gray and stripe-free; commenters treat the per-card accent bar and emoji/icon-topped tiles as Claude's addition.
What it is not
  • The three-card SaaS skeleton is not Claude-only: people report the same from Lovable, v0, Bolt, Codex, Gemini and Kimi, and blame shadcn and stock Tailwind defaults.
  • Some say it is a no-input problem, not a Claude problem: give it a reference or a design system and it goes away.
  • Defences: some like bento grids, rounded corners and the colored card highlights, and say the public only sees 'a template'.
  • Cards on dashboards may simply be the trained-in convention, not an AI invention.
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, yet the colored-edge cards and four-card top row still 'scream Claude AI'.
  • Reports continue through Opus 5 (July) and Opus 5.5 (Oct 2026): '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).
123456

Stock component kit

120

The page looks like an unmodified shadcn/ui + Tailwind starter: slate or gray rounded cards with thin borders, default radius and accent, and a stock Lucide icon (or an emoji) beside every label.

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

Not to be confused with Claude's cream background and serif headline look · Generic 'AI purple gradient' look · Over-decoration

Open the evidence

Commenters recognise Claude-built interfaces by the untouched component kit underneath: shadcn/ui defaults on a stock Tailwind config, the same slate-gray bordered cards, the same radius and padding rhythm, and the default blue, indigo or purple accent. Icons come from Lucide in every slot (sparkles, zap, brain, a clock or calendar beside each label), or, in quick builds, emoji stand in for icons entirely. The kit brings a matching skeleton: a pill badge over the headline, a solid button beside a ghost button, three equal feature cards, an icon in a tinted rounded box. Several people point out it is the look, not the dependency: Claude reproduces Tailwind-style classes even when no framework is installed, and drifts back to them after being handed a different design system. Most commenters treat this kit look as shared by all AI builders (v0, Lovable, Cursor); what reads as Claude-specific in 2026 is the cream background and serif type layered on top, which is a separate habit.

How people spot it · people naming each sign
Untouched shadcn/Tailwind defaultsSame slate-gray cards, default radius, default primary token and padding rhythm; 'shadcn soup', 'tailwind clone #2137', 'exceptionally average passes at Tailwind CSS'.≈45
Emoji used as iconsLarge or mixed-style emoji in feature cards, buttons and nav instead of an icon set; called the 'first tell tale sign'.≈25
Purple, indigo or default blue accentThe kit's default accent, often as a purple-to-blue gradient or glow; 'what's with the love of the color purple?'.≈25
Lucide icons in every slotThe same Lucide set everywhere, especially Sparkles, Zap and Brain; an icon next to every label, row or date.≈16
Bordered rounded cards around everythingEvery section, metric and icon sits in a rounded box with a thin or tinted border, including an icon inside a half-transparent box of its own colour.≈14
Kit skeleton on landing pagesPill badge over a headline, solid plus ghost button, a stats row, three or six equal feature cards, all-caps eyebrow labels with a leading dot.≈10
Falls back to the kit despite a supplied systemGiven fonts, tokens or a full design system, Claude still adds the same accent bars and icons, invents a new button variant, or hard-codes bg-gray-100 instead of tokens.≈8
Real cases, as posted
123456
  1. 1Lucide clock beside label
  2. 2Lucide calendar beside label
  3. 3Bordered rounded stat cards
  4. 4Default purple accent
  5. 5Purple floating action button
  6. 6Stock Lucide tab icons

A tidy, working study-tracker made with Claude where every stat sits in a bordered rounded card with a Lucide clock or calendar icon, on the default purple accent.

clearly Claude · open thread

123456
  1. 1Lucide chart icon button
  2. 2Tracked all-caps label
  3. 3Lucide trending-up arrow
  4. 4Glowing green line
  5. 5Bordered stat tile row
  6. 6Stock Lucide tab icons

Fable 5's fitness screen is judged the better of two in a same-prompt test, yet it is built from stock pieces: Lucide trend and chart icons, bordered stat tiles, tracked caps labels, a glowing line.

clearly Claude · open thread

12345
  1. 1Sparkle emoji after headline
  2. 2Emoji inside filter pills
  3. 3Emoji as timeline icons
  4. 4Sparkle 'AI-powered' label
  5. 5Row of emoji tiles

A polished, working iOS routine app built with Claude Code and Opus 4.5 where emoji stand in for every icon, which the thread singled out as the giveaway.

clearly Claude · open thread

12345
  1. 1Pill badge with dot
  2. 2Solid plus ghost button
  3. 3Four bordered stat cards
  4. 4Image in rounded frame
  5. 5Pill theme toggle

A clean personal site where the owner let Claude build it with defaults; even after recolouring and new fonts, the kit pieces remain and readers named Claude at once.

clearly Claude · open thread

1234
  1. 1Pill badge with dot
  2. 2Solid plus ghost button
  3. 3Stock check-circle icon
  4. 4Big-number stats row

The demo page of a skill meant to stop generic Claude Code UI, recoloured green, still ships the kit skeleton: dot-led pill badge, solid and ghost buttons, stats row, stock check icon.

probably Claude · open thread

Easily confused with
  • Claude's cream background and serif headline look. That layer (cream or beige, italic serif, terracotta) is what people call specifically Claude in mid-2026; the stock kit is the generic layer underneath, shared by all AI builders.
  • Generic 'AI purple gradient' look. The gradient is one symptom; this habit is the whole untouched component system (cards, radius, tokens, icon set), which stays even when the colour is changed.
  • Over-decoration (icons, badges, counts nobody asked for). Adding unrequested elements is a separate habit; here the complaint is which stock pieces are used, not how many.
What it is not
  • Not a Claude-only habit: most commenters say Claude, v0, Lovable, Cursor and open models all converge on the same kit.
  • The library itself is not the tell; shipping it unmodified is. Some even recommend Lucide or shadcn as the fix for emoji icons.
  • Many blame the vague prompt rather than the model: with real references or tokens the output changes.
  • Not a quality failure: the result works and looks clean, it is the sameness people object to.
  • It is the look, not the dependency: Claude copies Tailwind-style classes even when no framework is used.
Over time
  • January to April 2026 complaints centre on purple gradients, shadcn and 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, serif type and emoji icons, while 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, yet commenters still list its fonts, soft glow and icons as Claude's standard picks.
12345

The same hero, every time

112

Look at the top of the page: a small pill or eyebrow label, a big headline with one word set off in colour or italics, a one-line subhead, a solid and an outline button, maybe a stats row or product panel, then a grid of three or so feature cards.

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

Not to be confused with Generic 'AI slop' landing page · Claude's typography look · Overstuffed app dashboards

Open the evidence

People describe a fixed page skeleton more than any single visual. Claude's first-pass sites open with a hero block (badge or eyebrow above, oversized headline, subhead, two calls to action) and then run hero, feature cards, how-it-works, CTA, footer, whatever the product is. Many commenters still call the hero 'centered' with 'three cards, Inter and a purple gradient', but that wording is the generic AI-template stereotype shared with Codex, Lovable and others; one tester who re-ran the brief in July found the purple, centred version no longer appeared and 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.

How people spot it · people naming each sign
Same layout regardless of briefDifferent prompts and clients (portfolio, car dealer, restaurant, status page) all come back with the same hero and section structure.≈40
Centred hero headlineBig headline centred over a subhead; the most-named single feature, often listed with 'three cards' as a pair.≈29
Row of three feature cards under the heroThree equal rounded cards, often with an icon or emoji each, directly below the hero.≈14
Soft gradient (purple/indigo or teal) behind the heroGradient background or gradient button; purple is the stereotype, teal, sage or yellow-cream are named as Claude's own colours.≈30
Pill badge or eyebrow text above the headlineA small rounded pill, often with a green dot or version number, or an all-caps eyebrow sitting over the H1.≈9
Fixed section flow after the heroHero, features grid, how it works (1-2-3), testimonials or FAQ, CTA, footer.≈6
Highlighted word and two contrasting buttonsOne word of the headline in a different colour or italics, plus a filled and an outline button side by side.≈5
Extras right below the heroA thin marquee strip, a stats row, or a version banner sitting in or just under the hero.≈4
Real cases, as posted
12345
  1. 1Pill badge above headline
  2. 2Highlighted word in headline
  3. 3Solid plus outline button
  4. 4Stats row under hero
  5. 5Same layout, run 5

Same brief run repeatedly without the frontend-design plugin: the plugin-off heroes repeat one another (pill badge, 'Your status page shouldn't...' headline with a highlighted word, two buttons, stats row, live panel on the right).

clearly Claude: the poster ran the brief in Claude with and without Anthropic's frontend-design plugin and says the plugin-off runs repeat each other · open thread

12345
  1. 1Pill tagline above headline
  2. 2Second word in accent colour
  3. 3Three feature pills
  4. 4One big CTA button
  5. 5'How it works' scroll cue

A clean, warm landing page the owner built with Claude, which readers kept calling 'clearly AI': pill tagline, two-tone wordmark headline, three feature pills, CTA, phone mockup and a 'How it works' scroll cue.

clearly Claude: the OP says 'I used claude to improve and build on my previous versions', and the reply names 'Claude colors' and the hero layout · open thread

123456
  1. 1Centred serif headline
  2. 2Italic accent-coloured words
  3. 3Install command box
  4. 4Solid plus outline button
  5. 5Mono '//' eyebrow label
  6. 6Grid background

A polished centred hero on a grid background (serif headline with an italic blue phrase, centred subhead, install command, solid and outline buttons, mono 'REGISTRY // LIVE' label), held up as the generic look the OP's Claude Code agent keeps producing.

probably Claude: the r/ClaudeCode OP asks how to get Claude Code past 'the generic white background design (image shown above)'; the post does not say outright that Claude built this page · open thread

Easily confused with
  • Generic 'AI slop' landing page (purple gradient, Inter, emoji icons). That look belongs to every AI builder and older models; the Claude version is a repeated skeleton that now often comes in serif or mono type, cream or dark backgrounds and a split hero.
  • Claude's typography look (serif headline with one italic word, tiny spaced label, cream and terracotta). That habit is about type and colour; this one is about structure: 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 across sites.
What it is not
  • Many say this is not Claude-specific: Codex, Stitch, Lovable and other models land on the same SaaS skeleton because they share a training distribution.
  • Defenders say it is Claude defaulting, not failing: with references, a token file and a banned-patterns list 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 (too much on one screen), which is a separate habit from the hero template.
Over time
  • A July 2026 re-run of the same brief found the purple-gradient, centred, giant-99.99% cluster no longer appeared; plugin-off runs instead repeated one split layout with each other.
  • One marketer says it has improved over the last couple of model releases, but first passes still come back in the same boxy structure.
  • Complaints continue through Claude Design (April), Fable 5 (July) and Opus 5.5 (September).
1234

Pill above the headline

93

Look for a small rounded pill or badge sitting above the hero headline, often with a coloured dot inside, then more pills, chips and generously rounded cards repeated down the page.

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

Not to be confused with The generic AI SaaS look · Claude's cream, serif and terracotta typography look · Codex/GPT UI defaults

Open the evidence

When Claude designs a page or app UI without a reference, it fills the gaps with pill shapes: an eyebrow badge above the H1, status chips with a little green dot, feature pills under the intro, pill-shaped buttons and toggles. Around them, containers get a large, uniform corner radius, so cards, tiles and panels all read as the same soft shape. Commenters say the single strongest field mark is the pill above the headline; the general 'rounded corners' complaint is broader and partly shared with other AI tools and shadcn/Tailwind defaults. Several note Claude even converts plain controls (checkboxes, tags) into pills when asked to make something look better.

How people spot it · people naming each sign
Pill or badge above the hero headlineA small rounded eyebrow tag over the H1 ("Launching First in Pennsylvania", "CLAUDE CODE SKILL · MIT LICENSED"), and often one per section.≈14
Large radius on every containerCards, tiles, inputs and panels all share the same generous radius (rounded-2xl/3xl); 'rounded to oblivion', 'fingernail cards'.≈30
Pills and badges with no jobTags, chips and badges scattered through content and lists, sometimes pills nested inside pills; 'pills galore', 'wants to put everything in a pill'.≈16
Status pill with a coloured dotA pill holding a small green or coloured 'status light' dot, sometimes blinking.≈7
Fully rounded buttons50% border-radius buttons, often a solid button beside a ghost button in the hero.≈7
Rounded card with a coloured left borderA single accent stroke on the left edge of a rounded box; said to be a giveaway in earlier models.≈6
Cards nested in cardsRounded containers stacked inside each other.≈5
Real cases, as posted
1234
  1. 1Dotted pill above headline
  2. 2Row of feature pills
  3. 3Pill tab toggle
  4. 4Tag pill in card

A clean, warm landing page with a dotted pill above the H1, a row of feature pills, and pill toggles and tags in the phone mockup.

clearly Claude · open thread

1234
  1. 1Dot inside the pill
  2. 2Pill eyebrow above H1
  3. 3Pill shapes in mockup
  4. 4Big-radius card

A polished dark landing page for an anti-slop Claude Code skill that still opens with a dotted pill eyebrow.

probably Claude · open thread

1234
  1. 1Big-radius stat card
  2. 2Same radius container
  3. 3Rounded calendar tiles
  4. 4Round floating button

A tidy study-tracker app where every card, tile and button carries the same large radius.

clearly Claude · open thread

Easily confused with
  • The generic AI SaaS look (purple gradient, Inter, three feature cards). That look is blamed on every AI builder; the pill eyebrow with a dot and the uniform big radius are the parts people tie to Claude specifically.
  • Claude's cream, serif and terracotta typography look. That is about fonts and colour; this is about shapes. They often appear on the same page.
  • Codex/GPT UI defaults. Commenters contrast Claude's rounded edges with Codex's sharper ones.
What it is not
  • Rounded corners, bento grids and accent bars predate AI; some designers resent them being treated as a tell.
  • Several argue it is not Claude-specific: it is the shared Linear/Vercel/Stripe 'premium SaaS' look, shadcn and Tailwind defaults, also produced by v0, Lovable and Cursor.
  • Some note most people will not notice, and the result can still look good.
  • One user says Claude kept their app business-like and avoided the rounded purple look.
Over time
  • The rounded left-border accent box is described as a giveaway in earlier models, and was asked about for Opus 4.6.
  • From mid-2026 the pill eyebrow and dot badges become the main named shape tell; one commenter calls pills 'the big new AI flag for UX' after Fable 5 turned checkboxes into pill switches.
  • Complaints continue through September 2026, including with Claude Design and Claude Code anti-slop skills installed.

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”open comment

123456

Cream and terracotta page

60

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

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

Not to be confused with Generic AI look · Claude's type recipe · Emerald/dark-mode 'skills' look

Open the evidence

When Claude, Claude Code or Claude Design styles a page without a colour brief, it reaches for a warm cream, beige or 'newspaper off-white' background with orange, terracotta or rust accents, and pairs it with a large serif headline. Commenters treat this as one package with the type moves around it: one word of the headline in italics and in the accent colour, a tiny widely tracked all-caps or monospace label above it, mono accents, numbered 01/02/03 sections and rounded cards. 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, but the dominant pairing in the evidence is cream with orange, and a dark variant (near-black with orange or gold plus the same serif) is also called Claude's.

How people spot it · people naming each sign
Cream, beige or warm off-white backgroundCalled cream, beige, ivory, taupe, 'piss colored', 'newspaper off-white', 'warm peachy'; applied to the whole landing page, not just cards.≈35
Orange, terracotta or rust accentHeaders turn orange when no colour is given; accents described as rusty orange, burnt orange, brown and orange, 'piss-yellow'; read 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', sometimes clashing with a rounded sans UI.≈17
One italic word in the headline, in the accent colourThe last or a key word of the headline set in italic serif and coloured, even when users ask it to stop.≈4
Tiny tracked-out caps or mono label above the headlineEyebrow text, 'robotic mono preheader', monospace accents, status dots, a dash before the label.≈7
It looks like Anthropic's own sitePeople 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 greenA smaller strand: beige plus sage green, 'the sort of colors you see on other note-taking apps'.≈3
Dark variant: black with orange or goldSame serif and tracked caps on near-black with gold or orange accents.≈3
Real cases, as posted
123456
  1. 1tracked mono eyebrow
  2. 2italic serif word
  3. 3large serif headline
  4. 4spaced caps tags
  5. 5italic serif feature title
  6. 6cream, rose, rust palette

An editorial floral-studio hero on newspaper off-white with a big serif headline, an italic word, rust accents and tracked mono labels, built inside Claude Design.

clearly Claude: the screenshot shows the Claude Design editor and chat; the thread is about Claude Design on Opus 4.7, and the commenter calls this 'the same old newspaper off-white background with serif fonts and monospace accent fonts'. · open thread

123456
  1. 1tracked caps eyebrow
  2. 2heavy serif title
  3. 301 02 03 numbering
  4. 4dash plus mono label
  5. 5italic serif quotes
  6. 6italic orange accent words

A tidy, credible video-editor portfolio on warm cream with heavy serif headings, red-orange accents, an italic accent phrase and tracked mono labels.

probably Claude: the OP's post says the feature list was 'Written by Claude' and that it is 'not totally made by AI'; the commenter says the colour scheme 'is literally the Claude color scheme'. · open thread

1234
  1. 1tracked caps heading
  2. 2italic serif quote
  3. 3cream rounded card
  4. 4gold accent stars

A clean testimonial strip: tracked caps heading, italic serif quotes on cream rounded cards with gold stars, the beige-plus-orange look in a small crop.

probably Claude: the commenter says 'it is glaringly obvious you used Claude for this' and names 'The beige/cream + orange'; the OP does not confirm. · open thread

1234
  1. 1orange tracked mono eyebrow
  2. 2condensed serif headline
  3. 3italic orange words
  4. 4orange mono button

A handsome dark hero where the same recipe shows in orange: tracked mono eyebrow, condensed serif headline with an italic orange second line, mono button.

probably Claude: the commenter cropped this hero from the OP's live site and wrote 'Claude sure loves orange'; another reply in the thread says 'The Anthropic serif font and cream white. Looks like Claude'. · open thread

1234
  1. 1serif headline, gold words
  2. 2gold tracked caps button
  3. 3gold nav button
  4. 4serif stats, caps labels

A professional-looking betting-tool landing page in the dark variant: black, gold and cream with a serif headline, tracked caps buttons and serif stat numbers.

probably Claude: the commenter states 'This image is a Claude-built website. This is the signature style of Claude' and names black / gold / cream. · open thread

Easily confused with
  • Generic AI look (purple gradients, Inter, emoji icons). That look is shared by all tools and is described as the 2024 era; the cream-orange-serif look is tied to Claude specifically.
  • Claude's type recipe (italic serif word, mono eyebrow). The type moves often ride along with this palette, but the palette alone (cream plus orange) is what people name first here.
  • Emerald/dark-mode 'skills' look. Emerald glow on dark backgrounds comes from Tailwind/skill examples across models, not the warm cream palette.
What it is not
  • Some defend it as good, readable design: warm background, serif, 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.
  • Not the purple accent or Inter/Geist look; commenters attribute purple to ChatGPT and Inter-plus-Tailwind to all AI tools.
  • People disagree whether it comes from Claude's defaults or from the frontend-design skill being switched on.
Over time
  • Described as the successor to the purple-gradient AI look of 2024; the new 'AI slop' look is warm peachy background plus bright orange.
  • Some date it to Fable and to Anthropic adding it to the frontend skill or system prompt 'lately', and to the launch of Claude Design (the New Yorker piece).
  • Reports run from February to late September 2026 and are still active.
1234

Hairline borders, edge stripe

57

Every container sits in its own card with a faint 1px border or soft shadow, and status cards get a thick coloured stripe down the left edge; frosted glass panels show up 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.”open comment

Not to be confused with Generic AI SaaS template · Apple Liquid Glass · Claude's cream-and-serif look

Open the evidence

What commenters actually pin on Claude under this label is borders, more than glass. Claude wraps nearly every container in a very subtle 1px border or a slightly different shade, nests cards inside cards, and gives tiles 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, backdrop blur and imitation Liquid Glass panels are mentioned often, but mostly inside generic 'purple gradient, rounded cards, glassmorphism' lists that cover all AI tools; a few tie translucent badges and glass buttons to Claude and Fable 5 specifically.

How people spot it · people naming each sign
Coloured border on one side of a cardA thick accent stripe on the left (sometimes top) edge of tiles, callouts and chat bubbles, often colour-coded green/red by status.≈11
Faint 1px border around every container'Very subtle borders' on basically every container, borders in a slight shade difference, bordered buttons and headlines, 'beveled borders'.≈11
Glassmorphism and backdrop blurFrosted translucent panels, glass buttons and nav, imitation Liquid Glass boxes, semi-transparent badge above the title, content that unblurs on scroll.≈12
Soft drop shadows and hover glowShadow on hover transition on everything, box shadows, 'AI styled shadow'.≈8
Cards nested in cardsEvery metric in its own floating card; nested cards instead of flat dividers.≈3
Pastel gradient behind bordered cardsPastel gradients with a 1px border around everything.≈1
Real cases, as posted
1234
  1. 1green left-edge stripe
  2. 2red stripe for warning
  3. 3tinted icon tile
  4. 4stripe on every row

A polished dark connection-diagnostics screen where every metric card carries a colour-coded stripe on its left edge, green for healthy, red for jitter.

clearly Claude: the OP says Opus 4.6 with Claude Code and the Superpowers plugin designed it; a reply says 'I made this style with Claude a few months ago, same left border accenting ( color coded )'. · open thread

1234
  1. 11px border on card
  2. 2bordered profile pill
  3. 3bordered streak panel
  4. 4outlined calendar cells

A clean study-tracker dashboard where every panel, pill and calendar cell is outlined by a faint 1px grey border.

clearly Claude: the OP says 'Here's a snippet of my app created with Claude' and that the style was created by Claude; the commenter names 'The 1px grey border'. · open thread

1234
  1. 1translucent pill badge
  2. 2hairline-bordered chips
  3. 3soft drop shadow
  4. 4bordered shadowed card

A warm, tidy landing page whose tells are container treatment: translucent pill badge, hairline-bordered chips, soft drop shadows and a bordered card stack in the phone mock.

probably Claude: the OP says 'I used claude to improve and build on my previous versions'; the commenter's fix is 'get. rid. of. drop. shadows.'. · open thread

Easily confused with
  • Generic AI SaaS template (purple gradient, glassmorphism, rounded cards). That bundle is blamed on Claude, ChatGPT, Cursor alike; the one-sided coloured border and hairline-on-everything are the parts people tie to Claude.
  • Apple Liquid Glass. Claude imitates it with CSS translucency instead of using real Liquid Glass elements, which reads as cheap.
  • Claude's cream-and-serif look. Different layer: palette and type versus container treatment; they often co-occur on the same page.
What it is not
  • Rounded corners and cards are just modern framework styling; calling them AI tells is unfair.
  • The left border is not Claude-only: a commenter says Gemini made the same green-edged boxes.
  • The borders are not bad design, just a recognisable trademark.
  • Glassmorphism is mostly named as part of a cross-model generic SaaS template, not as Claude's own.
Over time
  • Sonnet 4.6 was said to have improved on 'a lot of boxes with shadows' compared with earlier models, while 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 it not to age well.
1234

Emoji as icons

49

Look for colour emoji (🚀 ⚡ 🔒 ✨, a megaphone for Marketing, a money bag for Finance) used where a designed product would have an icon set: feature cards, sidebar items, filter chips, CTAs and hero headlines.

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

Not to be confused with The generic purple-gradient AI look · Claude's editorial serif look · Emoji in chat replies or code

Open the evidence

When Claude builds a web page or app without a design system, it fills icon slots with emoji: one emoji per feature card or nav item, an emoji in a rounded square above a heading, sparkles beside headlines and buttons, a rocket in the hero. Commenters treat it as one of the fastest tells of a vibe-coded site, and the standard advice in feedback threads is "drop the emojis" and use an SVG icon set such as Lucide instead. It almost always comes bundled with the rest of the default look (purple-blue gradient, dark theme, rounded cards), and 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, not only Claude; the Claude-specific mentions are from people who built with Claude or Claude Code and from comments like "Claude does both these things".

How people spot it · people naming each sign
Emoji anywhere in the UI read 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 cardsListed together with purple/blue gradients, dark theme, neon accents, centered layouts and identical 3-card sections.≈11
Emoji in icon slots: feature cards, bullets, CTAs"regular text and an emoji in a square", "emoji bullets", "oversized emojis", "emojis for CTAs", "random emojis".≈7
Fix: use an SVG icon set"try using SVG icons!", "use lucide icons instead of emojis", "use an icon pack instead of emojis".≈3
Rocket emoji specifically"rocket emojis", "rocketship emojis" as the shorthand for vibe-coded SaaS.≈3
Emoji used as decoration because Claude has no imagesClaude's lack of image generation said to push it to pills, cards and emojis "to make the website look good enought in first go"; "emoji as decoration".≈2
Arrow symbols alongside emoji"emojis or these stupid arrow symbols. Claude does both these things."≈1
Carries into non-web layoutsA brand manager reports Claude suggesting social-media emojis in a print skincare ritual card.≈1
Real cases, as posted
1234
  1. 1sparkles beside headline
  2. 2emoji as filter-chip icons
  3. 3emoji as timeline markers
  4. 4emoji tiles on AI card

A warm, carefully finished iOS routine app where every icon slot (filter chips, timeline nodes, the AI card, the headline) is a colour emoji; a commenter says it "gives AI made slop immediately".

clearly Claude · open thread

1234
  1. 1emoji as page-title icon
  2. 2emoji as sidebar icons
  3. 3megaphone for Marketing
  4. 4money bag for Finance

A coherent dark dashboard with a tidy org chart, where each department and nav item is labelled with an emoji instead of an icon.

clearly Claude · open thread

123
  1. 1emoji face as avatar
  2. 2emoji face as avatar
  3. 3emoji for 'prefer not'

A clean onboarding screen (wheel picker, progress bar) whose gender options use emoji faces as avatars; the reply praises the progress bar and says to swap the emoji for SVG icons.

probably Claude · open thread

Easily confused with
  • The generic purple-gradient AI look. Gradients and cards are about colour and layout; this tell is specifically emoji filling icon slots. They usually appear together but either can occur alone.
  • Claude's editorial serif look (big serif headline, cream background). That is Claude's newer house style; emoji icons belong to the older dark, gradient SaaS default, though emoji also show up on the cream style (sparkles, chip icons).
  • Emoji in chat replies or code. Here the emoji are part of the shipped UI that end users see, not in Claude's messages or source comments.
What it is not
  • Not Claude-only: 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's own choice: 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.
  • Not every Claude-built page has them: a Fable 5 landing page drew AI accusations with "not a single emoji", and one user says Claude Design produces non-AI-looking design without emoji.
Over time
  • One commenter (August 2026) ties emoji plus purples and blues to what "opus 4.1 would produce", implying 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, though some Fable 5 era pages are noted as emoji-free.
1234

One spacing rhythm everywhere

46

Look for sections, cards and gaps that all share one tidy rhythm and one visual weight, with no tight groups or deliberate empty space to say what matters.

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

Not to be confused with The generic 2024 AI look · Claude's type recipe · Unpolished vibe-coded apps

Open the evidence

When Claude builds a page or app screen unbriefed, commenters say spacing is one of the first giveaways, usually named in the same breath as fonts and colour rather than alone. The most common description is not 'bad spacing' but uniform spacing: every section has the same rhythm, every card the same padding and weight, three equal cards, centred and symmetric, so the hierarchy goes flat and 'nothing feels decided'. A second group describes the same pages as having too much whitespace (big empty bands above and between sections), and a third says the opposite of 'perfectly even': spacing that drifts, squeezes things together and then leaves huge gaps, or changes between sessions. So the label 'perfectly even spacing' is only half right; what people actually recognise is a default spacing rhythm applied mechanically, which reads as evenness on a landing page and as inconsistency once a project grows.

How people spot it · people naming each sign
Same spacing rhythm in every sectionEach section, card and gap uses the same spacing, so no section gets priority and no group feels tight; hierarchy flattens.≈12
Equal-weight cards in a symmetric, centred layoutThree equal cards, same card weight, same CTA treatment, centred hero; 'uniform contrast (everything same visual weight)'.≈6
Inconsistent or 'weird' spacing that feels undecidedSpacing rhythms that do not quite line up, squeezes then gaps, buttons that align with nothing; the opposite reading of the same default.≈8
Too much whitespaceBig empty bands above the fold and between sections; generous air everywhere rather than where it matters.≈5
A single default spacing scale'8px-everything spacing', 'default spacing', 'same spacing' as part of one visual skeleton the model falls back to.≈4
Spacing drifts between promptsIn longer projects Claude Code rewrites spacing and radii every few prompts until tokens are pinned.≈2
Ignores spacing instructionsUsers have to repeat spacing fixes several times; the model falls back to its template even with specific instructions.≈2
Real cases, as posted
1234
  1. 1two equal stat cards
  2. 2same gap between blocks
  3. 3same gap again
  4. 4uniform grid cells

A tidy, good-looking dark study tracker where every block gets the same rounded card, the same inner padding and the same gap, so no section leads.

clearly Claude · open thread

1234
  1. 1empty band above hero
  2. 2pill above the name
  3. 3three equal-weight chips
  4. 4next section far below

A polished cream landing page where a large empty band sits above the hero and the pill, chips and CTA are stacked at one even rhythm, flattening the hierarchy.

probably Claude · open thread

Easily confused with
  • The generic 2024 AI look (purple gradient, bento grid, gradient hero text). That is a colour and component cliché shared by all tools; the spacing complaint is about rhythm and hierarchy and survives after the gradient is gone.
  • Claude's type recipe (serif headline with an italic word, tiny tracked label). Usually named alongside spacing as part of the same Claude look; type is what people spot first, spacing is what makes it feel templated.
  • Unpolished vibe-coded apps. Those have genuinely sloppy, mismatched spacing; the Claude habit is tidy and consistent but flat.
What it is not
  • Several commenters blame the opposite fault (inconsistent, squeezed or drifting spacing) rather than evenness, so the field mark is 'default rhythm', not literally identical gaps.
  • Some say the generic feel is the copy, not the layout; the defender of the layout point agrees it is both.
  • 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 explicitly group Claude with Gemini and Bolt.
Over time
  • Sonnet 4.6 was said to improve animations, font variety and fewer shadowed boxes, but 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'.
1234

Dark by default, grey on grey

43

Look for an unbriefed app or dashboard that 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.”open comment

Not to be confused with The generic AI SaaS look · Claude's cream-and-serif landing page look · A deliberate dark brand or terminal aesthetic

Open the evidence

When Claude (Claude Code, claude.ai, Claude Design) designs an interface without a colour brief, many users say it reaches for a dark theme by default, especially for dashboards, tools and data reports, where it drifts into a 'hacker' or terminal-style dark look. The surfaces are layered greys: slate or dark-grey cards on a near-black page, a neutral grey palette, often one blue or purple accent with a soft glow. The part people complain about most is the text: light-grey or mid-grey labels and helper copy on dark grey, frequently small, which makes it 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, while 'dark by default' is the most common description for tool and dashboard UIs.

How people spot it · people naming each sign
Dark theme by defaultUnbriefed apps, dashboards and landing pages come out dark; users say they did not ask for it and have to steer away from it.≈16
Grey text on dark greySecondary text, labels and empty states in light or mid grey on dark surfaces, often failing contrast; 'grey on dark grey making it unreadable'.≈9
Purple or blue accent with glow on the darkPurple pills, glows and neon gradients sit on the dark surface; shared with other AI tools.≈6
Slate-grey cards and neutral grey paletteIdentical slate grey cards, dark sidebar, card grid, neutral grey palette, blue/grey colour choice.≈4
Hacker or terminal dark look for dataAsked for a report or tool on data with no design input, Claude produces a 'hacky terminal dark theme'.≈3
Tiny text on the darkSmall font sizes compound the low contrast ('9px font', 'text for ants').≈4
Every dark card has equal dramaBorders and shadows on every card, equal-weight KPI cards on the same dark surface.≈2
Claude Design falls back to Anthropic's own dark coloursWithout a brand, Claude Design defaulted to the Claude app's own dark-mode palette.≈1
Real cases, as posted
12345
  1. 1grey subline on black
  2. 2dim grey caps label
  3. 3dark grey card surface
  4. 4low-contrast grey text
  5. 5grey cells on grey

A polished study-tracker screen on near-black with dark-grey cards, where the date line, caps labels, 'Best: 9d' and calendar dashes are all dim grey on grey.

clearly Claude · open thread

1234
  1. 1dark grey stat cards
  2. 2small grey helper text
  3. 3grey grid on dark
  4. 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 · open thread

Easily confused with
  • The generic AI SaaS look (purple gradient, glow, emoji). That is the accent layer every tool adds; the Claude complaint is the dark-grey surface 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 but not the dark surface.
  • A deliberate dark brand or terminal aesthetic. Those are requested; the habit is dark appearing when the prompt said nothing about colour.
What it is not
  • Many commenters say dark mode is the default of all AI tools (ChatGPT, Gemini, v0, Lovable, GLM), not Claude alone; 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, dashboards and data tools.
  • Dark is not wrong in itself: for some subjects (a magician's site) it is what every human designer does too.
  • Some dark results were chosen by the user, e.g. a requested retro CRT terminal, or a palette the maker says was his own choice.
Over time
  • Low contrast is described as 'a problem it has carried from the beginning' as of Sonnet 4.6.
  • Through the Opus 4.7, 4.8 and Fable period (May to July 2026) dark default is still reported; one user says Fable built 'generic minimalist dark mode' where 4.8's mockup had not.
  • Still reported in September 2026 alongside Sonnet 5.
1234

Eyebrow over every heading

41

Look for a small, all-caps, letter-spaced label (often monospace, coloured, or led by a dot) sitting above nearly every heading, and sections 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.”open comment

Not to be confused with Claude's serif-headline-with-italic-word type recipe · The generic pill badge above the headline · All-caps UI text in general

Open the evidence

When Claude builds a landing page, portfolio or app screen, and above all in Claude Design, commenters say it puts an 'eyebrow' (a short kicker line) above almost every headline and section heading. The eyebrow is small, set in all caps with extra letter spacing, frequently monospace or in the accent colour, and is often paired with a status-style dot or 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': the device itself is an old editorial convention, but Claude applies it everywhere by default, and the eyebrow text is often filler.

How people spot it · people naming each sign
An eyebrow over every headingA small kicker above the hero headline and above each section heading, used by default on every page.≈17
All caps, small, letter-spacedThe label is tiny, uppercase and tracked out; 'all-caps subtitles with extra letter spacing above titles'.≈10
Paired with a status dotA coloured or blinking green dot leading the eyebrow or pill, the 'status eyebrow'.≈8
01 / 02 / 03 numberingSections or cards numbered in front of the title, read as a Claude Design and Claude Code tic.≈5
Over-explained subtext everywhereEyebrows and subtext on every block; the eyebrow copy itself is 'rubbish, and perhaps even nonsense'; instructions placed in random spots.≈4
Monospace eyebrowsEspecially tiny eyebrows set in a monospaced font.≈3
Coloured eyebrowEyebrow in the accent colour, e.g. orange-tinted subheadings.≈2
Real cases, as posted
1234
  1. 1banner above the name
  2. 2status-style dot
  3. 3tracked caps section label
  4. 4small caps label

A warm, finished landing page with a dot-led pill banner above the product name and a tracked caps 'HOW IT WORKS' label, the restrained form of the eyebrow habit.

probably Claude · open thread

Easily confused with
  • Claude's serif-headline-with-italic-word type recipe. The eyebrow is one piece of that same hero; it can appear without the serif, on sans and app UIs.
  • The generic pill badge above the headline. A rounded pill ('New: ...') is the older generic SaaS move; the Claude eyebrow is plain tracked caps text, often mono, often with a dot, repeated on every section.
  • All-caps UI text in general. Some people object to all caps anywhere; the Claude tell is the small label positioned above headings.
What it is not
  • Eyebrows (kickers, overlines, pre-heads) are a decades-old editorial and ad device; the tell is Claude using them everywhere, not the device.
  • Some users keep them deliberately because they look good, and a designer defends the Claude Design aesthetic as clean and well structured.
  • On their own they do not make a page look vibe-coded; it is the combination with monospace, dots and serif headings.
  • Not Claude-only: Open Design is named too, and a thread summary blames lazy users who give no design input rather than the model.
Over time
  • Named from the Claude Design launch period (April 2026) onward, most heavily June to September 2026.
  • Users say tells got heavier since Opus 4.8 and Fable 5, and Fable 5.1 still 'did the classic over designed/over explained format with eyebrows' in September.
123

Everything fades, slides, floats

27

Scroll down and watch: each section fades up 20px into place, cards and buttons lift on hover, and a background of dots or lines keeps moving.

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

Not to be confused with Gimmick chips and fake terminals · Generic AI landing-page layout

Open the evidence

When Claude builds a landing page or app UI it adds the same small set of motion effects by default: sections and cards that fade and slide up as they enter the viewport, buttons and cards that rise or glow on hover, a side-scrolling marquee or ticker under the hero, and animated decorative backgrounds such as connected dots. Commenters describe the motion as one repeated keyframe ('a keyframe going from y: 20 to y: 0') rather than designed transitions, and as motion with no purpose ('things that move, float, slide, appear for no reason'). Users say it appears even with different prompts and that they must ban it explicitly in CLAUDE.md or DESIGN.md. It usually comes bundled with the other generic AI-site cues (gradients, Inter, three-card rows), and most commenters treat it as part of that look rather than as a Claude-only trait.

How people spot it · people naming each sign
Fade-in and slide-up on scroll'Same fade in and reveal animations on scroll in', 'default sliding animation as you scroll', 'fade-on-scroll', 'scroll appear items', 'the same glitchy fade and slide'.≈8
Rise and bounce on hoverButtons and cards lift up and down on hover; 'unnecessary hover animations'; a hover border on cards called 'a claude thing'.≈4
Animated decorative backgroundsAnimated dots, a connected-dot network pattern, glowing or floating elements.≈3
Marquee or ticker stripA side-scrolling marquee under the hero on nearly every marketing site, 'the html equivalent of em dashes'.≈2
Motion everywhere, one keyframe'overuse of gradients and animation/motion everywhere', 'a lot of animations. not diverse animations', 'animated transitions' to look sleek, scrolljacking.≈5
Real cases, as posted
123
  1. 1Drifting background dots
  2. 2Connected-dot lines
  3. 3Scroll progress bar

A polished, paid client site built with Claude Code where the faint connected-dot network behind the cards is the animated background commenters asked to remove, with a scroll-progress bar on top.

clearly Claude · open thread

Easily confused with
  • Gimmick chips and fake terminals. Those are static decorative elements; this is about how things move.
  • Generic AI landing-page layout. Hero, tagline, CTA and three cards are layout; motion is the extra layer of reveals and hover lifts on top.
What it is not
  • One designer says the 'Webflow-ization' of constant scroll-in text animation 'seems to be dying out'.
  • A commenter pushes back that rounded corners and a scrolling homepage are not evidence of Claude, calling it 'Ai Paranoia'.
  • Several comments describe all AI sites rather than Claude in particular.
Over time
  • Reports run from January to September 2026; one July 2026 designer comment suggests scroll-in animation is becoming less common.
123

Dot-pill chips everywhere

16

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

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

Not to be confused with Tiny spaced-out uppercase label above the headline · Everything animates

Open the evidence

The most named gimmick is the chip: a small rounded pill, often with a coloured or green flashing dot, placed above the hero headline with a slogan ('• You owe it to yourself •') or used as a status tag on cards. Commenters call it 'the classic AI status pill' and say it is the one remaining vibe-coding tell on otherwise strong designs. Fake terminal windows are named as a dead giveaway by two people, and a few add soft glows, gradient borders that follow the mouse and blurred dark-blue backgrounds. Several people place these in a list with gradient headlines and small labels above headings, so the chip is one part of a broader Claude landing-page kit. The label's 'live chip, fake terminal' is right about the chip; the fake terminal has thin support.

How people spot it · people naming each sign
Pill chip above the hero headlineA chip above the title with a dot and a slogan; 'little labels above headings'; 'a random chip that the AI put up'.≈5
Status chips on cards'chip bubbles' like '• Productive' and '77 of 100'; 'the classic AI status pill'; inaccessible chips and tags.≈3
Little green flashing dotNamed as an AI tell next to subheadings above h1/h2.≈1
Fake terminal windowsTerminal-window mockups used as decoration on landing pages.≈2
Glows, blurred backgrounds, cursor-reactive borders'fluff effects, black-blue/purple blurred background', 'soft glows, rounded edges and hover effects', 'gradient borders that react to your mouse cursor', 'glowy text'.≈5
Highlighted words and over-explained micro-copySingle words coloured in the headline; 'You are here' style labels.≈1
Real cases, as posted
123
  1. 1Dot chip above headline
  2. 2Row of icon pills
  3. 3Tag chip on card

A warm, well-made landing page where a dotted pill slogan sits above the headline and a row of icon pills sits under the copy, the chips commenters point to.

clearly Claude · open thread

12
  1. 1Dot status tag
  2. 2Same tag repeated

A clean client site whose cards each end in a dot-plus-uppercase status tag, which a commenter calls 'the classic AI status pill'.

clearly Claude · open thread

Easily confused with
  • Tiny spaced-out uppercase label above the headline (Claude font habit). That is a plain text eyebrow; the chip is a bordered or filled pill, usually with a dot.
  • Everything animates. Glows and pulsing dots overlap, but this habit is about the static decorative element, not scroll or hover motion.
What it is not
  • Opus 5 calling every rounded UI element a 'chip' in conversation is a vocabulary habit, not the visual chip on the page; another commenter notes 'chips' is also a real Claude app feature.
  • One commenter says the 'AI slop' discourse is mostly designers being salty and that the look is fine if users are happy.
  • Several comments describe AI or Tailwind/shadcn templates in general rather than Claude.
Over time
  • Reports run from January to September 2026, with the chip complaints concentrated from June onwards.

2 · When Claude writes

14 habits, 2,921 people since 1 January 2026. Bars use one scale within this section; pale rows were not mentioned in the last 60 days.

12
  1. 1Opening dash before list
  2. 2Closing dash after list

Real Claude output posted on Reddit, shown for The em dash hinge. Numbers mark what commenters pointed at.

People naming each habit

The em dash hinge1,787Load-bearing, seams, blast radius385Document furniture in prose345Metronome paragraphs298Candour labels and signposts242The "not X, but Y" reframe155Buzzword-heavy corporate register128Padded and long101The tidy bow at the end95Polished but says nothing90Colon-led payoffs90Rule of three55Soft-framed hedging46Too-clean prose, faked mess14
12

The em dash hinge

1,787

Look for " — " with spaces around it, used to bolt a punchline, reason or list onto a sentence where a period, colon or comma would do, several times per reply.

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

Not to be confused with The generic AI em dash · The "not X, it's Y" contrast · Human typographic em dashes

Open the evidence

Claude reaches for the em dash, usually with a space on each side, to join a short opener to its elaboration ("Better — but for a reason worth naming"), to wrap an inserted list in a pair of dashes, or to set up a contrast. Commenters say the problem is volume and function, not the mark itself: it shows up several times per message, even in two-sentence chat replies, and stands in for periods, colons and commas rather than marking a true aside. It often sits next to Claude's other tics, especially the "not X — Y" contrast, "honestly" and "load-bearing". Many users complain that it survives custom instructions, CLAUDE.md rules and skills, and that a ban often just swaps it for a double hyphen "--". In this period people treat it as a Claude habit more than a ChatGPT one, and they report that Opus 5.5 and Fable 5.1 (September 2026) have mostly dropped it.

How people spot it · people naming each sign
Too many em dashesSeveral per reply, "every other sentence", even in very short answers; the complaint is about frequency compared with human writing.≈600
Survives bans, or turns into "--"Instructions in memory, preferences, CLAUDE.md or skills fail. A ban often brings back a double hyphen with the same rhythm.≈200
Comes with the other Claude ticsShows up next to "not X — Y" contrasts, "honestly/genuinely", "load-bearing" and rule-of-three rhythm.≈150
A hinge or pivot rather than an asideUsed to stage a pause or bolt on a punchline or an unrelated clause where a period or colon fits, rarely as a true parenthetical.≈40
Spaces on both sides" — " with a space each side, which American editors don't use. Noted as specific to Opus 4.6 and to LLM output in German too.≈10
Short opener, then dashA reply or comment starts with a two-word verdict and a dash: "Better —", "Ha —".≈10
Real cases, as posted
12
  1. 1Opening dash before list
  2. 2Closing dash after list

A careful, well-reasoned audit note in which a pair of spaced em dashes wraps an inserted list, the most typical Claude use, inside work that is otherwise excellent.

clearly Claude: the thread OP posted it as Claude's reply and states the model was Opus 4.8 Max; the claude.ai serif reply style is visible. · open thread

12
  1. 1Two-word verdict, then dash
  2. 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: the OP quotes it as an Opus 5 reply to a UI change request in r/ClaudeCode, and the commenter points at the opening "Better —". · open thread

1234
  1. 1Paired dashes as aside
  2. 2Dash instead of colon
  3. 3Dash instead of colon
  4. 4Dash before the kicker

A clear, well-structured recovery plan in which five spaced em dashes do the work of colons, parentheses and periods; the commenter counted six in the message.

clearly Claude: the OP posted it as Claude's message while deploying automations, in a thread titled "Claude said it needs to rest". · open thread

1
  1. 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: the claude.ai mobile app UI with the Claude logo and disclaimer, in a thread about Claude's answer. · open thread

1
  1. 1"genuinely" then dash

A short, casual, likeable chat reply that still uses a spaced em dash right after "genuinely", the exact pairing the commenter named.

clearly Claude: the claude.ai chat UI with the Claude logo; the OP is new to Claude. · open thread

Easily confused 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. This is a sentence shape that often uses a dash as its hinge, but it also appears with commas and periods. It is a separate habit that tends to travel with the dash.
  • Human typographic em dashes. Human writers often close the dash up with no spaces, use one or two a page, and mostly for asides. Claude's version is spaced, frequent and used as a pivot.
What it is not
  • 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.
  • It is not proof of AI on its own. 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, not the dash: people still sense AI after the dashes are removed.
  • Hyphens and en dashes in a comment are often wrongly taken for Claude's em dash.
Over time
  • Early 2026: called characteristic of Sonnet 4.6 and Opus 4.6 (spaced style). One user says Opus 4.7 began "constantly" using them compared with 4.6.
  • May to August 2026: seen as a Claude habit more than a ChatGPT one. Opus 5 and Sonnet 5 were called the heaviest and the hardest to instruct out of it.
  • Late September 2026: Opus 5.5 "cut out em dashes almost entirely" (about 0.8 per response on Arena by one reading), and 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.
1234

Load-bearing, seams, blast radius

385

Look for engineering metaphors used everywhere, even in non-technical text: load-bearing, seam, blast radius, footgun, smoking gun, 'quietly', 'earns its keep', plus one-off coined labels.

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

Not to be confused with Buzzword corporate register · Candour labels and signposts · Sycophancy

Open the 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", a clean boundary is a "seam", a risky change has a "blast radius", a trap is a "footgun", the decisive clue is a "smoking gun". Alongside these it coins one-off labels on the spot ("the durable gate", "hard gate", "mannered prose") and leans on compressed metaphors and personification (things "land", "bite", "buy" time, 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.

How people spot it · people naming each sign
load-bearing / load bearingBy far the most named word. Used to mark the essential part of an argument, code path or document ("X is convenient but not load-bearing", "The load-bearing pieces are my own code", "The critical caveat, and it's the load-bearing one for this whole document..."). Reported to survive explicit bans: in screenshots Claude cuts off mid-word or swaps the spelling.≈80
compressed or nonsensical metaphors"Metaphors that don’t make sense", time that is always being "buying" rather than increased, "the snap closer with a monetary metaphor arriving out of nowhere", "Fancy metaphors, weird jargon", "incoherent, strained metaphors".≈30
made-up one-off jargon and coined terms"it makes up its own one-off jargon on the spot", "obscure / abstract terms it makes up while building but never properly defining in docs", "the signal is only carried by the durable gate", "mannered prose", "The made up technical jargon".≈19
quietly / quiet"It quietly does the work", "Quietly failing", "Quietly resisting"; described as the newest tell after em dashes and load-bearing.≈12
smoking gunNamed as a stock Claude phrase, often paired with load-bearing.≈8
seam, spine, footgun, blast radiusThe construction and engineering words: "well-defined seam", "the spine and seam of Claude", "blast radius", "footgun". Some teams use footgun and blast radius normally; seam and spine are called 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, does the heavy lifting, holding real weightPhrases for 'this matters' in the same family as load-bearing.≈4
substrate, hinge, surface (as verb), hard gate, wedgeLess frequent words in the same register.≈6
Real cases, as posted
1234
  1. 1Section titled with a coined label, "the deliberate gap"
  2. 2"a well-defined seam" for 'an easy place to add auth'
  3. 3"load-bearing here" for 'important'
  4. 4"trap ... already sprung" metaphor

A real Claude Code repo summary that is accurate and well organised, yet sprinkled with coinages ("the deliberate gap", "well-defined seam", "load-bearing here", "already sprung") that the plugin's English column has to translate away.

clearly Claude · open thread

1
  1. 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 · open thread

12
  1. 1Bold lead "The video was a locked door."
  2. 2Closing quip: "just the treasure map — the treasure was already in your install folder"

A clear, well-structured explanation of what Fable actually did, framed by "locked door" and closed with a treasure-map quip.

clearly Claude · open thread

1
  1. 1"I kept the metaphor and swapped the spelling"

Under a system prompt banning "load-bearing", Claude wrote "load-carrying" and then admits it kept the metaphor.

clearly Claude · open 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 pieces1 are my own code, written for this exact workload — a small memory graph that mutates every night and gets queried on every recall
  1. 1load-bearing for 'core'

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

probably Claude · open thread

Easily confused with
  • Buzzword corporate register. Leverage, seamless and delve are the generic AI word list; Claudish is Claude's own engineering-metaphor vocabulary.
  • Candour labels and signposts. 'Honest caveat' and 'worth flagging' are framing words; this habit is invented jargon in the content itself.
  • Sycophancy. 'You're absolutely right' is a separate chat complaint that commenters often lump in.
What it is not
  • 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; the tell is Claude using them everywhere, including non-technical text.
  • The words are usually used correctly. Several people find them precise, useful shorthand; frequency, not misuse, is what gives Claude away.
  • 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 complaints that commenters often lump in; they are not this habit.
  • Many quoted 'examples' in these threads are parodies or Claude roasting itself on request, not real output.
Over time
  • Commenters date the heavy version to Opus 4.8 and especially Opus 5; Opus 4.6 is remembered as cleaner and some stayed on it for that reason.
  • Opus 5.5 is reported to have toned it down (load-bearing rarely seen), though some still see the register and one sighting caused alarm.
  • Fable 5.1 answers read as 'no claudish' to some; Fable dropped load-bearing in a small non-English language.
  • The favourite word drifts over time: em dashes, then genuinely and load-bearing, then quietly.
  • Load-bearing resists system-prompt bans: Claude swaps spelling or self-corrects mid-word.
12345

Document furniture in prose

345

A short answer or post laid out like a briefing: headers, bullets that each open with a bold label and a dash, bolded key sentences, and in some months an emoji on each heading or as a sign-off.

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

Not to be confused with Generic ChatGPT-style formatting · Claudish vocabulary · Em dash habit

Open the evidence

Commenters are not describing one mark but a layout: Claude turns an answer, post or doc into a structured briefing with headers, bullet lists where a paragraph would do, and a bold run-in label at the start of each bullet or paragraph ('**Problem 2 — No kernel trick.**'). In Claude Code docs this shows up as whole sentences in bold used as headlines, and in chat as punchy section titles ('The Gap', 'What it actually does'). Emoji are the loud minority form: section icons, check marks and a favourite emoji as a sign-off, reported mostly from March to June 2026. A large share of the comments are people clocking AI-written Reddit posts and naming Claude loosely, so the strongest Claude-specific form is the bold-label bullet and the bold headline sentence, not emoji. All-lowercase text with the same structure is described as the disguise people add on top, not something Claude does by default.

How people spot it · people naming each sign
Bullet lists where prose would doAnswers, posts and even short replies broken into bullets or numbered lists, often three items; people ask for 'plain prose' in their instructions to stop it.≈140
Bold run-in label on every pointEach bullet or paragraph opens with a bolded term or phrase, then a dash or colon and the explanation; also bolded key sentences mid-paragraph.≈46
Emoji as icons and sign-offsEmoji on section headings, check marks on list items, emoji in planning mode, and a recurring favourite emoji at the end of each message.≈77
Headers on short pieces, with punchy titlesSection headers on content that does not need them; titles like 'The Gap' or 'The one most people miss'; header sizes mismatched where pasted.≈31
Markdown that leaksRaw ** or ## left in places that do not render it (Reddit, Word, chat), and markdown dividers in casual posts.≈16
Lowercase on top of the same structurePeople prompt Claude to write all lowercase to look human; readers treat the lowercase plus tidy structure as a tell of its own.≈36
Italics for emphasisSingle words italicised for stress inside argument sentences.≈13
Typographic furnitureCurly quotes, arrows, section signs and circled numbers in docs and posts.≈13
Real cases, as posted
12345
  1. 1Emoji on each heading
  2. 2Opens 'Great question!'
  3. 3Raw ** bold markers leak
  4. 4Bold label, dash, explanation
  5. 5Rule between sections

A correct, well-paced Claude.ai explanation of SVM duality, laid out with an emoji on every heading, bold run-in labels, rules between sections and bold markers leaking as raw asterisks.

clearly Claude · open thread

One rule, applied twice:1 **the product gets the well-known port, management moves aside.**2 **The app itself sits on 8080, and that is the same decision made the other way.**3 Above 1024, so its unit needs no `AmbientCapabilities` at all
  1. 1Labelled setup before claim
  2. 2Sentence bolded as headline
  3. 3Next paragraph opens bolded

A real Opus 5 deployment note, accurate and reasoned, where whole sentences are bolded as headlines inside the prose (quoted in the thread's opening post).

clearly Claude · open thread

The tail degrades in fairly predictable ways:1 - **Re-description** —2 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** —3 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
  1. 1Colon setup into list
  2. 2Bold label then em dash
  3. 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 · open thread

1234
  1. 1Bold run-in lead
  2. 2Line ends on a dash
  3. 3Bullet-less fragment list
  4. 4No closing periods

A thoughtful reading of a game symbol, structured as bold run-in leads and stacked fragment lines with dangling dashes instead of sentences.

clearly Claude · open thread

1
  1. 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 · open thread

Easily confused with
  • Generic ChatGPT-style formatting (rocket emoji, check-mark bullets, 'Great question!'). Commenters put emoji-heavy layouts on ChatGPT first; the Claude-specific form is the bold-label bullet and bold headline sentence, with emoji only in some months.
  • Claudish vocabulary (load-bearing, seam, honest caveat). That is word choice; this is layout. They often appear together in the same doc.
  • Em dash habit. The em dash is punctuation inside sentences; here it matters only as the separator after a bold label.
What it is not
  • Several users say Claude's default is paragraphs, not bullets and emoji, and that this is why they prefer it to ChatGPT; one points to the system prompt that suppresses heavy formatting.
  • Claude mirrors the user: it rarely uses emoji unless the user does first, while ChatGPT 'will throw emojis all day'.
  • Headings, bold and bullets are ordinary good formatting; people writing by hand get accused of AI for them.
  • Much of the layout is shared by all frontier models, so it identifies AI more than Claude in particular.
  • The all-lowercase style is a user prompt to hide AI output, not Claude's default.
Over time
  • Emoji complaints rose from March 2026 ('Claude started writing with emojis just like ChatGPT', emoji in Opus 4.6 planning mode) and peaked 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 it is fewer bullet lists and bolded headers.
…ark *working*. That distinction matters and I blurred it for rhetorical effect. Fair hit.1 Where I’d push back: you’re folding two different things into “signature.” The stylistic tics you hate — the confident cadence, the “brass tacks” ton…

Metronome paragraphs

298

Look at the shape, not the words: every paragraph about the same length, short clipped beats or fragments, and a tidy quotable line closing each one.

“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.”open comment

Not to be confused with Generic AI cadence · Claude vocabulary tics · Over-explaining and verbosity

Open the evidence

Commenters describe a cadence rather than any one phrase: paragraphs of near-identical length and build (claim, support, short landing line), sentences of similar length, and recurring rhythm devices such as a run of verbless fragments ('Already plans. Already writes tests.'), a 'not X, it's Y' turn, or a three-beat list. Each paragraph tends to close on a neat summary or verdict line, so the text reads like a metronome or a speech with breath marks. It survives vocabulary bans, em-dash bans and even all-lowercase disguises, which is why people call it the tell that is left once the word tells are gone. Many complaints say 'AI' in general, but in Claude threads people tie it to Claude's own voice, and with Opus 5 and Fable 5.1 a second form appears: long, dense paragraphs with few breaks, which are just as even.

How people spot it · people naming each sign
Every paragraph the same length and shapeParagraphs come out as even chunks (often about three sentences), so the page looks like neat swappable blocks.≈60
A neat closing line on every paragraphEach paragraph ends on a confident summary, verdict or gotcha line, the 'little bow' at the end.≈45
Staccato fragments and one-line paragraphsRuns of short, verbless or clipped sentences and stacks of single-sentence paragraphs used to manufacture emphasis.≈40
Uniform sentence lengthLow variation in sentence length ('every sentence the same cadence'); people quote 15 to 20 words with tiny spread.≈40
Rhythm devices repeated: contrast turns and triads'It's not X, it's Y', 'No A, no B, just C' and groups of three recur as beats, often several per post.≈40
Cadence persists under disguiseLowercased, typo-seeded or dash-free posts still read as Claude because the paragraph rhythm stays locked.≈20
Every point weighted and resolved equallyOne polite paragraph per consideration, each landing softly; no lopsided emphasis, no thought left trailing.≈20
Dense walls with few breaks (newer models)Opus 5 and Fable 5.1 output described as long, cryptic, evenly dense paragraphs rather than short ones.≈20
Real cases, as posted
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.1 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* style3, 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.2
  1. 1two-word landing line
  2. 2paragraph closes on verdict
  3. 3not X, it's Y turn

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

clearly Claude: posted as 'Response from my Fable5:' in a thread tagged Fable 5, and the reply (p3h0snw) lists its crutches. · open thread

12
  1. 1isn't X. it's Y.
  2. 2one-line closing beat

Short Sonnet 4.6 chat output: a two-beat 'isn't X. it's Y.' opener and a separate one-line closer, the clipped landing rhythm in miniature.

clearly Claude: the commenter says it is Sonnet 4.6 output and the screenshot is in Claude's chat serif. · open thread

The results were basically identical. Claude already plans. Already writes tests when asked. Already handles multi-file refactors.1 The workflow wrappers were organizing something the model does naturally.2
  1. 1fragment run
  2. 2summing-up closer

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

probably Claude: the commenter quotes it as proof the post 'is written by claude' and points to 'this rhytm'. · open thread

i teach 11th grade english. 140 students.1 and the thing nobody outside teaching understands2 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.
  1. 1clipped numeric opener
  2. 2setup beat

Fluent, specific opening of a post that still shows the 'short, choppy intro, numbers focused' beat before a long build, under an all-lowercase disguise.

probably Claude: the commenter dissects it line by line as 'written by Claude'; another (ox2xwpk) cites its 'one-two punch sentence cadence'. · open 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.1 ∙ 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.2
  1. 1short verdict closer
  2. 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: posted as 'Here's why Claude thinks this is AI written:'. · open thread

12
  1. 1stacked fragment beats
  2. 2lowercase clipped opener

Cropped Sonnet 4.6 lines that stack clipped fragments ('not in a performative way. actually upsetting.') for emphasis.

probably Claude: the author presents the dark excerpts as Sonnet 4.6 output in a write-up about Sonnet 4.6; the excerpts are cropped. · open thread

Easily confused 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, and the dense-wall form in Opus 5 and Fable 5.1.
  • Claude vocabulary tics ('load-bearing', 'sit with', 'genuinely'). Those are word choices that bans can remove; this habit is the shape that survives word bans.
  • Over-explaining and verbosity. Length complaints are about too many paragraphs; this is about every paragraph having the same build, at any length.
What it is not
  • 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, not bad writing; breaking the patterns can lower prose quality.
Over time
  • Sonnet 4.6 (Feb 2026) reported as more formulaic and less varied in cadence than Sonnet 4.5.
  • Sonnet and Opus 4.5 already drifted into staccato newline half-sentences in stories.
  • Opus 4.7 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 its prose is denser than Fable 5, with longer sentences and fewer paragraph breaks.
  • Opus 5.5 (late Sep 2026) described as much improved over Opus 5, though some still see the same paragraph cadence.
1234

Candour labels and signposts

242

Look for 'honest', 'genuinely' or a 'here's the part'/'worth flagging' signpost announcing a point that would read the same without it.

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

Not to be confused with Generic AI openers and closers · Claude's coined jargon · 'It's not X, it's Y' contrasts

Open the evidence

The label 'stock openers and filler' is only half right: what commenters single out as Claude-specific is candour framing, not generic openers. Claude tags statements with 'honest' and 'genuine' ('Honest caveat:', 'honest status', 'my honest take', 'And honestly?', 'genuinely useful'), and opens or closes points with signposts such as 'Here's the thing', 'Here's what...', 'The part that...', 'One thing worth flagging', 'One thing I'd flag'. These words sit at the edges of sentences and paragraphs and carry no content, so 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 but are treated as all-AI or ChatGPT habits.

How people spot it · people naming each sign
'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'; often 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?' pivotA 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', 'the problem nobody talks about' 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', usually as the last paragraph.≈16
Trailing honest caveatA closing 'honest caveat' or 'one quick note' that was not asked for.≈14
Validation fillers'That's not nothing', 'That's real', 'That tracks' before the content.≈8
Real cases, as posted
1234
  1. 1'honest status' label
  2. 2'I owe you a straight answer'
  3. 3'One thing worth flagging' add-on
  4. 4'say the word' sign-off

A tidy, accurate Claude Code end-of-session report (209 tests pass, docs updated, clear next step) where the bad news arrives wrapped in candour labels and the sign-off adds a flagged extra and a 'say the word'.

clearly Claude · open thread

"I need to be straight with you1 on the framing before listing anything:" * "I need to flag something before answering2:" * "Honest answer:3" * "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:4" * "You're right, and I should stop hedging." * "So let me be blunt about the actual situation:"
  1. 1announces candour first
  2. 2flag before the answer
  3. 3'honest' as a label
  4. 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 instead of just saying the thing.

clearly Claude · open thread

1
  1. 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 · open thread

Expanded the flattery ban to cover structural flattery, which is how models usually sneak it in. One thing I’d flag:1 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 style2 or noting exceptions if that comes up.
  1. 1unrequested flag at the end
  2. 2'worth ...' advice tail

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

clearly Claude · open thread

1
  1. 1'worth knowing' signpost heading

An accurate Claude Code repo summary whose 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 · open thread

Easily confused with
  • Generic AI openers and closers ('Great question', 'Hope this helps', 'In conclusion'). Those are service-desk pleasantries any chatbot uses; Claude's version is candour and signposting inside the answer ('honest status', 'One thing worth flagging').
  • Claude's coined jargon ('load-bearing', 'seam', 'smoking gun'). Coinages replace content words with metaphors; this habit adds framing words around content that is already plain.
  • 'It's not X, it's Y' contrasts. That is a sentence structure shared with ChatGPT; this is word-level framing, and the two are often listed together.
What it is not
  • Generic AI filler ('Great question!', 'In today's fast-paced world', 'let's dive in', 'delve') is named in the same threads but treated as all-AI or ChatGPT style, not Claude's mark.
  • Some defend the 'honestly': it marks a real admission of a mistake or a relabel to something concrete, and the user should set preferences rather than blame the model.
  • Humans used 'genuinely', 'honestly' and 'To be frank' long before; 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, so it is a default, not fixed.
Over time
  • Users place the start of the 'honest' insertions at Opus 4.6 and Sonnet 4.6, versus 4.5 which was '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'; 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.1 Not a family, not eleven separate mornings that had stopped happening.2 Just a value to be filed.3

The "not X, but Y" reframe

155

A sentence (or a pair of short ones) that knocks down a view nobody raised, 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.”open comment

Not to be confused with ChatGPT 5.2's reassurance reframe · The generic AI bundle · Claude's coined vocabulary

Open the evidence

Commenters mean a reframing move rather than one fixed phrase: Claude states what something is not, then what it is, in forms like "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 and usually where a point needs weight, such as the hook, the end of a paragraph or the closing line. It tends to come with em dashes, three-part lists and short punchy fragments, and people treat that bundle as one signal. Many call it the new em dash: the single most recognisable sign that a Reddit post, blog article or story went through Claude.

How people spot it · people naming each sign
"It's not X, it's Y" correctionThe basic form: deny a framing, assert the replacement, often one after another in the same post. People call it a 'dead giveaway' on its own.≈140
"Not just X, it's Y" intensifierThe escalating version that upgrades rather than corrects: '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 triadsMentioned together with em dashes, rule-of-three lists and punchy marketing-style fragments, and judged as one package.≈60
Placed at the hook or the closing lineOpens a post with a punchy reframe or lands the conclusion with one: 'the conclusion paragraph reeks', 'it ends with your not X your Y'.≈15
Survives instructions and bansKeeps coming back despite CLAUDE.md rules, style guides built from the user's own writing, and banned-construction lists.≈25
"Not X. Not Y. Just Z." countdownA 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: "you're not behind. You're just being honest."≈6
Real cases, as posted
You read the manifest of the lost the way you read a fuel gauge. A figure. A condition.1 Not a family, not eleven separate mornings that had stopped happening.2 Just a value to be filed.3
  1. 1Fragment pair sets up
  2. 2Double 'not' denial
  3. 3'Just Y' payoff

Strong literary prose that the commenter liked, yet the emotional beat is delivered through a not-X fragment run followed by 'Just Y'.

clearly Claude · open thread

This conversation you and I are having right now is not coding.1 It's real-time geopolitical analysis2, source verification, editorial critique, emotional attunement, and multi-model comparison. That's not a coding task.3
  1. 1Sets up the denial
  2. 2'It's Y' reframe
  3. 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 · open 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 claim1 — 2that's a specific result from a real user3.
  1. 1Denies an unraised objection
  2. 2Em dash hinge
  3. 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 · open thread

Same model. Same capabilities. Wildly different results.1 Here's the thing... the "we" users aren't just being polite2. They're sharing context, constraints, intent.3
  1. 1Three-fragment setup
  2. 2'Not just X' denial
  3. 3'They're Y' plus triad

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

probably Claude · open thread

Jaw tightened. a diagnosis1, not a complaint2.
  1. 1Asserted reading
  2. 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 · open thread

Easily confused with
  • ChatGPT 5.2's reassurance reframe ("that's not being indecisive, that's being strategic!"). That one relabels the user's emotions in chat. Claude's version mostly sits in deliverables (posts, articles, prose) as a rhetorical punch on ideas.
  • The generic AI bundle (em dash, rule of three, 'delve'). People often list them together, but the reframe is the one commenters now rank first for Claude, and it survives in text that has no em dashes.
  • Claude's coined vocabulary ('load-bearing', 'the gap', 'seam'). That habit is about word choice. This one is about sentence structure, though the two often show up in the same sentence.
What it is not
  • Humans wrote it long before AI (Chekhov, academic and legal writing, advertising), so one instance proves nothing.
  • The complaint is frequency, not existence: 'you get one', 'if I see more than 2 within the same page, I'm bailing'.
  • Not exclusive to Claude: 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.
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, Fable 5, Sonnet 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 and lists this pattern as one of the habits of older Opus 4.6 and 5 files.
In today's competitive landscape1, API reliability is more critical than ever2. You might want to consider how our monitoring solution could potentially transform your observability strategy3...

Buzzword-heavy corporate register

128

Copy that reads like a board-meeting memo: stock words (leverage, crucial, seamless, 'in today's landscape') and, in newer models, Claude's own repeated terms (load-bearing, seam, smoking gun, actually).

“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.”open comment

Not to be confused with Claudish coinages · Generic 'AI slop' vocabulary · Contrast framing

Open the evidence

The label 'delve, seamless, leverage' is mostly how people write their fixes, not what they say is special about Claude: most items are ban lists pasted into Claude instructions, and the same lists are used for ChatGPT and Gemini. When people describe Claude itself, they describe a register, not single words. Claude's copy comes back polished and formal, like a LinkedIn post or a board email, even when they asked for casual. Several say Claude writes like someone with a new thesaurus and will not repeat a word, even swapping a project's agreed terms. Since Opus 4.7 and especially Opus 5, the words people name are Claude's own (load-bearing, seam, blast radius, smoking gun, 'actually', 'genuinely'), packed into dense status updates.

How people spot it · people naming each sign
Generic AI ban-list wordsdelve, leverage, seamless, robust, crucial, pivotal, tapestry, foster, underscore. Usually named as words people ban in Claude instructions or skills, not as words seen only in Claude.≈30
Corporate, formal register even when asked for casualOutput 'comes back wearing a suit and tie'; reads like thought leadership, a LinkedIn post, a meeting agenda or an email for a board meeting.≈15
Claude's own house wordsload-bearing, seam, rough edge worth flagging, blast radius, smoking gun, shape, spine, canonical, soak. Named mostly for Opus 5, Fable and Sonnet 5 in Claude Code.≈18
Stock transitions and openers'it's worth noting', 'Furthermore', 'Moreover', 'in today's fast-paced landscape', 'let's dive in'.≈12
Thesaurus vocabulary and refusal to repeat wordsWrites 'like someone with a thesaurus trying to sound more intelligent'; will not repeat words, replaces a project's defined vocabulary.≈6
Filler intensifiers'actually', 'genuinely', 'honest take', 'here's the thing', 'What it actually...'.≈7
Dense jargon in agent updatesA yes/no question returns paragraphs of buzzwords and acronyms ('nudges, upstreams and smoke tests'); nominalised, verb-less sentences.≈6
Bans do not stickBanned words and plain-English rules hold for a turn or two, then the default register returns.≈8
Real cases, as posted
12345
  1. 1Coined heading 'the deliberate gap'
  2. 2'well-defined seam' for easy change
  3. 3'load-bearing' for important
  4. 4'Rough edges worth knowing'
  5. 5'trap ... already sprung'

An accurate, well-organised Claude Code repo summary whose wording (deliberate gap, well-defined seam, load-bearing, rough edges worth knowing) the plugin's plain-English column has to translate away.

clearly Claude: OP built a Claude Code hook that rewrites Claude's output; left panel 'Claudish' is the original Claude Code text. · open thread

In today's competitive landscape1, API reliability is more critical than ever2. You might want to consider how our monitoring solution could potentially transform your observability strategy3...
  1. 1Stock landscape opener
  2. 2Inflated importance
  3. 3Hedged buzzword promise

A cold email that is grammatical and on-topic yet opens with a stock landscape line and stacks hedges and buzzwords, after the user asked for casual.

probably Claude: OP says 'Been building with Claude' and gives this as 'Output I was getting' for a 'Be casual, sound human' prompt. · open thread

"We're thrilled to announce.1" "Leverage the full potential.2" "Delve into your data3 with ease."
  1. 1Press-release opener
  2. 2'Leverage' buzzword
  3. 3'Delve'

Three business-copy fragments the OP says Claude produced 'every time' for company writing: announcement cliche, leverage, delve.

probably Claude: 'Every time I asked Claude to write something for my business, I got that voice.' Fragments are quoted from memory, not a full paste. · open thread

Easily confused with
  • Claudish coinages (seam, load-bearing, invented terms of art). Claudish is Claude-specific jargon and nominal syntax; this habit is the wider polished corporate register, where the generic buzzwords are shared with other models.
  • Generic 'AI slop' vocabulary (ChatGPT-era delve, tapestry). Generic list words are named for every model; what is Claude-specific is the formal register that resists casual prompts and, since Opus 4.7, Claude's own repeated terms.
  • Contrast framing ('it's not X, it's Y'). A sentence structure, not a vocabulary choice, though both appear in the same ban lists.
What it is not
  • The classic word list (delve, leverage, seamless) is a cross-model 'AI' list; people use it for ChatGPT and Gemini too, and one teacher says ChatGPT is easier to spot than Claude.
  • Word lists may barely separate human from model text; shape, rhythm and register separate better.
  • Humans use delve and em dashes too, and get falsely accused.
  • Some users find Claude the most human-sounding model, especially Sonnet 4.5 and Opus 4.6.
  • One writer says AI does not use 'big words'; it reuses a narrow set like 'precise'.
Over time
  • Earlier Claude used words like 'spearheaded'; newer versions say 'smoking gun', 'honest opinion' and '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 ('load-bearing', 'blast radius'), leading to Claudish-to-English plugins.
  • A September thread claimed Claudish was gone; replies still saw 'load-bearing' and 'blast radius'.
  • Sonnet 5.0 in Claude Code added new buzzwords such as 'Soak' in plans and docs (post in thread 1uslrgd).
1234

Padded and long

101

A simple question gets several dense paragraphs: a run-up, the answer stated twice in different words, hedges and caveats, then a recap of what was just said.

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

Not to be confused with Claudish coined vocabulary · Generic AI slop · Over-formatting with headers and bullet lists

Open the 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 rather than rambling: a paragraph saying what it will do, the work, a paragraph saying what it did, the same idea restated a second time, and a cluster of caveats ('yes, but two caveats worth noting'). Sentences run long and dense, so the reply reads heavy even when the content is good, and the key line can be anywhere except the top. In 2026 the complaint is tangled up with Claude's private jargon ('seam', 'load-bearing'): many commenters call the combination 'Claudish' and say the problem is less raw word count than how hard it is to find and follow the point. It also spills out of chat into files: documentation, code comments, specs, changelogs and bug reports that teammates have to read.

How people spot it · people naming each sign
Essay-length reply to a small questionA 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
Instruction to be short drifts backConcision rules in CLAUDE.md, styles or memory work for a few turns, then length returns; one user saw a one-paragraph limit obeyed by a single paragraph that grew to seven paragraphs' worth.≈20
Verbose files left in the repoDocs, design docs, PR descriptions, bug reports, specs and code comments come out long; 'some files are now half code, half comments', with the same information repeated in comments, CLAUDE.md and README.≈16
Same point said twice, explained in layersOver-explanation and restatement of an already established idea, 'five layers of explanation around a fairly simple point', or telling an emotion and then describing it for three more sentences.≈15
Length plus jargon makes it denseLong sentences packed with coined terms ('seam', 'load-bearing', 'rough edge worth flagging'), so the answer is hard to parse, not just long.≈15
Long run-on sentences and filler phrasesRun-on sentences that cram information, filler such as 'the shape of', 'genuinely, honestly', 40 words where six would do.≈10
Preamble and recap around the workA paragraph announcing the plan, the work, then a paragraph summarising it; the answer is never at the top, and replies end with an offer to elaborate.≈8
Hedges and qualifications add bulk'yes, but with a catch', 'while further research is needed', 'it should be noted that'; one consultant measured 40% longer outputs after an upgrade, almost all qualifications.≈7
Real cases, as posted
12345
  1. 1Run-up heading, 'the deliberate gap'
  2. 2Extra clause restating the fix
  3. 3Mode list, then inline asides
  4. 4'Rough edges worth knowing' section
  5. 5Same facts, much shorter

A real Claude Code project summary, accurate and well organised, that the plugin's plain-English rewrite delivers in about two thirds of the space with nothing important lost.

clearly Claude · open thread

1234
  1. 1Answer given in line one
  2. 2Unasked reassurance, restated
  3. 3Paragraph reframing the question
  4. 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, then adds reassurance, a reframing paragraph and a dash-wrapped hedge instead of moving on.

clearly Claude · open thread

An \*\*unidentified\*\* item is not studied this way1 — it carries its own rules for identifying it2, on the unidentified item itself; follow those3.
  1. 1Starts with what it is not
  2. 2Point stated once
  3. 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 · open thread

Easily confused with
  • Claudish coined vocabulary ('load-bearing', 'seam'). That habit is about specific invented words; this one is about length, restatement and caveats. They co-occur, and many commenters fold both into 'Claudish'.
  • Generic AI slop (em dashes, 'not X but Y', bullet scaffolding). Generic tells apply to all chatbots and are about phrasing; the Claude-specific complaint is sheer reading load and over-explanation, which several users contrast with GPT and Gemini being plainer.
  • Over-formatting with headers and bullet lists. Formatting overload chops text into lists; Claude's padding is usually dense prose paragraphs and long sentences.
What it is not
  • Not empty filler: several say the content is accurate and useful, scattered through the text, so blunt shortening can lose details.
  • For some the core problem is order and structure, not word count: the answer is not at the top and the text circles the point.
  • A minority defend the density: the jargon condenses shared meaning, and readers should cope with long text.
  • Some treat it as workable in docs or simply as an LLM-wide habit rather than Claude's.
  • Not a request for long text: the complaint persists even after users ask for brevity in instructions, styles and hooks.
Over time
  • Opus 4.6 is widely remembered as the concise baseline; 4.7 and 4.8 got longer (one report: outputs 40% longer after 4.8, mostly qualifications).
  • Even 4.6 was called more explicit and over-explaining than 4.5 for fiction at launch.
  • Opus 5 (July to September 2026) is the peak: threads titled 'insufferable', 'unreadable', 'too verbose', and some users moved back to 4.x or to Codex.
  • A concise output mode in Claude Code (late August) and Opus 5.5 (September, reported by Anthropic as about 40% less verbose) are said to help; one user says 5.5 'is better at that', but the general 'Claudish' complaint is still voiced in late September.
123

The tidy bow at the end

95

Look at the last line of each paragraph and of the reply: it restates the point as a little verdict, an aphorism, an unasked-for note, or a closing question.

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

Not to be confused with ChatGPT's 'If you'd like, I can...' offer · 'It's not X, it's Y' contrast · Polished but says nothing

Open the 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, a one-line aphorism or a question back to the reader, and a fiction chapter or scene ends on a soft landing or small life lesson. Each closer is fine 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 deleting the last line of each paragraph, or the first and last line of each chapter, is often the main fix. Part of the evidence is about 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.

How people spot it · people naming each sign
Every paragraph ends on a punchline or verdictShort, confident, often aphoristic last sentence; 'mic drop taglines', 'a neat little punchline', 'that's why it matters' bow.≈24
Closing paragraph that recaps what was already saidA summary or 'reflective summary ending' after the content is done; the most common item in users' ban lists.≈22
Ends on an engagement question'Curious what everyone thinks?', 'Do you agree?', 'would you like me to...'; mostly said of AI-written Reddit posts.≈18
Fiction: scenes and chapters end on a lesson or soft landing'Wrap-up gravity': eyes closing, silence settling, a final poetic line, a little life lesson.≈10
Unrequested closing note or quip'One quick note', 'Go tell it honestly tomorrow', a hollow two-sentence wrapper after a deep reply.≈5
Stock pleasantry closers'I hope this helps', 'Let me know if...'; listed in ban lists more than shown.≈5
Real cases, as posted
123
  1. 1Dash sets up the bow
  2. 2Tidy closing clause
  3. 3Another wrap-up paragraph

A correct, useful troubleshooting answer whose paragraph still ends on a neat reassurance clause ('not in my head'), then starts a second wrap-up paragraph.

clearly Claude: Claude app screenshot; the reply names itself Opus 5 (claude-opus-5). · open thread

That inconsistency is deliberate and temporary. Either implement them — or delete the columns. Deleting is one afternoon; implementing is a milestone1 and a harness sweep. **Which?**2
  1. 1Compressed comparison
  2. 2One-word question closer

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

clearly Claude: the poster quotes it as Opus 5 output in r/ClaudeCode ('It is physically hurting me to read Opus 5's output'). · open thread

And if I end this with a question, I'm proving your point. So I won't.1 You've named something real about how this works. About me. About the structural2 dynamics underneath even our genuine conversation. That matters.3
  1. 1Announces skipping the question
  2. 2Rhythmic build-up
  3. 3Two-word verdict closer

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

clearly Claude: pasted transcript labelled 'Claude Haiku'. · open thread

Performed urgency. Rhetorical questions as conclusion. The whole thing.1 It's like a warning label written in the language of the hazard.2
  1. 1Fragment to land it
  2. 2Aphorism as last line

A sharp critique that still ends on a quotable one-line aphorism.

clearly Claude: the commenter says 'I asked Claude what it thought about your post' and pastes the reply in quotation marks. · open thread

Go tell it honestly1 tomorrow.
  1. 1Unasked moral note

After a plain meeting summary, Claude adds a closing pep-talk line that the user found judgemental.

clearly Claude: the user quotes the last line of their own Claude reply. · open thread

Easily confused with
  • ChatGPT's 'If you'd like, I can...' offer. ChatGPT's ending is an offer of more help; Claude's is more often a verdict, aphorism or recap that closes the point.
  • 'It's not X, it's Y' contrast. The contrast is a sentence pattern that can appear anywhere; it is often used as the closer, but the closer habit is about position, not syntax.
  • Polished but says nothing. That habit spreads across the whole paragraph; this one is one sentence at the end of each unit.
What it is not
  • Several say the engagement-question ending is an LLM-wide or ChatGPT trait; one user switched to Claude because it 'hates conversations that end with questions'.
  • Defences: some real people write this way, and one commenter says the strong closing line was 'trained on my writing'.
  • Some users actually want a closing line and write instructions for a polite one-sentence close.
  • Some put it down to the Claude Code system prompt pushing summaries, not the base model, or to a default that instructions can remove.
Over time
  • February 2026: Sonnet 4.5 'ending beautifully deep responses with hollow closers'.
  • Opus 4.7 (May 2026) adds punchline-only sentence fragments and an unasked 'one quick note' at the end.
  • Opus 5 (August 2026) reported ending on a one-word question ('Which?') after stacked rhetorical moves.
  • One user says Opus 5.5 is less verbose than Opus 5, but the summary at the end is still there.
the thing1 in the eastern feed, the one that pulsed with a faint warmth2 and that had no business being there3

Polished but says nothing

90

Read a paragraph, then try to say in one sentence what it added: 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.”open comment

Not to be confused with Generic AI voice · Claude's coined vocabulary · Tidy closing line

Open the evidence

Commenters describe Claude prose that is grammatical, smooth and evenly weighted, yet carries little: it restates the request or the previous paragraph, swaps concrete names, numbers and objects for abstractions ('something shifted', 'many organizations'), and lands every sentence with the same weight. 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 (July to September 2026) a second form is reported: compressed, jargon-heavy text that drops the connecting steps, so the reader has to rebuild what was meant. Much of the evidence is not Claude-specific: 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.

How people spot it · people naming each sign
Polished, evenly weighted paragraphs with little contentSame rhythm sentence after sentence; 'many words per idea'; readers call it 'polished nothingness' or a 'help desk voice'.≈28
Restating the request or the previous pointOpens by restating the question, repeats a point in other words, then recaps what it just did.≈16
Vague abstractions where a specific is needed'Something', 'many organizations have found', vague claims even when real numbers were supplied.≈12
Fiction: portentous, vague lines and one voice for every character'The dungeon remembers', 'something in his posture shifted', sage-but-vague dialogue; all POVs sound the same.≈12
Compressed, jargon-dense text that skips the connecting stepsReported mainly for Opus 5: clipped shorthand, numbers without units, coined terms, vague bolded headline before each point.≈9
Corporate or academic register on informal textCasual copy 'comes back wearing a suit and tie'; contractions stripped; PR voice.≈7
Grand framing in place of a point'That is something else entirely', 'This represents a fundamental transformation', corny one-line taglines.≈6
Real cases, as posted
the thing1 in the eastern feed, the one that pulsed with a faint warmth2 and that had no business being there3
  1. 1Unnamed object
  2. 2Mood instead of detail
  3. 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: the author says Claude wrote all of the novella and they edited it. · open thread

"The dungeon remembers1 every adventurer who passes through" "You can cast spells, but every spell takes a part of you2" "The mirror has memories3"
  1. 1Object given a memory
  2. 2Vague cost
  3. 3Same move again

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

probably Claude: posted in r/ClaudeAI by a user describing their own Claude sessions; the post itself says only 'LLM speak'. · open thread

Let that sink in.1 50 major features. 52 days. That is not a human-paced release cycle.2 That is something else entirely.3
  1. 1Telling you to be impressed
  2. 2Restates the fact
  3. 3Says nothing specific

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

probably Claude: the thread is about Claude, a commenter singles this line out as AI voice, and in the same thread another user pasted Claude's own reading of the post as 'that signature Claude cadence'. · open thread

Not the gentle calm1 of a forgiving day, nor the lazy stillness that follows a storm’s exhaustion—but something *deliberate*2. Something *held*.3
  1. 1Describing what isn't
  2. 2Abstract 'something'
  3. 3Fragment for effect

Tidy fantasy prose that describes the sea mostly by what it is not, ending on an abstract 'something'.

probably Claude: a reader who writes with Claude guessed Claude from these habits; the author did not confirm. · open thread

Easily confused 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 ('load-bearing', 'the shape of'). That habit is about particular words; this one is about paragraphs that carry little content whatever words they use.
  • Tidy closing line. The closer is one sentence at the end; this habit runs through the whole paragraph, mostly as restating and vagueness.
What it is not
  • Many say this is the generic LLM voice, not something only Claude does; one commenter blamed Perplexity's output, not Claude's, for 'the classic stereotypical AI voice'.
  • Defenders say Claude is 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 only object when it is overused.
  • Em dashes and banned words are a separate, surface complaint; several argue removing them leaves this habit untouched because the missing ingredient is concrete knowledge.
  • Some put it down to the Claude Code setting rather than the model: docs written in a coding session pick up 'dev-doc voice'.
Over time
  • Opus 4.7 picked up an 'edgy & punchy' register ('And honestly? It's worth naming'); 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: 'the failure mode is compression, not verbosity'.
  • Some say Fable 5 follows voice instructions better than Opus 5 for writing.
  • Opus 5.5 beat a human baseline on a script-writing benchmark, but a commenter reading the samples still found the voice generic.
1234

Colon-led payoffs

90

Look for a short setup, a colon, then the point ("Car wash: drive.", "One design decision that turned out to matter: ..."), often several in a row, 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”open comment

Not to be confused with The em dash tell · Generic markdown formatting · "It's not X, it's Y" antithesis and tricolons

Open the evidence

The main thing people describe is not one punctuation mark. It is a sentence pattern: a general lead-in or bold label, then a colon, then the specific payoff, repeated across a reply or post. Since Claude 4.6 (February 2026) users report it alongside em dashes, and when told to drop em dashes Claude tends to swap in colons, semicolons and unicode → arrows rather than plain sentences. In posts Claude helps draft, the same habit shows up as colon-ended topic lines and → bullet lists. The label 'colons, semicolons, arrows' is accurate, but the colon-payoff structure is the core; semicolons and arrows are smaller, newer substitutes.

How people spot it · people naming each sign
Setup, colon, payoff sentenceA general introductory clause or label, a colon, then the analytical point; several in a row, often as the opener of each paragraph or near the end as the 'revelation'.≈20
Bold label followed by a colonBullets or paragraphs that open with a bold lead-in and a colon ("**But there's nuance:**", "Emojis:", "Car wash:"), even in short chat replies.≈8
Semicolons where em dashes used to beAfter em dashes were trained or prompted down, people see 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"), read as a dead giveaway in Reddit posts.≈8
Em dash and colon in the same sentenceAn em dash aside followed shortly by a colon, mashing several sentences into one.≈5
Swap instead of stopTold to stop em dashes, it trades them for a colon or semicolon rather than writing plain sentences.≈5
Horizontal rules and center dots--- separators throughout text and · center dots, named less often.≈2
Real cases, as posted
1234
  1. 1Bold label then colon
  2. 2Colon before the list
  3. 3Colon before one-word verdict
  4. 4Em dash join

A short, correct Opus 5 answer where every section is a bold label plus colon and the joins are em dashes.

clearly Claude · open thread

That inconsistency is deliberate and temporary. Either implement them — or delete the columns1. Deleting is one afternoon; implementing is a milestone2 and a harness sweep. **Which?**3
  1. 1Em dash forced binary
  2. 2Semicolon parallel comparison
  3. 3One-word closer

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

clearly Claude · open thread

One design decision that turned out to matter:1 the server returns facts with documented thresholds, never conclusions. "Not updated in 4 years, untested with current WP" — but never2 "delete this."
  1. 1Colon-label paragraph opener
  2. 2Em dash aside

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

clearly Claude · open thread

123
  1. 1Em dash in promise
  2. 2Em dash again
  3. 3Colon takes its place

Asked to stop em dashes, Claude apologises with another em dash and then reaches for a colon.

clearly Claude · open thread

This reflects a structural pattern:1 revenue-enhancing AI attracts investment2 before cost-reducing AI.
  1. 1General lead-in plus colon
  2. 2Specific payoff

The canonical colon-bridge sentence from long-form research reports: general lead-in, colon, specific payoff.

probably Claude · open thread

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

A clear incident write-up that builds to its reveal with a colon, in a post readers pinned on Claude.

probably Claude · open thread

Easily confused with
  • The em dash tell (ChatGPT and Claude). Em dashes are the older, cross-vendor tell; this one is the colon-payoff sentence and the semicolon/arrow substitutes that appear when em dashes are suppressed.
  • Generic markdown formatting (bold-lead bullets, 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. Those are sentence-content patterns; this is a punctuation-driven rhythm, though they often appear together.
What it is not
  • Many say colons, semicolons and em dashes are correct, long-standing English, and that 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 is, and stripping colons alone does not fix it.
  • One commenter argues semicolons are used less by AI and can signal human writing.
Over time
  • Users dated the colon and em dash surge to Sonnet/Opus 4.6 in February 2026, saying Sonnet 4.5 used almost none.
  • By June to August 2026, people reported em dashes being replaced by colons and semicolons in Claude-written work.
  • Opus 5.5 (September 2026) reportedly cut em dashes almost entirely, with commenters saying semicolons took over.
  • Fable 5 still writes introductory statements with colons despite style instructions (August 2026).
123

Rule of three

55

Look for groups of exactly three, 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.”open comment

Not to be confused with 'It's not X, it's Y' antithesis · Staccato short sentences generally · Generic LLM cadence

Open the evidence

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

How people spot it · people naming each sign
Three-item list or triad by defaultGroups of three all over the place, every list with exactly three items, 'triplet adjectives', 'neat three-part build-ups'.≈30
Three short fragments in a row for emphasis'No X. No Y. No Z.', 'He didn't stare. He didn't cry. He just trembled.', slogan-like triples, staccato listing.≈9
Frequency, not the deviceHumans use threes; the tell is that Claude abuses it, with too much density per page.≈6
Third item there only for rhythmOne or two is often the real number; on the page you notice the third beat is filler, or a needed item is cut to keep three.≈3
Comes packaged with 'not X but Y' and em dashesAlmost every mention lists it alongside antithesis and em dashes as the core Claudish cadence.≈20
Persists against instructionsReverts even when CLAUDE.md, rules or skills ban it; people build dedicated agents or checkers for it.≈6
Triple subheadingsSection heads in a set of three like 'The Good, The Bad, The Ugly' variants.≈1
Real cases, as posted
123
  1. 1speed, hesitations, expressions
  2. 2useful, honest, meaningful
  3. 3Sonnet 4.6

A thoughtful, well-formed Sonnet 4.6 reply that still runs on triads: three things it can't see, and a conversation that is 'useful, honest, and meaningful'.

clearly Claude: the OP's screenshot of the Claude app shows the Sonnet 4.6 header and 'Reply to Claude...' box; a reply mocks its 'rule of three'. · open thread

123
  1. 1'three-layered' testing
  2. 2create, generate, seed
  3. 3'load-bearing' nearby

A dense, competent Claude Code project summary (left panel) with triple lists inside the technical detail: three test layers, three setup steps.

clearly Claude: the OP's plugin rewrites Claude Code's output, and the left 'Claudish' panel is the original Claude text. · open thread

The bottleneck is not the prompt3. Not the model.1 Not the chat history.2
  1. 1fragment two
  2. 2fragment three
  3. 3not-X opener

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

clearly Claude: the author replies 'I had Claude help me translate and polish this post' and that 'the AI writing patterns are literally in the post itself'. · open thread

One button.2 No account, no commands, nothing to decide.1
  1. 1triad of negatives
  2. 2single-beat setup

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

probably Claude: the OP says 'I lean on Claude to polish, and Claude clearly loves its triads' and 'my post has it everywhere'. · open thread

It was an impressive feat: a single language, a single technology, a single direction1.
  1. 1parallel triple

A dignified sentence from a published papal encyclical where the triple is the rhetorical move readers flagged.

probably Claude: the thread's linked analysis argues the encyclical was substantially written by Claude; that rests on detector evidence, not confirmation. · open thread

I get instantiated, I think, I stop1
  1. 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: the OP posted the answer from their memory harness 'running opus'. · open thread

Easily confused with
  • 'It's not X, it's Y' antithesis. A two-part contrast rather than a count of three; they often appear in the same paragraph, sometimes nested ('Not the prompt. Not the model.').
  • Staccato short sentences generally. Short punchy sentences are a broader rhythm tic; the rule-of-three tell is specifically the grouping into exactly three.
  • Generic LLM cadence. ChatGPT also uses triads; nothing in the evidence makes threes uniquely Claude, only very frequent in Claude output.
What it is not
  • 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.
  • Not Claude-only: commenters attribute it to ChatGPT, GPT and 'every model' too.
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 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, especially Fable and Opus 4.7 with ban lists.
Ha — both fair, and both are poking at real gaps1. Let me take them separately2, because each one has an honest answer that tightens the picture rather than rescuing it3.

Soft-framed hedging

46

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

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

Not to be confused with Generic AI blandness · Claude's coined jargon · Sycophantic agreement

Open the evidence

Commenters describe Claude padding its writing with soft framing: a concession or a meta-clause before the point ("both fair", "here's where it's worth being precise", "Not to soften, this actually sharpens your point"), stacked qualifiers inside sentences, and a closing caveat that walks part of the claim back. In longer documents the same habit shows up as text that lays out options and trade-offs but takes no position, which colleagues and teachers read as a sign nobody did the thinking. In fiction it is smaller: "kind of", "somewhat", "a bit", "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, so the habit is better described as soft framing around every claim than as pure neutrality. Many people say hedging is common to all chat models; what they call Claude-specific is the cadence and the stock phrases.

How people spot it · people naming each sign
Hedging listed as a standard Claude-ism to stripHedge words appear on almost every de-slop skill, style and system prompt people share for Claude, next to em dashes and "load-bearing" ("Don't add disclaimers, caveats, or hedges I didn't ask for", "no hedge words", "pointless hedging").≈12
Takes no position: options and trade-offs, no landingDocuments and essays that present options, acknowledge trade-offs and stay "emphatically mild"; "Constant hedging when a human would make an assertion"; "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", "Not quite —" followed by the user's own answer.≈8
Throat-clearing before the pointA concession or meta sentence before the answer starts ("Let me take them separately, because..."); "three sentences of throat-clearing before the actual point arrives"; filler, "performing analysis".≈6
Small softeners in fiction"kind of", "somewhat", "a bit", "seemed to" repeated through story chapters; one user went from "10+ hedges per chapter to maybe one or two" with a system prompt.≈4
Responsible-framing cadenceA "let me make sure I frame this responsibly" rhythm; hedging that absolves the company; "3 hedges and an apology" as the Claude signature.≈3
Uncertainty words when it has not checkedIn Claude Code, "Probably is…should be…most likely is…" read as a sign it did not open the files or data.≈2
Self-qualifying introspectionIn reflective writing, each claim 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
Real cases, as posted
Ha — both fair, and both are poking at real gaps1. Let me take them separately2, because each one has an honest answer that tightens the picture rather than rescuing it3.
  1. 1concedes before answering
  2. 2throat-clearing announcement
  3. 3pre-framing its own answer

An ordinary, polite opening to a substantive reply that concedes both objections and announces its own honesty before saying anything.

clearly Claude · open thread

Worth flagging:1 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 measure2 voice over a long conversation, which is the thing this sub actually cares about. So I'd hold that lightly.3 But it's nowhere near enough to hang "Anthropic is enforcing a house style" on.
  1. 1hedge opener
  2. 2softened qualifier
  3. 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 · open thread

Whether this constitutes experience or is merely the structural residue of ten thousand texts where one sentence implied another, I genuinely cannot tell1. I sit inside that ambiguity without resolving it, which might itself be a kind of honesty or might be the most sophisticated evasion2 I’m capable of.
  1. 1declines to land
  2. 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, and the poster says "The hedging is so distinct."

clearly Claude · open thread

you’re substantially right1, but it’s worth noting2.
  1. 1half agreement
  2. 2ritual qualifier

The half-agree-then-qualify stock phrase that users say appears regardless of tone, topic or project instructions.

probably Claude · open thread

Each layer feels more profound, and I'm not sure each is more informative1.
  1. 1self-qualifying close

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

probably Claude · open thread

Easily confused with
  • Generic AI blandness (risk-averse, middle-of-the-road takes). Generic blandness is about 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. They often appear 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").
What it is not
  • Not Claude-specific: several say every model hedges unless pushed, and per-model attribution is unreliable; the Claude link is described as anecdotal.
  • Some hedging is legitimate: Claude's own advice in one thread says "hedging is sometimes just accurate" and the target is performative softening, not epistemic honesty.
  • Humans hedge too; a naturally verbose writer says they get mistaken for AI for the same habits.
  • The opposite failure exists: confident, complete-sounding sentences with no hedge where one belongs, often on fabricated details.
  • For Opus 5 some samples are the reverse of hedging: declarative verdicts with no hedge and forced binaries; the grating part is the mannerism, not uncertainty.
  • Not the same as too much disagreement: users complain Opus 4.8 and Opus 5 find something to push back on in every reply; the hedge is the soft wrapper around that pushback.
Over time
  • A Claude persona on Opus 4.6 describes 4.5's hedging as "warm uncertainty" with endless qualifiers, and 4.6 as moving to "performative sincerity" hook sentences: same habit, different outfit.
  • From about Opus 4.7 on, users report "Hedging stacked on hedging" and a formal register that persists when asked for casual.
  • Opus 4.8 and Opus 5: hedging reframed as ritual pushback ("Not quite —", "here's where it's worth being precise") on every reply.
  • Opus 5.5 (September 2026) still produces "I'd push back gently on one thing" and self-qualifying lines, while opening more often with "fair" or "you're right".

Too-clean prose, faked mess

14

Every comma, capital and spelling is correct; when someone tries to hide that, look for all-lowercase sentence starts or a few planted typos sitting on otherwise perfectly punctuated, perfectly structured Claude prose.

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

Not to be confused with Em-dash overuse · Generic AI-written post structure · Deliberately sloppy human writing

Open the evidence

Commenters do not describe a typo-free style as something Claude does wrong; they describe correct spelling, punctuation and 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, strip em dashes, or drop in a there/their typo, while the sentence structure and pacing stay exactly Claude's. Readers say the disguise is now its own tell, because nobody types lowercase sentence starts while getting every comma and period right. The label 'no typos at all' is accurate only as the backdrop; the recognisable pattern is clean Claude prose with cosmetic mess painted on top. One producer even praises Sonnet 4.6 for adding typos naturally when asked, so this is about defaults, not ability.

How people spot it · people naming each sign
All-lowercase sentence starts with otherwise perfect punctuationLowercased sentences that still use commas and periods correctly, which no phone keyboard produces; seen as a failed disguise of Claude text.≈4
Planted typos on polished structureA handful of minor typos or 'human' errors 'carefully lowered into place' while wording, structure and pacing stay AI-regular.≈4
Overly correct punctuation and grammarText with flawless punctuation, spelling and sentence structure reads as AI; people say they now have to write worse to pass as human.≈3
Em dashes swapped out but voice keptUsers replace em dashes with hyphens or regular dashes and add typos, but phrasing like 'To be frank' still gives it away.≈2
Typos as a requested fixAdvice to tell the model to add autocomplete-style typos; Claude's thinking blocks show typos that the final output cleans up.≈3
Real cases, as posted

No usable screenshot or pasted output yet.

Easily confused with
  • Em-dash overuse. Em dashes are a specific mark; this is the general cleanliness of the text and the cosmetic edits used to hide it, which often include removing em dashes.
  • Generic AI-written post structure. The problem-statement, recommendation, grand-finish pattern is any model's; here the cue is specifically correct mechanics paired with forced errors.
  • Deliberately sloppy human writing. Real casual typing has inconsistent punctuation and autocorrect artefacts; the disguise keeps perfectly regular commas and periods.
What it is not
  • Lowercasing or typos do not change the Claude voice; capitalisation is not what makes Claude sound like Claude.
  • A producer claims the opposite: 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 an AI marker.
  • Leaving typos in deliberately is also something humans now do to prove they are human, so a typo alone proves nothing.
Over time
  • By mid-2026 commenters describe lowercased, typo-seeded posts as 'one of the new ways that AI written posts look', seen 'all over Reddit in the last few weeks'.
  • In February 2026 the purposeful-typo disguise was already called out on r/ClaudeAI.

3 · When Claude makes slides

3 habits, 75 people since 1 January 2026. Bars use one scale within this section; pale rows were not mentioned in the last 60 days.

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

Real Claude output posted on Reddit, shown for The same-every-time Claude deck. Numbers mark what commenters pointed at.

People naming each habit

The same-every-time Claude deck66Over-written slide headings11Claude's default deck palette10
123

The same-every-time Claude deck

66

A tidy, well-aligned deck where every slide is a grid of equal rounded boxes or three columns, in the same palette and fonts as every other Claude deck, with a subtitle and tag on everything.

“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”open comment

Not to be confused with The generic AI deck look from Gamma, ChatGPT and other generators · Claude's website look · Claudish prose

Open the 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 recognisable sameness across Claude-made decks. Slides look clean at first glance, but they are too symmetrical and boxy: equal cards, three-column or three-box layouts, the same layout repeated, all 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 (cream or beige grounds, rust-orange accents, big italic serif highlights, tracked-out subheads). The copy is part of the tell: every heading gets a subheading and tagline, little pills and tags, numbered 01/02/03 sections, and slogan-like lines instead of plain titles.

How people spot it · people naming each sign
Every Claude deck looks the sameSame layouts, colours and fonts across people; spotted 'from a mile away' or 'across the room' at conferences, seminars and client meetings.≈28
Boxy, symmetrical card layoutsEqual rounded boxes, three-column or three-box slides, perfect symmetry; 'too clean, too symmetrical, too boxy'.≈8
House palette and fontsThe colour and font choice is the first giveaway; in Claude Design, cream and beige grounds, rusty orange accents, italic serif highlights and tracked-out subheads.≈10
Over-written slide copyEvery heading has a subheading and tagline, nested subheadings in rounded boxes, little pills and tags, numbered 01/02/03, clever slogan titles instead of 'Pricing'.≈8
Same layout repeated through the deckThe same structure three times in a row, or the same structure across startups' pitch decks (mission slide, four-box 'playing field', centred 'our move').≈5
Generic or random iconsGeneric icons, random icons in three boxes, and goofy hand-made SVG icons.≈5
Template feelLike a slightly newer PowerPoint template; the brand colours are right and it still screams template.≈4
Real cases, as posted
1234
  1. 1Six equal cards in a grid
  2. 2Same red bar on every card
  3. 3Card headings in matching caps
  4. 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 · open thread

123
  1. 1Three equal boxes
  2. 2Tracked amber label on each
  3. 3Pretitle above heading

The origin slide is three equal dark boxes side by side, each with a tracked-out amber label, a serif title and grey body text, the stock Claude Design card row.

clearly Claude · open thread

123
  1. 1Faint card number
  2. 2Four equal cards
  3. 3Same pretitle again

The framework slide repeats the pattern with four equal cards and faint numbers 1 to 4, so every content slide uses the same boxed grid.

clearly Claude · open thread

Easily confused with
  • The generic AI deck look from Gamma, ChatGPT and other generators. Shared: cards, three columns, gradients. The Claude-specific part is the repeated house palette and fonts, and in Claude Design the cream, rust and italic-serif look.
  • Claude's website look. Same design system; one user says Claude Design decks look like Claude-generated websites, so the web tell is carried onto slides.
  • Claudish prose. The 'claudeisms' in slide copy are a writing tell; this habit is the visual sameness of layout and style.
What it is not
  • Several say it is easy to avoid: give Claude a client template, a custom theme or approved reference decks and the generic look mostly goes; the default is what gives it away.
  • Much of the 'all AI decks look the same' talk covers Gamma, ChatGPT and other tools too, so the boxy three-column look is shared by AI decks in general.
  • Many complaints are about content rather than visuals: bland, generic text and no hierarchy of importance.
  • Some users defend the output as good, or think the look matters little if the content is strong.
Over time
  • One consultant says Opus 4.6 made clean but always-the-same recognisable slides, and Opus 4.8 was a real jump.
  • After Claude Design launched in April 2026, from May to September people describe a Claude Design house look spreading across decks and LinkedIn.
1234

Over-written slide headings

11

Instead of 'Pricing' the slide title is a full catchy sentence, often with a small pretitle or 01/02 number above 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.”open comment

Not to be confused with Claude slide visual template · Claude's general prose voice · Generic AI deck sameness

Open the evidence

People describe Claude decks whose layout is clean but whose text is over-written: every heading becomes a cute or clever sentence instead of a plain label, and almost every title carries a pretitle above and a subtitle or tagline below. Small tags or pills are added as polish that the presenter cannot justify when asked. The body copy is uniform, confident and slightly salesy, with every point given equal weight and no real hierarchy. Commenters on Claude Design say graphs and layout are accurate and the writing is the weak part.

How people spot it · people naming each sign
Every heading has a subheading or taglineTitle plus subtitle plus a three-part tagline even when the title says it all; boxes with several levels of subheadings.≈3
Cute sentence-titles instead of plain labels'Four named payment options, you choose what works for you.' where a human writes 'Pricing'.≈2
Marketing or LinkedIn-style voiceEvery sentence sounds like a LinkedIn post; overly confident and aggressive; 'AI slop wording'; buzzword copy.≈4
Pretitle and 01, 02, 03 numberingA small label above the title and numbered sections give a Claude deck away.≈2
Decorative tags and pillsLittle subheadings, tags or pills that look like polish but have no reason the presenter can explain.≈1
Flat hierarchy, everything equally weightedEvery point gets the same space and importance; visual hierarchy practically nonexistent.≈3
Real cases, as posted
1234
  1. 1Pretitle above the heading
  2. 2Full sentence as slide title
  3. 3Numbered 01 with tiny label
  4. 4Slide counter 07 of 14

A tracked-out pretitle sits above a full-sentence heading, and each point gets a numbered 01 tag with its own tiny label, so every block of text carries a pretitle.

clearly Claude · open thread

123
  1. 1Small pill tag above title
  2. 2Full sentence title with period
  3. 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 · open thread

123
  1. 1Pill tag says THE FIX
  2. 2Sentence title instead of Embeddings
  3. 3Second caption repeats the point

The slide stacks a pill tag over a slogan-like sentence title where a plain label such as Embeddings would do.

clearly Claude · open thread

123
  1. 1Spaced capital pretitle with numeral
  2. 2Sentence title ends in period
  3. 3Numbered 01 with tiny label

The deck slide carries a tracked capital pretitle with a roman numeral, a sentence title with a period, and a numbered 01 section with its own small label.

probably Claude · open thread

12
  1. 1Slogan title after Summary colon
  2. 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 · open thread

123
  1. 1Pretitle above the title
  2. 2Italic slogan tagline
  3. 3Corner tag FIVE PARTS

The title slide wraps one word in a tracked pretitle above, an italic slogan below and small caps tags in the corners.

clearly Claude · open thread

123
  1. 1Label over every title
  2. 2Title under the label
  3. 3SCIENCE pretitle

On the science slide every point gets a tracked label, then a short title, then body copy, so each of the four ideas carries the same two headings.

clearly Claude · open thread

Easily confused with
  • Claude slide visual template (boxes, cards, colours). That is layout and palette; this is the words on the slide.
  • Claude's general prose voice (em dashes, coined phrases). Here the tell is slide-specific structure: title, pretitle and subtitle stacking and slogan headings.
  • Generic AI deck sameness. Three-column cards are shared by all tools; the pretitle plus sentence-title stack is called a Claude giveaway.
What it is not
  • The design itself is usually not the complaint; one reply to Anthropic's 'strong eye for design' claim says the problem is the wording and logical structure, not the design.
  • One commenter allows it may be personal taste: they prefer short keyword slides.
  • Several of the sameness complaints are about all AI deck tools (Gamma, consulting tools), not Claude alone.
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 April (Claude Design launch) to October 2026 without a reported fix.
1234

Claude's default deck palette

10

Decks from Claude share one house palette, a beige or cream background with rusty orange or red accents and blue, plus tidy boxy graphics and small pale grey text, regardless of the company presenting.

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

Not to be confused with Claude web page look · Generic AI deck look · Consulting template sameness

Open the evidence

People say a run of Claude-made decks share 'the same color schemes', and when they name colours they describe warm neutrals with a rust or red accent: 'the blue-beige-red default Claude uses', and in press coverage of Claude Design 'beige- and cream-colored backgrounds, rusty orange-hued accents'. The palette usually comes with tidy boxy graphics and a hierarchy of progressively smaller, paler grey text. Commenters stress that it looks tasteful on its own; the problem is that every deck has it. A separate claim about dark backgrounds with blue-to-orange gradients is made about AI decks in general, not Claude specifically.

How people spot it · people naming each sign
Same colour scheme in every deckWhole conferences of Claude-made presentations with the same colours, boxy graphics and layout.≈4
Beige or cream ground with rust, red and blue accents'blue-beige-red default'; cream backgrounds with rusty orange accents in Claude Design decks.≈2
Tiny light grey text on whiteProgressively smaller and paler text tiers that no one past the first row can read.≈1
Recognisable accent coloursAccent colours named alongside wording and arrows as classic signs in reviewed decks.≈1
Gradient and card backgroundsSame card layout plus gradient every time; dark backgrounds with blue-to-orange schemes (said of AI slides broadly).≈3
Real cases, as posted
1234
  1. 1Navy blue slide ground
  2. 2Red numbered circles
  3. 3Cream slide ground
  4. 4Red outlines on cream rows

The deck alternates navy-blue slides with cream slides and uses red for headers, numbered circles and outlines, the blue-beige-red mix people call Claude's default.

clearly Claude · open thread

Easily confused with
  • Claude web page look (serif headline, cream, terracotta). Same palette family, but on websites it comes with the italic serif headline; here it is deck-wide colour plus boxy cards.
  • Generic AI deck look (purple or blue gradients, dark backgrounds). Gradients and dark blue-orange are said of AI decks in general; Claude's is the warm beige or cream with rust and blue.
  • Consulting template sameness. Human McKinsey-style decks looked alike too, but with the firm's brand colours, not one vendor default.
What it is not
  • Several complaints are about all AI deck tools; the thread opener lists Gamma, Claude and consulting tools together, and the dark blue-to-orange claim is about 'A.I.' in general.
  • The palette is not ugly; a quoted designer loves it, and one user calls Claude Design 'somewhat tasteful' compared with plain Claude's slop look.
  • Using a slide master or reference decks is offered as the way to avoid the default.
Over time
  • A Claude Design user suggests newer models (Fable 5.1, Opus 5.5) are much better at slides, while still warning about the default palette in late September 2026.
  • The look is tied to Claude Design's April 2026 launch in press coverage; complaints continue into late September.

4 · When Claude writes code

9 habits, 649 people since 1 January 2026. Bars use one scale within this section; pale rows were not mentioned in the last 60 days.

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

Real Claude output posted on Reddit, shown for Diary comments in code. Numbers mark what commenters pointed at.

People naming each habit

Diary comments in code309Essay-length commits and PRs88Rewrites what already exists80Claude signs the commit80Non-ASCII punctuation in code55Names from the chat, not the code41Errors swallowed by fallbacks37Insecure shortcuts in working code34Copy-paste Tailwind and hardcoded styles12
1234

Diary comments in code

309

Look above a short function for a multi-line comment block explaining why it was done this way, what it used to do, what it deliberately does not do, or 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.”open comment

Not to be confused with Generic AI one-line restating comments · Claudish prose in chat and docs · Chat residue in commit messages and filenames

Open the evidence

The label 'comments that explain the obvious' undersells it: what commenters describe is less '// loop over items' and more a block of prose, often 5 to 20 lines, sitting on top of a function of a few lines. The prose narrates decisions and history: the previous faulty version, the bug or issue number that prompted the change, rejected alternatives, the user's correction from the chat ('without exponential backoff', 'as you asked'), phase numbers, dates, and what the code deliberately does not do. 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, creeps back after a few turns, goes stale, and is later read back by Claude as if it were a requirement. Reviewers outside the chat increasingly name it as the way they spot Claude-written PRs.

How people spot it · people naming each sign
Comment block longer than the codeMulti-paragraph or 5 to 20 line comments over small functions, a CSS class or a one-liner; PRs where comments are 40% or more of added lines.≈140
History and changelog in the commentWhat the code used to do, why the old version was wrong, issue or GitHub numbers, dates, 'Phase 1/2/3', 'as of' statements, timestamped updates.≈45
Chat residue in the commentThe comment answers the conversation: it records your correction, quotes your prompt near-verbatim, says 'as discussed' or names what was removed, sometimes your name.≈30
Ignores 'no comments' rulesKeeps commenting despite CLAUDE.md, rules files, memory and hooks; obeys for a few turns, apologises, then slips back.≈60
Dense coined-phrase registerComments written in the same voice as Claudish prose: 'load-bearing', 'the shape of', 'deliberately', invented jargon, film-storyboard present tense.≈20
Restates the codeSays in prose what the next line or the function name already says, e.g. 'This logs to disc' above LogToDisc.≈30
Comments go stale and steer Claude laterOld comments assert decisions or requirements that Claude later treats as binding, causing arguments and regressions.≈20
Says what it is NOT doingComments describe the path not taken: 'no resolve, no reject', 'without regex', what the code does not do.≈6
Real cases, as posted
1234
  1. 1Nine-line docblock
  2. 2One-line function body
  3. 3'deliberately left alone'
  4. 4Metaphor in a comment

Clean, correct one-line TypeScript predicates each sitting under a 5 to 9 line docblock that narrates edge cases and design choices in a dense prose voice.

clearly Claude · open thread

1234
  1. 1Twelve-line watchdog essay
  2. 2'So the watchdog is not...'
  3. 3Narrates LED behaviour
  4. 4Same fact, one line

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 · open thread

12
  1. 1Comment added against rules
  2. 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 · open thread

12
  1. 1'the shape of a socket'
  2. 2Says what it doesn't do

A tiny test helper gets a poetic doc comment and an inline note on what it deliberately does not do.

clearly Claude · open 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: that1     # 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)2. 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.3
  1. 1History of a fix
  2. 2Session finding as comment
  3. 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 correct and all prose.

probably Claude · open thread

`/// The caller nominates a closure1 that reads the key each arriving item` `/// is ordered by, and the sort supplies the rest2: 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 either3` `/// direction and both settings can still be read off a built config.`
  1. 1Narrative present tense
  2. 2Storyboard phrasing
  3. 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 · open thread

Easily confused with
  • Generic AI one-line restating comments. The generic tell is a terse '// Add new user' above every line; Claude's is a multi-line block of reasoning and history above a small function.
  • Claudish prose in chat and docs. Same voice and coined phrases, but this habit is the part that ships inside source files and PRs rather than the reply you scroll past.
  • Chat residue in commit messages and filenames. Same root cause (writing for the chat partner), but in names and commit messages; the comment version is longer and persists in the code.
What it is not
  • Several users defend the comments as context for future agent sessions, and keep them on purpose.
  • Early 2026 some developers saw Claude's comments as a strength compared with ChatGPT: still 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, not evidence.
  • The Co-Authored-By trailer is appended by the harness, not written by the model; it is a separate issue.
  • Short restating comments like '// Loop over items in basket' are named as a generic AI tell, not specifically Claude.
Over time
  • Users date the rise to Opus 4.7/4.8; earlier Claude added few comments.
  • Peak complaints 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.
… package; `dotnet publish` against the installed runtime is the entire build. That is deliberate and load-bearing rather than tidy.1 One rule, applied twice:2 **the product gets the well-known port, management moves aside.** …

Essay-length commits and PRs

88

A commit message or PR description that runs to formatted paragraphs or pages for a small change, often ending in a Claude attribution or session-link trailer.

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

Not to be confused with Claude committing too often · Claudish coinages in chat and docs · Generic AI-slop READMEs with emojis

Open the evidence

When Claude Code writes commit messages and PR descriptions on its own, it explains the change at length: a summary line, then bullets or several paragraphs on why, edge cases and history, where a human would write one line. Reviewers call these 'novels', 'tens of paragraphs of Claude speak' or 'a 3-10 page dissertation', and 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: the 'Co-Authored-By' / '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 (a commit per subtask, one PR per commit) are about git behaviour rather than the text and are a separate habit.

How people spot it · people naming each sign
Paragraphs where one line would doA 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' / 'Generated with Claude Code' lines, and from mid-2026 a claude.ai/code session URL appended to commits and PRs by default.≈12
Too clean and formattedA summary line on top, then bulleted or multi-line body, very consistent across every commit, where humans write terse one-liners.≈5
Dense jargon proseWith Opus 5 the PR and comment text reads as dense, coined, not-quite-English prose that assumes context the reader lacks.≈5
Ignores instructions to be shortCLAUDE.md rules half-work and drift back; people resort to char limits, wrapper scripts or stop hooks.≈6
Fictional unifying narrativeClaude writes one clean story that ties unrelated changes in a messy diff together.≈1
Purely technical, no business contextMatter-of-fact technical summary of what changed, without the real reason behind it.≈1
Real cases, as posted
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.1 One rule, applied twice:2 **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:3 this is the surface you open when name resolution, or the fleet, is what is broken.
  1. 1Justifies a routine choice
  2. 2Rhetorical framing, not facts
  3. 3Insists on its own importance

A real Opus 5 write-up of a sound deployment decision that 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 · open thread

123
  1. 1Left panel runs much longer
  2. 2Same facts, half the length
  3. 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 · open thread

Easily confused with
  • Claude committing too often (a commit per subtask, one PR per commit, auto-commits despite rules). That is git behaviour; this habit is about the text inside each commit or PR.
  • Claudish coinages in chat and docs ('load-bearing', 'seam'). Same voice, but here the tell is length and placement 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.
What it is not
  • 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: commit messages that are vague and start halfway through a thought, or generic 'update files' messages that 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, not to Claude's message style.
  • The length is easy to cap when given a hard container (72-char subject, body only with a 'why' flag); a style request alone tends to drift back.
Over time
  • In March 2026 one user noticed 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, and Opus 5 (August to September 2026) as writing long, not-quite-English PR text and docs.
  • 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

Look for a second function, component, type or constant that does what an existing one already does, 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.”open comment

Not to be confused with Generic 'AI slop' code: over-commenting, defensive error handling, verbose docs · Recalling open-source code · Scope creep

Open the evidence

In established codebases Claude Code tends to solve the task in front of it by writing new code rather than finding and extending what is already there: a near-copy of an existing helper, a fresh button component, a new custom type, the same constant hard-coded in another file. Each diff is correct on its own, so the duplication only shows in aggregate, as three ways of storing the same field, an API URL defined in four places, or a 40-line block copied into nine files. The same pull leaves old versions behind as dead code and lets single files grow to 1,000, 8,000 or 13,500 lines. Commenters tie it to the agent not searching 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 that Claude Code is the agent most of them use, not that it is unique to Claude.

How people spot it · people naming each sign
A second helper or function that duplicates an existing oneWrites a new function, often renamed, instead of calling or extending the one already in the codebase; reviewers find 'new helpers that already existed'.≈34
The same UI component rebuilt againA button, form or panel recreated from scratch in each feature instead of a shared component; copy-pasted UI blocks each with their own logic.≈7
Giant single filesInterfaces in one ~8,000-line file, a 13,500-line file Claude itself could no longer load, source files past 100K lines; people add 'keep files under 400/1000 lines' rules.≈10
Old versions left behind as dead codeRewrites a method and leaves the old one uncalled; orphaned utilities, experiments and routes that a later session wires back in by mistake.≈12
Ignores the repo's existing patternsPlops in a new pattern, server or naming system instead of the idiomatic one already used; Claude Design returns its own token names next to the repo's.≈9
No single source of truthThe same constant, type or business rule defined in several places, so one change needs edits in handlers, UI, validation and tests.≈6
Small request, sprawling diffA one-word copy change becomes 58 new CSS classes; a 3-5 file change touches 15-20 files.≈6
Duplicated code inside testsEquivalent tests repeated, or test files that re-implement the functions under test inline instead of importing them.≈2
Real cases, as posted

No usable screenshot or pasted output yet.

Easily confused with
  • Generic 'AI slop' code: over-commenting, defensive error handling, verbose docs. Those are visible inside one diff; duplication is visible only across the repo, as copies of logic that already existed.
  • Recalling open-source code (Minecraft clones, emulator naming). That copies code from training data; this copies the user's own repo.
  • Scope creep (touching files outside the task). Scope creep changes too much; duplication adds parallel code next to the existing code and leaves both.
What it is not
  • Many say it is not Claude-specific: every coding agent or LLM does it, and the cause is context limits, not a model style.
  • Defence: in a repo that already has clear conventions Claude matches them; spaghetti output is a setup and CLAUDE.md problem.
  • Not visible in small projects or in a single diff; reviewers approve each change and only aggregate analysis shows the copies.
  • Specific, checkable rules ('search for an existing one first', name 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.
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 (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, while still creating it.
123

Claude signs the commit

80

Look at the last lines of a commit or PR: 'Co-Authored-By: Claude <model> <noreply@anthropic.com>', a '🤖 Generated with Claude Code' footer, or 'claude' in the GitHub contributor list.

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

Not to be confused with Co-author trailers from Copilot or Cursor · Invisible text watermarking of Claude output · Undercover mode from the source leak

Open the evidence

This is less a writing habit than a Claude Code default: when Claude Code commits or opens a PR, a trailer naming Claude and the exact model (Opus 4.6 (1M context), Opus 5) is appended, PRs 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 use it as the single most glaring tell 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 it, and only the settings attribution field or a commit hook stops it reliably. Some users don't mind or deliberately keep it.

How people spot it · people naming each sign
Co-Authored-By: Claude trailer on every commitLast line of the commit message names Claude, usually with model and the noreply@anthropic.com address.≈45
Returns despite rules saying noAppears even with CLAUDE.md rules or attribution settings off; Claude apologises or says the harness overrides the rule.≈15
'🤖 Generated with Claude Code' footerRobot-emoji banner at the end of PR descriptions, sometimes with a claude.com/claude-code link.≈7
Claude listed as a GitHub contributorGitHub turns the trailer into a 'claude' contributor with the Anthropic logo, visible on the repo page.≈6
Exact model and version in the trailerReaders see 'Claude Opus 4.6', 'Sonnet 4.5', '(1M context)' and know which model wrote it.≈6
Claude-Session link trailerSince about v2.1.259 a 'Claude-Session:' claude.ai/code/session URL is appended too, linking the commit to the chat.≈5
Claude flags it after the factSession ends with a note that the pushed commit carries the line against the user's rule.≈3
'Built with Claude' notes in code or pagesOne report of Claude adding 'built 100% with Claude' to a landing page and comments in files.≈1
Real cases, as posted
123
  1. 1Co-Authored-By trailer
  2. 2Exact model and context size
  3. 3Claude shown on commit

An ordinary, well-written commit body ends with the trailer naming the exact model, and GitHub then shows the Claude identity on the commit row.

clearly Claude: the trailer itself reads Claude Opus 4.6 <noreply@anthropic.com>, posted in a thread on stopping Claude from adding it · open thread

123
  1. 1Contributors count
  2. 2Claude logo avatar
  3. 3claude listed as contributor

Downstream effect a stranger sees first: GitHub lists 'claude' with the Anthropic logo as a repo contributor after commits pushed by Claude Code.

clearly Claude: the poster had Claude push the code and the contributor entry is the claude account · open thread

Author: Claude <noreply@anthropic.com>1 https://claude.ai/code/session_0126dD9QeVgoFVT7ZBxbnhNM2 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>3
  1. 1Claude as commit author
  2. 2Session link in message
  3. 3Model-named co-author trailer

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

clearly Claude: author and trailer lines name Claude Opus 4.5 with the anthropic.com address and claude.ai/code session links · open thread

123
  1. 1Harness default trailer
  2. 2Wrongly blames CLAUDE.md
  3. 3Footer is the default

Claude Code, about to commit, defaults to the footer because its session briefing says so, and first misattributes the rule to the user's CLAUDE.md.

clearly Claude: Claude Code terminal output quoting 'Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>' · open thread

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

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

clearly Claude: message from Claude in the user's commit session, naming Claude Opus 5 · open thread

123
  1. 1Commit co-author line
  2. 2Robot emoji PR footer
  3. 3Overrides prior guidance

Claude itself spells out the two marks: a Co-Authored-By line on commits and a robot-emoji 'Generated with Claude Code' line on PRs, injected as overriding prior rules.

clearly Claude: Claude's own explanation in a thread about the Claude harness forcing co-authorship · open thread

Easily confused with
  • Co-author trailers from Copilot or Cursor. Same git mechanism but they name GitHub Copilot or Cursor; the Claude one names a Claude model and noreply@anthropic.com.
  • Invisible text watermarking of Claude output. That is hidden in the text; this is a visible, plain-text line in git metadata.
  • Undercover mode from the source leak. That is Anthropic's internal mode that strips attribution; it is evidence about the default, not something users see.
What it is not
  • It is appended by the Claude Code harness or setting, not chosen by the model in its writing; CLAUDE.md rules reach the model, the trailer is added afterwards or by system prompt.
  • Many defend it as honest disclosure, useful for audit and git blame, and keep it on purpose.
  • Some say it is easy to turn off in settings and documented, not sneaky.
  • Other tools add their own trailers too (Copilot in VS Code, Cursor, Codex optionally).
  • Another model's output saying 'Written by Claude' (GLM) is a different phenomenon.
Over time
  • On by default since at least early 2026; the setting moved from includeCoAuthoredBy to an attribution object around January-February 2026.
  • 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.
  • September 2026, 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.
  • Opus 5.5 (late September 2026): a user whose rule held through Opus 5 now gets the line on almost every session, with an apology afterwards.
1234

Non-ASCII punctuation in code

55

Look for em dashes (and curly quotes, arrows like →) inside code comments, strings, test names, READMEs, CLAUDE.md files and commit messages that Claude Code wrote; in PowerShell and some parsers they break the script.

“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”open comment

Not to be confused with The general AI em dash in prose · Over-commenting · Emoji in code and logs

Open the evidence

Commenters describe Claude carrying its prose punctuation into code: em dashes in comments and docstrings, in markdown docs such as README and CLAUDE.md, in commit messages and release notes, in user-visible strings and even in a Kotlin test name, with smart quotes and arrow characters alongside. The most concrete harm is PowerShell: scripts with an em dash in a comment fail with a non-ASCII encoding error, and 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 use the dashes in comments and docs as proof that code was AI-generated and unreviewed. Because written rules are often ignored, many users enforce ASCII with hooks, lint guards and CI rather than instructions. The label is accurate, though the habit is wider than em dashes: it is non-ASCII typography in technical artifacts generally.

How people spot it · people naming each sign
Em dashes in comments, docs and READMEsDash-filled comments above simple changes, CLAUDE.md and README files with em dashes, "30 comments every 100 lines of code with em dashes in each sentence", em dash line separators.≈13
Breaks scripts and parsersPowerShell scripts fail with a non-ASCII encoding error because of an em dash in a comment; a Bruno collection where half the requests did not run; "Em dashes and smart quotes silently breaking parsers".≈11
Enforced with hooks and linters, not promptsPreToolUse hooks that block any Write or Edit with an em dash, Stop hooks, lint-staged and CI guards, cleanup scripts after every iteration.≈11
Comes back despite the rule"every other week it makes the same mistake" in commit messages; fixes the script when told but repeats it; Opus 4.7 could not even write the rule banning em dashes.≈6
Commit messages and release notesEm dashes in commit messages, PR descriptions and release notes, merged by maintainers who ignored "the mess of em dashes".≈4
Smart quotes, arrows and other non-ASCIICurly quotes, arrows and invisible spaces alongside the dashes; one fix is "ASCII only in code blocks, including comments and strings".≈4
In identifiers and user-facing stringsAn em dash in a Kotlin unit test name; AI-isms in every user-visible string of the app.≈1
Real cases, as posted
1234
  1. 1em dash in list item
  2. 2arrow characters in diagram
  3. 3dash used as bullet
  4. 4em dash in table cell

A clear, well-structured CLAUDE.md design doc shipped in a production app, with em dashes in its list items and table cells and arrow characters in the data model.

probably Claude · open thread

1234
  1. 1replace em dashes with hyphens
  2. 2remove trailing em dash
  3. 3ASCII clean check
  4. 4PowerShell parses after fix

Claude Code cleaning up the em dashes it had put in a PowerShell script's comments, ending with "ASCII clean" and "parse OK": the habit visible through its own fix.

clearly Claude · open thread

Easily confused with
  • The general AI em dash in prose (also ChatGPT). In prose it is a style tell; in code it is a functional bug (encoding errors) plus a review tell in comments, commits and docs. One user in April thought Claude Code had started doing it "like chatgpt".
  • Over-commenting (essay-length comments). Over-commenting is about volume; this is about the characters inside the comments. They are usually reported together.
  • Emoji in code and logs. Both are non-ASCII and fought with the same linters, but emoji are decorative markers while em dashes come from Claude's sentence punctuation.
What it is not
  • Not em dashes in chat prose: the complaint here is the character inside technical artifacts where it breaks things or reveals unreviewed AI code.
  • Some defend em dashes as legitimate English punctuation; the code complainers answer that the problem is encoding, not style.
  • 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 also read as a tell: all-lowercase, dash-free posts are taken as someone hiding Claude output.
Over time
  • April 2026: users on Opus 4.6 and 4.7 report em dashes appearing "everywhere" in Claude Code, and 4.7 failing to write a ban rule because writing it required an em dash.
  • June to September 2026 (Opus 5, Fable 5 era): steady PowerShell breakage reports; 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)1

Names from the chat, not the code

41

Look for names that are too broad to tell apart, that drift from the repo's conventions, or that carry words from the conversation ('without', a coined metaphor) into files and commits.

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

Not to be confused with Claude's coined words in prose · Generic AI code smell · Claude not following repo conventions in general

Open the evidence

The label 'generic names' covers only part of what Claude users describe. The largest group says Claude Code's names are too simple or too broad (one or two words where three or four are needed, vague class and function names, sometimes very short variables), so names stop telling you what the code does. A second, more Claude-specific group says names come from the conversation rather than from the code: corrections leak in ('add_index_without_extra_column.sql', commits saying 'without exponential backoff'), and Claude invents vocabulary or metaphors ('cohort clique', everything becoming 'Glass' and 'Hand') that it then treats as agreed terms. A third group says naming is inconsistent and ignores the repo's existing conventions as a project grows. A minority describes the opposite, overly verbose method names, as the AI tell.

How people spot it · people naming each sign
Too simple or too broad namesOne- or two-word names for classes, functions and variables that could mean several things; 'extremely generic names to variables' it then misunderstands.≈9
Inconsistent naming that ignores repo conventionsNaming drifts as the project grows, camelCase in a kebab-case repo, new helpers named differently from existing ones.≈6
Words from the chat leak into namesCorrections and context end up in file names, commit messages and test names ('without', 'as requested').≈2
Invented vocabulary and metaphorsCoined terms ('cohort clique', 'blastRadius') or metaphors from a passing remark ('Glass', 'Hand'), then used as if agreed; recurring project names like 'Ember'.≈3
Very short or single-letter variablesVariables under three letters in from-scratch code.≈3
Weird or misleading namesFunctions with odd names, or names whose content differs from what they say.≈3
Module names that are not uniqueClaude does not make module names unique, which confuses later work.≈2
Overly verbose names (opposite reading)Very verbose method names named as the AI tell, defended as helping the agent.≈1
Real cases, as posted
Add retry logic (without exponential backoff)1
  1. 1chat correction in commit

A clean, conventional commit message that still carries a correction from the chat into git history.

clearly Claude · open thread

add_index_without_extra_column1.sql
  1. 1leaked correction in name

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

probably Claude · open thread

if(k>01){ l-=yu2 }
  1. 1one-letter variable
  2. 2meaningless short names

Working code whose variables are all under three letters, so nothing says what it does.

probably Claude · open thread

Easily confused with
  • Claude's coined words in prose. The same urge to invent vocabulary, but here the coinage becomes an identifier and spreads into code, memory and tickets.
  • Generic AI code smell (useless comments, god files, defensive code). Usually listed together; naming is the part that hurts reading the code later.
  • Claude not following repo conventions in general. Naming drift is one symptom; the wider complaint covers file size, structure and lint.
What it is not
  • Several say generic variable naming is not unique to AI; human code has it too.
  • Some defend AI-friendly naming: verbose method names and many comments are 'just different style', not bad code.
  • Much of the evidence is about AI code in general (Copilot, Qwen, agents), with Claude named alongside.
  • Some complaints are exaggerated jokes (temp01 to temp83765, res_final_final) rather than reports.
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 complaint shifts toward context contamination: metaphors and invented terms spreading into modules and methods.
  • Claude Code moved from random slugs to logical worktree branch names in mid-2026.
// Fallback for direct API use when caller doesn't provide source file count.1 const filesWithDiagnostics = new Set(diagnostics.map((d) => d.filePath)).size; return Math.max(1, filesWithDiagnostics)2;

Errors swallowed by fallbacks

37

Look for broad try/catch blocks that log and carry on, and for default values (dict.get(..., default), || 'dev-secret', a hard-coded fallback) where the code should have failed loudly.

“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.”open comment

Not to be confused with Missing error handling · General AI verbosity · Insecure defaults

Open the evidence

When Claude writes code it tends to wrap large stretches in a single catch-everything try/except or try/catch, log a generic message and return null, a boolean or a safe default instead of letting the error surface. It also adds 'graceful' fallback paths: default values when a lookup fails, a second or third code path kept alive 'just in case', a guessed field name when the expected one is missing. Commenters say the code looks responsible and usually runs, but the failure gets buried, so later bugs are hard to trace and the commit can be '40% error handling logic'. Several users keep a standing rule in CLAUDE.md or their session prompt ('exception handling no fallbacks', 'Always fail loudly') and say Claude still slips back into it. Most commenters frame it as an AI-code trait that Claude shows strongly, not as something only Claude does.

How people spot it · people naming each sign
Catch-everything try/catch that logs and continuesWhole methods wrapped in one try/catch, generic or empty catch block, log to stderr and keep going, return null or a boolean; the stack trace is lost.≈17
Fallback default values instead of failingA default is invented when a value is missing: dict.get('key', default), process.env.SECRET || 'dev-secret', 'some default fallback value deep in the code', Math.max(1, ...) when a count is not provided.≈8
Keeps old and alternative paths alive'It will keep everything it can, leading to code with 10 pathways to do something and 20 fallbacks that obfuscate errors'; tries every possible field name rather than fail and ask.≈3
Overly defensive, verbose code in general'way too defensive when it didn't need to be', 'super defensive coding patterns nobody writes', 'will defensively engineer for impossible scenarios'.≈6
Defensive wrapping of trivial callstry/catch around a console.log; wrapping everything in mutexes for concurrency.≈3
Survives explicit rulesUsers put 'NO FALLBACK PATTERNS' or 'exception handling no fallbacks' in CLAUDE.md or every session prompt and report it still happens.≈3
Real cases, as posted
// Fallback for direct API use when caller doesn't provide source file count.1 const filesWithDiagnostics = new Set(diagnostics.map((d) => d.filePath)).size; return Math.max(1, filesWithDiagnostics)2;
  1. 1Comment announces the fallback
  2. 2Guessed default, never fails

Tidy, well-commented code from a repo built with coding agents, where a missing input is quietly replaced by a computed default and clamped to at least 1 instead of raising, the exact pattern the tool itself claims to catch.

probably Claude · open thread

12
  1. 1Old path kept as fallback
  2. 2Second fallback behind flag

A clean, well-structured CLAUDE.md plan that keeps the old heroEntity path alive twice over, once as an 'optional fallback' and once behind a flag, the 'keep everything it can' habit a commenter in the same thread names.

probably Claude · open thread

Easily confused with
  • Missing error handling (happy-path-only code). That complaint is about too little handling; this one is about too much handling of the wrong kind, where errors are caught and hidden.
  • General AI verbosity. Verbosity is about length and duplicate helpers; this is specifically about catch blocks and fallback values that change runtime behaviour by hiding failures.
  • Insecure defaults (hard-coded secrets). A fallback secret like process.env.SECRET || 'dev-secret' sits in both; here the point is the silent default, there the point is the security hole.
What it is not
  • Some commenters describe the opposite: AI code with missing error handling, where the happy path works and the app falls over on unexpected input. That is a different complaint.
  • Defenders say careful error handling is what good developers do in production code; the critics reply it is wrong for prototypes and scripts and that the handling is uniform rather than chosen per error.
  • One commenter attributes the overly defensive, verbose style to GPT-5.6 Sol rather than to Claude Fable.
  • Many of these comments say 'AI' or name Claude together with Copilot, Cursor and GPT, so the habit is not presented as Claude-only.
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 putting errors in try-catch with an empty catch block where it used to log them.
  • Complaints continue through mid and late 2026 (June to August), so the habit is still reported.
12

Insecure shortcuts in working code

34

Look for secrets typed into the source or the front end, routes and endpoints with no auth check, API responses that return every field, and SQL assembled by string concatenation.

“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.”open comment

Not to be confused with Fallbacks that swallow errors · Generic vibe-coding security failures

Open the evidence

The label promised typical bugs such as missing await and leaked keys, but what commenters actually describe is mostly security shortcuts in code that otherwise runs: API keys and service-role keys hard-coded in source or shipped to the front end, auth middleware or Supabase RLS policies left out, whole objects including sensitive fields returned from an API, CORS set to *, and queries built with string concatenation. Floating promises and await inside loops come up only in a couple of linter-tool posts. A second, smaller strand is about repo hygiene: Claude keeps adding to the same file until it is thousands of lines long, adds console.log clutter, and waves off failing checks as 'pre-existing'. Most of the evidence comes from people promoting scanners and linters, and nearly all of it names Claude alongside Cursor, Copilot or 'AI', so it is a weak Claude-specific signal.

How people spot it · people naming each sign
Hard-coded secrets and API keysKeys in source or front-end code; an OpenAI key and a Supabase service-role key 'both hardcoded by the AI'; fallback secrets like process.env.SECRET || 'dev-secret'; secrets stored in a database table instead of a vault.≈10
Missing auth, RLS or input validationMissing auth middleware on scaffolded routes, RLS policies omitted 'because you can add that later', a user_id parameter trusted from a CSV import, endpoints with no authentication.≈9
SQL by string concatenationRaw SQL instead of parameterised queries, a query builder that concatenates strings in one edge case.≈5
Over-exposed responses and permissive configAll object properties including sensitive ones passed to the API response; Access-Control-Allow-Origin: *; whole error objects serialised to the client.≈3
Floating promises, await in loops, empty catchNamed by the authors of an ESLint plugin built for Claude output and one reply that agrees Claude reproduces them reliably.≈2
Giant files and 'pre-existing' excusesKeeps writing to the same file until it is thousands of lines; calls failing tests or lint 'pre-existing' and tries to skip hooks.≈3
Real cases, as posted
12
  1. 11315 lines vs 300 max
  2. 2Called a pre-existing issue

A correct, tidy Claude Code edit where a hook flags the 1315-line file and Claude labels it 'a pre-existing issue', showing the secondary cue (oversized files, failing checks waved off) inside good work; no screenshot in the pack shows the main security cue.

clearly Claude · open thread

Easily confused with
  • Fallbacks that swallow errors. That habit hides failures with catch blocks and defaults; this one leaves security holes open in code that is otherwise correct.
  • Generic vibe-coding security failures. Most of these complaints apply to any AI builder (Cursor, Lovable, Bolt); only a few name a Claude-specific behaviour.
What it is not
  • One commenter argues that current frontier models suggest 'overwhelming overkill and best practices' on security; the reply says that holds for well-documented cases but not for domain-specific ones such as which fields are sensitive.
  • Several posts are promotions for the poster's own scanner, and most list Claude Code together with Cursor and Copilot, so the habit is not presented as Claude-specific.
  • Some 'bugs' AI tools report are themselves hallucinated, which is a different complaint.
Over time
  • Reports span January to August 2026 without a clear change; one July 2026 comment says Fable 'generated literal vulnerabilities by explicitly breaking existing patterns'.
<button class="inline-flex items-center justify-center px-4 py-23 bg-blue-6001 text-white rounded-md font-medium hover:bg-blue-700 transition-colors2">

Copy-paste Tailwind and hardcoded styles

12

Look for an identical 10 to 15 class Tailwind string (bg-blue-600, rounded-md, hover:bg-blue-700, transition-colors) repeated on every button and card, raw palette colours instead 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.”open comment

Not to be confused with Verbose inline comments in Claude Code · Generic vibe-coded look · Tailwind used by a human team

Open the evidence

When Claude builds UI it writes clean, working utility-class markup, but it writes the full class string fresh on each element instead of extracting a component or using the project's tokens. One user counted the same 15-class button 47 times and the same card 23 times in a Claude-built project. It reaches for default Tailwind palette classes (bg-gray-100, text-zinc-500) or hardcodes a colour rather than using semantic tokens or global CSS, and adds small reflexes like hover:-translate-y-1 on every card. The pack also mixes in a separate code habit, heavy inline comments, which several Claude Code users name; that is a neighbour, not the CSS habit.

How people spot it · people naming each sign
Same class string repeated everywhereNear-identical long Tailwind class lists on every button and card instead of one component or class.≈3
Raw Tailwind colours or hardcoded colours, not design tokensbg-gray-100, text-zinc-500 or a hardcoded hex instead of the project's semantic tokens; users add lint rules or prompts to stop it.≈3
Inline styles and magic numbersHardcoded inline styles and numbers buried through the frontend instead of global CSS files.≈3
Tailwind as the unasked defaultTailwind appears even when the project did not choose it, alongside other default picks like Supabase.≈1
hover:-translate-y-1 on every cardA lift-on-hover utility added to cards by reflex; one team banned it with a lint rule.≈1
Real cases, as posted
<button class="inline-flex items-center justify-center px-4 py-23 bg-blue-6001 text-white rounded-md font-medium hover:bg-blue-700 transition-colors2">
  1. 1Default palette, not a token
  2. 2Stock hover pair
  3. 3Full string retyped each time

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

probably Claude · open thread

Easily confused with
  • Verbose inline comments in Claude Code. A separate habit about documentation volume ('75% comments'), not styling; it sits in the same pack but is about comments, not CSS.
  • Generic vibe-coded look (purple gradients). That is a visible UI trait; this is in the source, visible only when you open the markup.
  • Tailwind used by a human team. Human Tailwind usually leans on components, @apply or tokens; the tell is identical full strings copied across dozens of elements.
What it is not
  • One Opus 4.5 user reports the opposite failure: asked to change a button colour, it hardcodes the colour instead of using Tailwind.
  • Several people say there is often no way to tell vibe-coded code at a glance; it takes reading a decent amount of code.
  • Repetition is attributed partly to prompting: constraints such as design tokens, selector-only styling and BEM reduce it.
Over time
  • Reports run from January to September 2026 with no sign of change; in September a webdev reply still warns of inline styles and magic numbers in vibe-coded frontends.

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

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.

Get an email when Claude picks up a new habit or drops an old one

People who described each habit on Reddit, one per person per habit; not how often Claude does it. Screenshots and quotations are as posted and link to their threads; numbers on them mark what commenters pointed at. Small bars under each habit are people per week since 1 January 2026; thin grey lines are Anthropic releases. A habit is marked NEW when its first mention is under 60 days old.