Litestore is free. The harness is the paid layer that keeps a fork correct as you change it, running in CI on your own code.
A write ships without invalidating its cache tag.
A nested read skips the soft-delete filter.
A second component is built beside one nobody knew about.
Every check came from a bug this codebase has already paid for.
Stale pages after a write.
A migration that weakens a promise.
Work that was built but never wired up.
A runtime crash the compiler should have caught.
A second way of doing something that already has one.
A code path where a bug costs real money.
.claude/
They drop into .claude, so Claude Code writes changes that match the conventions already in the codebase.
The checks catch a forgotten convention. The guides catch the more expensive mistake: building the wrong thing correctly.
Command
bun run verify
Checks
25, each its own script
Rules
~1,800 lines across 8 guides
Baselines
Existing offenders ratcheted, not blocking
Network
None. Nothing phones home
Scope
Your fork, including modules you add
For teams maintaining a fork
Twenty-five architecture checks and the rule set behind them, so a change that breaks a convention fails in CI instead of in production.
Get the Harness