What it does: 1.Converts between Mermaid, draw.io, and Excalidraw formats 2.Currently supports: Flowcharts and graph-based diagrams 3.Preserves semantic structure and layout in most cases.
Why I built it: Honestly, I was tired of copy-pasting and redrawing diagrams when switching contexts. Plus, many AI coding tools (Claude, Cursor, etc) only generate Mermaid diagrams inside the chat, and sometimes I want the diagrams to be more verbose.
Current state: Working MVP with Flowcharts and graph-based diagrams support
What I'm asking: 1.Does this solve a problem you actually have? 2.What formats/features would make this essential for your workflow? 3.Any issues/bugs/potential improvements you observe?
I'd love honest feedback—even if it's "this isn't useful because X." Trying to validate if this is worth building out further or if I should pivot to something else.
mattewong•4mo ago
OK... this isn't useful to me because I now just only use mermaid and stopped using other diagraming tools, because mermaid can be embedded now in so many places (github, in-browser editing/rendering, shareable URL, python etc), can be easily saved as text and edited (whether manually or programmatically), there are no IP issues, etc. So more useful for me would be, whatever you need to use something other than mermaid for-- do what it takes to make mermaid fill that need, so that there is no need to use anything else.