← ClaudeAtlas

provelisted

Capture the BEFORE state while the defect still reproduces, then the AFTER state once the change works, and put both where a human reviewer sees them. Use at the start of any fix, before the first edit, and again once it works. Also when a reviewer would have to take your word for a change.
djnsty23/claude-auto-dev · ★ 3 · AI & Automation · score 65
Install: claude install-skill djnsty23/claude-auto-dev
# Prove Two captures of the same observable, taken at the two moments that make them comparable. Everything else here is detail. **The before capture happens while the defect still reproduces.** That is the only moment it costs nothing, and it is gone the instant you start editing. A session that fixes first and captures second cannot tell "I fixed it" from "it was never broken in the way I described", because both produce one green screenshot. ## Where it goes `.claude/evidence/<slug>/` holds `before.png`, `after.png` for visual work; `before.txt`, `after.txt` for numbers or output. **Not `.claude/screenshots/`.** That directory is gitignored and documented as cleaned each run, so a before state stored there is destroyed by the run that produces the after state. `.claude/` is deliberately not ignored wholesale, so `.claude/evidence/` is tracked and survives. **Tracked means commit it WITH the change, not beside it.** Left uncommitted the evidence dirties the tree, and any gate that refuses a dirty tree then refuses to run at all, which is a self-inflicted block right at the step that needs the gate green. Same commit as the code is also where a reviewer wants it. ## Step 1: before, and it is a probe ```bash mkdir -p .claude/evidence/<slug> ``` Reproduce the defect, then capture. Which observable depends on the change: | Change has | Capture | |---|---| | A visible surface | Screenshot at the viewport the bug appears at. Assert `innerWidth`/`innerHeight` in the same