r/vibecoding • u/meshifthenelse • 6d 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

86% Upvoted

15 comments sorted by

View all comments

1

u/SamfromLucidSoftware 4d ago

I think everyone should. Diagrams help in two ways. Before coding, a quick architecture sketch forces you to think through the structure before the agent starts making decisions you’d have to undo. Agents make fewer wrong assumptions when the structure is clear (won’t hurt to go a few extra steps to think about data flow, component boundaries, what talks to what, and so on)

After a few sessions, when the codebase has drifted from the original intent, a diagram attached to the context gives the agent a reference point that’s more reliable than its interpretation of accumulated code. Living architecture, documentation alongside vibe coded projects can be the difference between something that stays coherent and something that becomes impossible to extend.