The prompt
Put here: the goal, why it matters, who it is for, and how you will judge done.
Keep out: anything you would repeat tomorrow.
A widely shared infographic tells you to delete most of your Claude setup and keep a handful of habits. We checked every one of its 29 claims against Anthropic's own documentation. The direction is right. The absolutes are not — and most setup bloat turns out to be misplacement, not excess.
The infographic is current — it names Opus 5.5 and the merged Chat/Cowork experience — and its instinct is sound. Where it fails, it fails by turning "prune and test" into "delete".
Its strongest line is almost Anthropic's own wording. Anthropic's Claude Code guidance warns that an over-long instruction file gets half-ignored because important rules drown in noise. [6]
Two lines would do damage if followed literally: emptying your instructions and deleting every reusable prompt. Anthropic's method is prune each line, test, and move recurring procedures into skills that load on demand. [6][8]
"It's all one" is half true. Chat and Cowork merged into one conversation; Claude Code still has its own tab. The Capabilities toggle the card points to is an organisation-owner setting, not a personal one. [11][12]
"Ask for HTML" predates living artifacts. Docs, Slides and Design now come back as private, shareable, editable pages that export to Word, PowerPoint or PDF. Ask for the outcome, not the format. [18][19]
Most bloat is misplacement. Facts sitting in instructions, procedures sitting in standing rules, folder maps Claude could read for itself. The fix is a placement map, not a purge. See §03
Claims are paraphrased from the card. A struck-through claim should not be followed as printed; a wavy underline marks a claim that needs a correction. Open any row for the evidence and the source.
Bloat is usually a rule in the wrong place: loaded every time when it is needed once, or written as a rule when it is a fact. Move before you delete.
Put here: the goal, why it matters, who it is for, and how you will judge done.
Keep out: anything you would repeat tomorrow.
Put here: standing rules Claude can't infer — language, hard constraints, format defaults, each with its reason.
Keep out: facts about you, procedures, folder maps. Settings › Your Claude.
Put here: facts about you, your people and your ongoing work. Claude maintains it; you review it.
Keep out: rules about behaviour. Review under Settings › Your Claude › Manage.
Put here: reference files (retrieval handles volume), instructions unique to that work, its own memory.
Keep out: your global rules, repeated.
Put here: repeatable procedures and house style, with a precise "use when".
Keep out: one-offs, and two skills doing one job.
Put here: live data your recurring work needs — calendar, drive, CRM.
Keep out: "just in case" apps. Customize › Connectors.
Put here: commands Claude can't guess, conventions that differ from defaults, known gotchas.
Keep out: anything readable from the code itself.
Put here: rules that must hold every time — formatters, blocked paths, checks.
Keep out: judgment calls; instructions are advisory, hooks are not.
“Would removing this cause Claude to make mistakes?”Anthropic, Best practices for Claude Code [6]
If the answer is no, delete the line. If yes, keep it — and check its wording against current guidance. Six rewrites we see most often:
Why. Emphasis and blanket triggers written for older models now cause overtriggering. Name the condition instead. [2]
Why. Describing the target works better than a prohibition. [2]
Why. Opus 5.5 thinks adaptively and always; effort is the control. Prompts asking for reasoning in the reply may be declined. [1][3]
Why. Generic bans swap one default for another; named patterns stick. [1][2]
Why. A checkable format beats an adjective. Be specific about the output you want. [2]
Why. The reason lets Claude generalise — invoices and follow-ups stay formal too, without another rule. [2]
The card's "Medium" is correct as a default. The professional habit is to move the dial per task — the change applies from the next response.
Sources: [3][14][1]. Thinking cannot be switched off on Opus 5.5 at any level; lower effort lets Claude skip it on simple problems.
Auto lets Claude keep working while automated safety checks screen each action; Manual asks before Claude acts. Anthropic ships Auto on Pro, Max and Team and Manual on Enterprise — one product, two governance postures. A leaner setup should make Claude faster, never less accountable.
A heuristic first pass, not a verdict: it flags patterns Anthropic's guidance warns about, with line numbers. The line test decides.
Runs entirely in this page. Nothing you paste is sent or stored.
Paste into a new conversation. Every cut must cite current Anthropic guidance; nothing changes until you apply it and test it on your own tasks.
Audit my Claude setup against Anthropic's current guidance. Do not change or delete anything yourself. 1. Read what you can see of my setup: Instructions for Claude, this project's instructions, my installed skills and connected apps, and any CLAUDE.md files you can open. If you can't see something, ask me to paste it. 2. Read the live guidance first: Anthropic's prompting best practices, the prompting guide for the model you are running, the Claude Code best-practices page, and the skill authoring best practices. 3. Go line by line. Give each instruction one verdict (KEEP, CUT, REWRITE, or MOVE to memory, a project, a skill, or a hook) using one test: would removing this line make you get something wrong? 4. Justify every CUT with the guidance it rests on, and link the page. If you can't find support, the verdict is KEEP. 5. Flag emphatic wording, rules phrased only as prohibitions, "think carefully" lines, references to older models, duplicates, and anything you would do correctly without being told. 6. Return a table (line, verdict, reason, source), then the rewritten setup, then the three tasks I should run to test it before I apply anything.
Anthropic documentation, read on 26 October 2026. Product details move quickly — recheck before acting on anything time-sensitive.
Method. Each claim on the card was paraphrased and checked against the pages above. Verified means Anthropic states it. Holds means Anthropic's guidance supports it in principle without saying it outright — our judgment, labelled as such. Nuanced: right direction, wrong detail. Overstated: harmful if followed literally. Outdated: the product has moved on. Claims come from the infographic "Delete 90% of your Claude setup" by Ruben Hassid (How to AI). ImageFirm is not affiliated with Anthropic.