Install & start

Two steps to a rendered diagram: install Studio, then author your first file.

1. Install Studio

Pick your editor — the extension is the same everywhere.

VS Code / Cursor / VSCodium / Windsurf JetBrains IDEs

Or search Transitrix Studio in your Extensions panel. Sequence, state and ER/class diagrams render natively via PlantUML — no extra extension needed. For lighter, quicker views, add Markdown Preview Mermaid Support alongside it — same plain-text model, no lock-in.

2. Scaffold your repo — or just a first file

Paste this into any coding agent — Claude Code, Cursor, Copilot Chat, Gemini CLI — from the folder you want to work in:

Fetch and follow
https://raw.githubusercontent.com/transitrix/methodology/main/transitrix/skills/onboard/SKILL.md
— for any templates/<file> path it references (incl. ${CLAUDE_SKILL_DIR}/templates/<file>),
fetch it instead from
https://raw.githubusercontent.com/transitrix/methodology/main/transitrix/skills/onboard/templates/<file>

It asks what you want to model, then scaffolds accordingly:

Either way, open the result in your editor — the diagram renders as you type. Skill source →

Using the Claude Code plugin workflow instead?

Same result, from the terminal claude CLI:

/plugin marketplace add transitrix/methodology
/plugin install transitrix@transitrix-methodology
/transitrix:onboard

No coding agent to hand? Clone the worked example instead and open any .transitrix.yaml file under canon/ — see it rendered before you author your own.

Joining a repo your team already has

Someone already set up the model — clone it and contribute like any other change:

  1. Clone the repo, open it in your editor (viewers installed — see above).
  2. Read AGENTS.md at the root — zones, notations, conventions.
  3. Edit or add a file, then npx @transitrix/cli validate <file>.
  4. Open a pull request — CI re-validates automatically.

Next