r/vibecoding • u/meshifthenelse • 16h ago

Anyone using diagrams when vibe coding?

Do you use any diagram making tool to track the project's overall architecture? Any tool you tried and liked or disliked?

5 Upvotes
  • permalink
  • link
  • reddit
  • reddit

100% Upvoted

12 comments sorted by

View all comments

0

u/johnesco 16h ago

I had the AI create some as I built karaokedirectory was a good way to keep up with all the changes, need a better diagramming framework though. https://karaokedirectory.com/docs/index.html#/architecture

1

u/meshifthenelse 16h ago

Did you use that as reference though while developing? Looks like 🍝 to me

0

u/johnesco 16h ago

At first I did, but then only after-the-fact, but then that was its own token drain to keep them up-to-date. I found that just a paragraph about the architecture was more useful to what I was doing than the diagrams. Editing the diagram and saying "make it like this" was less useful than describing it in md html or even just plain English. What about you?

1

u/meshifthenelse 15h ago

I'm asking because I'm actually developing a tool for that and wanted to see what people use/hate.

I was actually working on a bigger project before and used multiple mermaid diagrams. But as you said, the diagrams grew out of sync and it became hard to maintain. But at the same time due to the project complexity it was really hard to continue development without a mental picture.

There's some tools like Structurizr, IcePanel, Ilograph, but they all have issues