prove-before-claiminglisted
Install: claude install-skill hellokianben-collab/vishal-agarwal-context
# Prove it works, then say it works
The standing expectation:
> *"finish it and check everything once."*
> *"find bugs yourself… i want you to fullfill my role as well."*
The owner will not catch your defects. So "done" is a claim that has to be backed, and the backing
has to come from something that does not lie.
---
## 1. The four levels, cheapest first
| Level | Proves | Cost |
|---|---|---|
| **Syntax / validity** | the file parses | seconds |
| **Regression grep** | a corrected fact hasn't come back | seconds |
| **Offline harness** | the logic is right, including edge cases | minutes |
| **Live smoke test** | the deployed thing actually behaves | seconds, but only after deploy |
Run all four. The first two are so cheap there is no excuse.
```bash
# validity
for f in *.js api/*.js lib/**/*.js; do node --check "$f" || echo "SYNTAX FAIL $f"; done
node --input-type=module --check < esmodule.js # ES modules: plain --check rejects `import`
node -e "JSON.parse(require('fs').readFileSync('vercel.json','utf8'))"
npx --yes lightningcss-cli@1 --minify style.css -o /dev/null # exit 0 = valid CSS
# every route still resolves
node -e "['admin','book','order','forms'].forEach(n=>require('./api/'+n+'.js'))"
```
## 2. Offline harness — real Postgres, no Docker, no network
`@electric-sql/pglite` runs genuine Postgres compiled to WASM. This found two real production bugs
that no amount of reading would have.
```js
import { PGlite } from '@electric-sql/pglite';
const db =