The harness runs in CI and fails the build when a change breaks a rule the codebase depends on — including the code you add.
It breaks three weeks later, on a page nobody was looking at, for a reason nobody connects to the change. By then the commit that caused it is buried.
A mutation without a cache invalidation. A nested read that skips the soft-delete filter. A component rebuilt because nobody knew the first one existed. All caught before merge.
Cache and freshness, database guarantees, dead code, type and boundary safety, convention discipline, and the paths where a bug costs real money.
Existing offenders are recorded so the harness never blocks you on day one — and a hygiene check watches the harness itself, so allowlists cannot quietly grow.
Around 2,600 lines across eight guides, dropped into .claude so an agent writes changes that match the conventions already in the codebase.
It reads the source in your repository. Nothing is uploaded and there is nothing to sign into.
Running Litestore costs nothing. What costs something is the twenty-fifth change to a codebase you did not write, made by someone who was not there for the first twenty-four.
Litestore itself. Clone it, run it on any number of stores, sell with it.
Keeping a fork correct after twelve months of your own changes.
It is not needed to run a store. It is needed to change one confidently.
Five commands. No account, no CLI login, no dashboard in between.
~/litestore
$git clone https://github.com/litestore/litestore
$bun install
$cp .env.example .env.local
$bun run db:push && bun run db:seed
$bun run dev
✓ storefront http://localhost:3000
✓ admin http://localhost:3000/admin
$ _
the pages people see
the code that talks to the database
the shop logic, 78 folders of it
your database tables
Payment ledgers are append-only. A correction is a new row.
Refunds stay inside the order total, by database constraint.
Stock movements must balance arithmetically.
tests
architecture checks
task kinds
test files
Each its own script
Across eight guides
In 151 files
For the whole team
The checks catch a forgotten convention. The guides catch the more expensive mistake: building the wrong thing correctly.
Problems that already exist are recorded so the checks never block you on day one.
No account, no CLI login, and no dashboard in between.
Reviews and orders are in the same database, so a verified-buyer badge is checked against a real order.
The harness runs in CI on your own code, and the rule set comes with it.