Stop teaching agents the same repo rules twice.
Capacitor scores sessions against your rubric and turns durable lessons into repo guidance loaded before the next agent starts.
The same mistake comes back next week.
+ jest.mock("./db", () => ({ ... })) // session 87+ jest.mock("./db", () => ({ ... })) // session 134Your team never mocks the database in this repo. Every new session has to relearn that rule.
Please don’t mock the database in this repo. Use the integration test harness.
I’ll mock the db module so the checkout tests run faster.
Without evals, lessons stay trapped in individual sessions.
The useful lesson becomes repo guidance.
The rule moves from a reviewer comment into the repo’s agent guidance. The next agent reads it before writing code.
Score the session and promote the db-mocking finding.
This repo’s guidance says not to mock ./db in checkout tests. I’ll use the integration harness instead.
With evals, the floor rises without asking every reviewer to repeat themselves.
Evaluations run per session, score against your questions, and emit judge facts. Repeated high-signal facts can be promoted into curatable guidelines that ship at SessionStart. See Evaluations.
Improve your team’s agents, run over run.
Capacitor scores sessions and promotes what worked. Start free to score your team’s first sessions.
Fix flaky auth-token refresh test
Tried mocking the clock first — abandoned after the race persisted. Root cause: token cache TTL rounding. Patched in auth/cache.ts, added regression test. Two approaches rejected, one shipped.