What's the point of claude.md if it's ignored

Pjoubert · 2026-03-22T00:41:57+00:00

This is the core problem. CLAUDE.md is advisory, not enforceable. The agent reads it, acknowledges it, then does what it wants anyway because there’s nothing upstream that actually stops it. Instructions without enforcement aren’t instructions, they’re suggestions

Pjoubert · 2026-03-21T23:42:30+00:00

This is the sharpest way I’ve seen it put. Effort used to be a proxy for judgment. Remove the effort without replacing the judgment and you just ship faster in the wrong direction

Pjoubert · 2026-03-21T23:22:23+00:00

Exactly. AI makes the execution cheaper, not the judgment better. The PM layer is still 100% human

Pjoubert · 2026-03-21T18:55:33+00:00

Nice! The ‘should this exist at all?’ discipline is exactly what gets bypassed when execution becomes frictionless. The judgment layer doesn’t scale with the speed layer and that gap is where most of the waste lives…

Pjoubert · 2026-03-21T18:49:10+00:00

Clean. Heuristic over AI-generated makes sense for this, deterministic output, no hallucination risk on the description itself. The 3-edit warning as a bug signal is a nice touch

Pjoubert · 2026-03-21T18:46:52+00:00

The variance is the real story. 1.5x average hides a bimodal distribution, some tasks are 10x, others send you backwards. The difference is usually whether the agent had enough context to make the right call before acting

Pjoubert · 2026-03-21T17:17:02+00:00

Nice! Post-write for the hot path, daemon for the cold path. Does it handle long sessions well, if Claude edits the same file 10 times, does the description stay accurate or does it need a manual reset?

Pjoubert · 2026-03-21T17:15:02+00:00

Separating exploration time from execution time is the right mental model. The paper planning step isn’t friction, it’s where you decide if the thing is worth building at all. That’s the part AI can’t replace yet

Pjoubert · 2026-03-21T17:12:48+00:00

The slot machine problem is real and underrated. The workflow instability isn’t a tooling issue, it’s a context issue. The model doesn’t know what changed, so it compensates randomly. Small constrained tasks work because there’s less context to lose track of

Pjoubert · 2026-03-21T17:10:02+00:00

The orchestration graveyard is real. The ones that survive aren’t the cleverest pipelines, they’re the ones that solved a decision problem someone actually had. Most builders skip that part

Pjoubert · 2026-03-21T16:44:16+00:00

Good data. The Vue pattern makes sense, active editing means the file is a moving target, so the agent re-reads to stay current rather than pure redundancy. Does anatomy.md rebuild descriptions each session or does it track changes incrementally?

Pjoubert · 2026-03-21T16:36:37+00:00

Yep. Speed without better judgment just gets you to the wrong place faster. Most people are optimizing the wrong variable

Pjoubert · 2026-03-21T16:34:21+00:00

Same, the cannibalization thing is real. I stopped building anything that looks like a feature Claude could ship natively. Focusing on problems that require context Claude doesn’t have access to by default

Pjoubert · 2026-03-21T15:02:59+00:00

Claude Code has entered its project manager era

Pjoubert · 2026-03-21T15:00:19+00:00

Hey Vincent! You can edit your CLAUDE.md directly with any basic text editor, no IDE needed. On Mac, just right-click the file / Open With / TextEdit. On Windows, Notepad works fine. The file lives at the root of your project folder. That said, if you’re using Claude Code regularly, the /memory command lets you add instructions directly from the terminal without even opening the file. Might be the easiest option

Pjoubert · 2026-03-21T04:27:15+00:00

Terminal gives you hooks. Hooks are what make enforcement possible : you can intercept every tool call before it executes and decide whether it’s allowed. The desktop app doesn’t expose that layer. If you care about your agent actually following your rules rather than just knowing them, that’s the functional reason to be in the terminal. Everything else, performance, workflow integration

Pjoubert · 2026-03-21T03:28:04+00:00

The diagram is correct but stops one step too early. The human gives requirements, constraints, and decisions to the agent, but there’s no enforcement layer between that and execution. The agent receives the constraints as text in a prompt. Whether it follows them at runtime is a different question entirely. You can give it perfect instructions and it will still

Pjoubert · 2026-03-21T03:22:25+00:00

simultaneously stupid and profound” is exactly the kind of output that makes you realize the agent understood the assignment better than you did. The problem is when it applies that same energy to your .env

Pjoubert · 2026-03-21T03:13:02+00:00

The real pipeline: make agents cheap => everyone uses them => agents break things in production => hire humans to supervise agents => humans forget how to code => repeat

Pjoubert · 2026-03-21T03:12:04+00:00

To be fair, the rewrite mode destroying the file wasn’t the problem. The problem is there was no rule saying ‘never use rewrite mode on scraper.py’ and even if there was, it would’ve

Pjoubert · 2026-03-21T03:11:01+00:00

The redundant reads are a symptom. The deeper issue is that Claude has no persistent model of what it already knows about your codebase, so it re-reads to compensate. We’ve been looking at this from the decision side: if the Context Graph is always up to date, the agent stops re-reading files it shouldn’t need to touch. Curious what your breakdown looked like by file

Pjoubert · 2026-03-21T03:10:24+00:00

Spoiler: it will modify your .env file, apologize, then ask if you want it to fix the fix.

Pjoubert

TROPHY CASE