Install & start
Two steps to a rendered diagram: install Studio, then author your first file.
1. Install Studio
Choose your host. VS Code-compatible editors use the Open VSX extension; JetBrains and Obsidian have separate plugins.
In Cursor, VSCodium and Windsurf you can also just search Transitrix Studio in the Extensions panel — they read Open VSX.
On stock VS Code, take the file instead. Microsoft's build reads only its own marketplace, so an Extensions search will not find Studio there. Download the .vsix from the Open VSX listing, then use Extensions → … → Install from VSIX…, or run code --install-extension transitrix-studio-*.vsix. Same build, same version.
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.
Marketplace status and release verification — review the evidence and its scope before installing.
Obsidian Desktop — manual installation
Watch the Obsidian walkthrough (1:52, English narration) to see source editing, goal diagrams and light/dark themes with close-ups and object highlights.
Transitrix Studio 0.1.1 previews self-contained diagram YAML in your notes. Requires Obsidian Desktop 1.0.0 or newer.
- Download
main.js,manifest.jsonandstyles.cssfrom the assets of release 0.1.1. - In your vault, create
.obsidian/plugins/transitrix-studio/and place all three files directly inside it. - Restart Obsidian. In Settings → Community plugins, turn Restricted mode off to allow plugins, then enable Transitrix Studio.
- Copy a worked code block from the demo notes into a note and open it in Reading view.
Supported blocks: Goals, DGCA, DGA, Action network, Action Card, Blocks and Process Blueprint. See fence names and settings. Live Preview and mobile are not supported. Each block must contain its own diagram data: view_config-only documents and sources references are rejected. Notes are not modified by the plugin.
2. In a code editor: 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:
- Empty folder — your organisation's Transitrix repository, from scratch:
canon/,field/,codex/zones, thetransitrix.yamlmanifest,AGENTS.mdrole guides, and a GitHub Actions CI workflow that validates every pull request. - Existing repo — orients itself and adds a first file.
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:
- Clone the repo, open it in your editor (viewers installed — see above).
- Read
AGENTS.mdat the root — zones, notations, conventions. - Edit or add a file, then
npx @transitrix/cli validate <file>. - Open a pull request — CI re-validates automatically.
Next
- Full methodology specification: github.com/transitrix/methodology
- All supported notations: notations on GitHub
- Worked example repository: github.com/transitrix/acme-corp
- Studio source & issues: github.com/transitrix/transitrix-studio
- Early-adopter pilots or questions: [email protected]