omm
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
Run omm init. The CLI scans your project and generates a .omm/ directory with structured Mermaid diagrams for each architectural domain.
$ omm initTwo Claude Code skills — /omm-init and /omm-scan — let the AI analyze your code and write diagrams directly via the CLI. Architecture stays in sync as you build.
$ /omm-scanSpin up the local viewer. Real-time updates via SSE. Drill into any diagram, see diffs between versions, and navigate cross-diagram references.
$ omm serveFeatures
Every diagram is plain text (.mmd). Committed to git. Diffable. Reviewable.
See exactly what changed between two versions — added nodes in green, removed in red.
Reference another diagram with @class-name. Click to drill down. Navigate up with breadcrumbs.
omm-init and omm-scan ship as Claude Code skills. AI writes the diagrams, CLI owns the files.
File watcher + SSE means the browser updates the moment you save a diagram.
Node.js http module only. Mermaid and Markdown rendered client-side via CDN.
Install
$ npm install -g oh-my-mermaid$ npx oh-my-mermaid init$ npm install -D oh-my-mermaidCLI
omm initCreate .omm/ and install Claude Code skillsomm 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 serveStart the local web viewer on :3000omm statusSummary: class count, last updated