Your tests pass, your linter is green — and the code still isn't written the way your team agreed it should be. Every codebase has standards only a reader can check: services that validate input before doing work, error messages written for the person who hits them, decision records that follow the agreed shape. Nothing enforces them, so they drift — and the coding agents writing more of the code every month were trained against tests that pass or fail, never against your conventions.
Praxis makes those standards enforceable. Write a README spec that says what correct looks like for the files it governs; praxis eval run has LLM reviewers hold every file to it. Recurring findings grow into a named taxonomy of your codebase's real issues — every verdict cached, every run in an append-only ledger, every rate reported honestly. And when the governed documents are knowledge files, praxis compile assembles them into subject-matter-expert agent profiles.
▶ Watch the 7-minute intro — why Praxis exists, what the loop looks like on screen, and where to start.
npm install -g @zarpay/praxis-cliThis repository is organized as three top-level projects:
| Directory | What it is |
|---|---|
cli/ |
The @zarpay/praxis-cli package — source, tests, scaffold, and the design specs. |
site/ |
The documentation site (VitePress), published at zarpay.github.io/praxis-cli. |
demo/ |
Scoop Society — a small ice cream parlor review API that dogfoods the development version of Praxis end to end. |
# Work on the CLI
cd cli && npm install && npm test
# Run the d
5B20
ocs site locally
cd site && npm install && npm run dev
# Exercise the dev CLI against a real project
cd demo && npm install && npx praxis statusBump cli/package.json, update cli/CHANGELOG.md, tag main (vX.Y.Z), and publish a GitHub release — the release.yml workflow verifies the tag against the package version, runs the gate, and publishes to npm with provenance. docs.yml deploys the site on every push to main.
MIT