SKILL.md
Coordinated Data Views
Some data has more than one natural representation. A set of locations has both a map and a list. A dependency network has both a diagram and a node table. A dataset has both a chart and a raw table. When both representations are genuinely useful for different tasks, show them simultaneously and keep them synchronized — this is called a coordinated view.
The core rule: any selection or highlight made in one view is immediately reflected in the other.
When to Use Coordinated Views
Use coordinated views when:
- The two representations serve different tasks — the table is for finding/scanning; the visual view is for understanding arrangement or relationships
- Users will frequently move between the two — not just glance at one occasionally
- The dataset is large enough that the visual view alone doesn't identify individual items, and the table alone doesn't communicate how they relate
Do not add a coordinated view purely for visual richness. If users only ever look at the table and ignore the visual view, it adds complexity without benefit.