Architecture mirror for vibe coding
Vibe coding makes you move fast — but the architecture quietly bloats. oh-my-mermaid keeps a living diagram of your codebase, automatically.
The problem
01
AI writes code faster than you can think. Modules pile up. Dependencies multiply.
02
Nobody updated the diagram. Nobody knows what connects to what anymore.
03
Your own codebase becomes a black box. Debugging becomes guessing.
How it works
Install the CLI and register Claude Code skills. The CLI scans your project and generates a .omm/ directory with structured Mermaid diagrams.
$ omm setupTwo Claude Code skills — /omm-scan and /omm-push — let AI analyze your code and write diagrams directly. Architecture stays in sync as you build.
$ /omm-scanView locally or push to cloud. Share with your team via organization workspaces. Drill into any diagram, see diffs, navigate cross-references.
$ omm viewFeatures
Every diagram is plain text (.mmd). Committed to git. Diffable. Reviewable.
Reference another diagram with @class-name. Click to drill down. Navigate with breadcrumbs.
/omm-scan and /omm-push ship as Claude Code skills. AI writes diagrams, CLI owns the files.
Push your architecture to the cloud. Share read-only links with stakeholders or embed in docs.
Create organizations, invite editors, manage seats. Everyone sees the same living architecture.
File watcher + SSE means the browser updates the moment you save a diagram.
Install
$ npm install -g oh-my-mermaid$ npx oh-my-mermaid setupCLI
omm setupRegister skills with Claude Code and AI toolsomm listList all architecture classesomm show <class>Print all fields for a classomm diff <class>Show diagram diff from previous versionomm refs <class>Show which classes reference this oneomm viewStart the local web viewer on :3000omm pushPush .omm/ to cloudomm pullPull .omm/ from cloudomm sharePrint the shareable URLomm org listList your organizations