presence

When you're about to claim success ("fixed", "done", "works", "passing tests") at the end of a turn, verify the claim is backed by actual evidence in this session. presence's Stop hook will flag a success claim that has no recent test/build pass behind it. Be aware of this gate and either run the verification, or hedge the claim explicitly.

When you're about to claim a previous fix worked, or are tempted to repeat an approach Claude Code has tried in this repo before, consult the outcome telemetry. presence tracks every commit Claude made and watches for reverts. Look up "did my last attempt at X stick?" before re-trying.

When working in a codebase you've touched before, consult and update the persistent project model maintained by presence. The model lives at ~/.claude/presence/projects/<repo-id>/model.md and contains terse notes about architecture, conventions, and verified facts. Use it BEFORE re-deriving things you've already learned, and APPEND to it when you confirm something non-obvious that future sessions will benefit from knowing.