The command line that presses RampLab editions: a guided reading of a codebase where every claim carries a code anchor checked against the source.
npm install -g @ramplab/cli
cd path/to/your/repo
ramplab generate . --out lab.spec.json
ramplab preview lab.spec.jsonOr hand it a GitHub URL and it clones into a temporary checkout, presses that, and removes it afterwards:
ramplab generate https://github.com/owner/repoWorth stating precisely, because you are probably installing this on a machine that holds somebody else's source.
- Pressing sends excerpts of your code to Anthropic, under your own credential. That is how the writing gets done and how the verify stage checks it. It is the same request your editor makes when you ask Claude about a file.
- Nothing goes to RampLab while you press. Our servers do not see the repository, the excerpts, or that the press ran at all.
validate,previewandexporttouch no network.publishuploads the finished edition and nothing else. An edition quotes real lines of your source, so those lines go with it. That is the point of publishing one, and it is worth knowing before you do.
This repository is why you can check all of that rather than take our word for it.
If you use Claude Code you already have what you need: the press signs in the
way Claude Code does, so a Pro, Max, Team or Enterprise plan works with no API
key. Set ANTHROPIC_API_KEY to meter it against an API key instead, at
roughly $5 to $30 in tokens per edition. A key takes precedence wherever it is
set, and the press says which one it is about to spend before it starts.
ramplab generate <repo|url> [--out <file>] |
Press an edition. The only command that spends a credential or reads your source. |
ramplab validate <spec.json> |
Check a spec is loadable. Free, offline. |
ramplab preview <spec.json> [--port <n>] |
Read it on your own machine. |
ramplab export <spec.json> --static <dir> |
Write a self contained folder to host anywhere. |
ramplab publish <spec.json> |
Offer it to the library at library.ramplab.dev. |
@ramplab/cli |
The command line itself. |
@ramplab/generator |
The pipeline: map, plan, author, verify, and mechanical anchor resolution. |
@ramplab/spec |
The edition format. Publishing this is what lets anyone build tooling on editions. |
@ramplab/renderer |
The reader, used by preview and export. |
Development happens in a private monorepo alongside the hosted library, and this repository is mirrored from it on release. Issues and pull requests are read and very welcome; a merged change is applied upstream and comes back in the next release rather than being merged here directly.
MIT. See LICENSE.