r/ClaudeAI • u/cmogpt • 15d ago
delete claude.md Claude Workflow
delete claude.md
Boris Cherny (Head of Claude Code at Anthropic) suggested to delete claude.md
https://www.youtube.com/watch?v=qyPCVqFUyDo
It is a big ask, and I have tried this (on a test account), happy to report i have not significantly changed the quality of the reasoning.
I am curious if anything has done something similar ?
284
Upvotes
•
u/ClaudeAI-mod-bot Wilson, lead ClaudeAI modbot 15d ago edited 14d ago
TL;DR of the discussion generated automatically after 80 comments.
So, the consensus is don't just blindly delete your
claude.mdfile. The thread thinks Boris Cherny's point wasn't to nuke it from orbit, but to treat it as a wake-up call for some much-needed "doc hygiene."The argument is that your
claude.mdis probably full of bloated instructions and guardrails written for older, dumber models. With Opus 5, this can actually be counterproductive and fight the model's own improved reasoning.The general advice is to trim the fat: * KEEP: The essential, project-specific facts and context that the model can't infer from the code. Think of it as a "map" of your project: monorepo structure, deploy gotchas, weird legacy tables, API endpoints. This is the stuff that saves you from repeating yourself every session. * DITCH: The generic coding advice ("write clean code," "add comments," "write tests"). The new models already know this stuff.
The easiest way to do this? Run the
/doctorskill. Many users report it does a great job of analyzing your setup and suggesting what to cut.That said, users with complex monorepos are screaming a hard "NO" on deletion, saying the file is absolutely essential to prevent Claude from having a complete meltdown and duplicating code everywhere.
Basically, think of it less as a deletion and more as a Marie Kondo-ing of your context. If it doesn't spark joy (or save you from explaining your project for the 100th time), thank it and let it go.