- 88comments
- 17comments
- 56comments
- 4comments
- 9comments
- 5comments
- 35comments
- 416comments
- 27comments
- 219comments
- 25comments
- 409comments
- 198comments
- 445comments
- 21comments
- 37comments
- 2comments
- 145comments
- 137comments
- 73comments
- 1comments
- 43comments
- 69comments
- 100comments
- 25comments
- 38comments
- 127comments
- 406comments
- 40comments
- 15comments
I wanted to have the benefits of both, where you can define a diagram in a diagram language, but also retain a high degree of control over what the diagram looks like.
I also wanted this to work well for humans and agents.
On the Github link, there's a playground where you can try it out without installation. There's also instructions for a simple npm install and for installing a skill you can use with Claude or other agents.
Great! Reminds me of Pikchr a bit https://pikchr.org/home/doc/trunk/homepage.md
I like it. I have too many issues with Mermaid
Thanks! I really like Mermaid, but if the diagram gets too complicated, it draws it how it wants and I end up reaching for Draw.io, which is also awesome, but can take a lot of time.
This genuinely fucks. Thank you
Fighting with mermaid is so frustraiting, especially when it comes to normal vs github formatting. This is going to replace several ad-hoc half impls I have laying around
This is basically tikz's positioning library (right=of, below left=of) without having to touch LaTeX. With tikz it was never the nodes that hurt me, it was the edges. Once two edges want the same side of a box it gets ugly fast. Does the resolver do any routing, or is from:/to: all you get? And what happens with conflicting statements, does the first one win or do you get an error?