Flow visualiser

three views on how Primoro modules behave and interact

Different angles on the same corpus. The module dependency map is the 10,000-ft overview of which modules talk to which. Per-module flows drill into how a single module works internally + its outbound calls. User journeys are the cross-module behavioural narratives a designer or developer would explain to a stakeholder ("here's how booking an appointment actually works end-to-end").

🔗

Module dependencies

Force-directed graph of declared + Claude-inferred relationships between every module. Filter by tier, suite, edge kind, confidence. Click a node to inspect its neighbours.

37 modules 190 edges
⤳

Per-module flows

For each module, a flowchart of its internal steps + outbound module calls, extracted from the UX + technical specs. Multi-platform tagging — toggle pills to see web vs tablet vs mobile journeys.

2 flows generated · jump to any module
🧭

User journeys

Cross-module sequence diagrams for end-to-end user tasks. Each participating module is a column; messages flow top-to-bottom. Best for "explain this feature to a developer in one diagram".

1 journey · + create new

Recently generated per-module flows

Recently generated journeys