Use cases

Document a repo with one command.

At the end, your repo is documented in Stable Baseline: folders, documents and diagrams, all written from your code.

Filmed on a sample company, Quillmere. Its people and data are invented.Watch on YouTube

What you need

Any plan, including Free. You bring the AI tool, such as Claude Code or ChatGPT, and connect it to Stable Baseline.
A workspace and a project in Stable Baseline. The welcome at your first sign-in makes your first of each. See Quickstart.
A code repo on your computer, and a terminal open in its folder.
The steps use Claude Code's commands. A tool without commands can take the same request in plain words: see its recipe.

Steps

1
Add Stable Baseline to Claude Code
In a terminal in your repo, run this once:
bash
```
claude mcp add --transport http sb https://api.stablebaseline.io/functions/v1/cloud-serve/mcp
```
Then type /mcp in Claude Code, choose sb, and authenticate. Your browser opens, so you can sign in and choose what Claude Code may reach.
2
Run the setup command
In your repo's folder, start Claude Code with claude. Type /sb:sb-setup and say what you want. For example:
prompt
```
Document this repo for new engineers, with a data model document that draws every table and every link.
```
/mcp__sb__sb-setup does the same.
Choose your workspace and project
Setup finds your workspace and project. If you have more than one, it asks which. It never creates them. If the project already has documents, it asks whether to add to them, replace them, or stop. Replace deletes what is there, so choose it with care.
Watch the project fill
Open your project in Stable Baseline. The Documents tree on the left gains folders and documents. Recent Documents lists each new one, and the counts under Content go up.
Part way through: four folders, five documents and three diagrams so far.
Open a document and its diagram
Press any document in the tree. Its diagrams land in the document as they are drawn. If you asked for a data model, open it to see every table and every link in one diagram.
The data model: every table and every link, filed with the other docs.
6
Change the code, then update the docs
After a code change, type /sb:sb-update and say what changed. For example:
prompt
```
We added GET /orders/:id/receipt in the last commit. Update the docs that cover the components and the order routes.
```
Open the document it edited. The change is there, and the version history records who made it.
The Components table, with the new Receipt routes row added by the update.

Keep it current

Setup also adds a Stable Baseline section to AGENTS.md. It tells your AI tool to keep the docs current as the code changes. If your repo has a CLAUDE.md, add the line @AGENTS.md to it, so Claude Code loads those rules in every session.

What to try next

Ask your tool for more, in plain words:

“Add a sequence diagram of the sign-in flow to the authentication document.”

“What changed in the checkout service this week? Update its document.”

Claude Code recipe

Every way to connect it, and the other commands.

Documents

Edit, share and export what was written.

Diagrams

Change a diagram, or draw another.

Other AI tools

Cursor, ChatGPT, VS Code and more.