Use when creating or refining UML, flow, system, architecture, or process diagrams where clarity, visual hierarchy, readable labels, and straight-line routing matter more than exhaustive detail.
Design diagrams as communication artifacts first, notation artifacts second.
One diagram should tell one story.
If the diagram is trying to show ingestion, do not also make it explain every schema field, exception path, or implementation detail. Split diagrams before adding clutter.
Identify the primary reading path first.
Make side interactions visibly secondary.
Prefer stages over annotations.
Keep node text short.
Collapse repeated concepts.
Choose one level and stay there:
Do not mix all three in one figure.
State the diagram’s single question.
Mark the primary path.
Demote side paths.
Remove overloaded edge text.
Shorten every node.
Re-check visual scan order.
Re-render and inspect the actual image or PDF page.
Too much text on arrows:
Main flow is unclear:
Side interaction steals attention:
Diagram feels implementation-heavy:
Labels overlap:
Bidirectional arrows look messy:
When using this skill:
design: broader interface and hierarchy directiondesign-audit: critique of finished visual work