{"id":79637,"plugin_id":"plugins_6ab42aaa4d808191be10baa770d399ad","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-04T00:11:33.491Z","digest":"fdea4c18eda1ab379aeaadcb6a4f87525dbf31b1516d25dfed0cfa570adf1cc2","against":null,"payload":{"description":"Create static conceptual diagrams, process illustrations and map-like graphics with truthfulness about spatial data.","included_files":[],"name":"diagram-and-map","skill_md_contents":"---\nname: diagram-and-map\ndescription: Create static conceptual diagrams, process illustrations and map-like graphics with truthfulness about spatial data.\n---\n\n\n# Diagrams and map-like images\n1. Clarify visual's role: conceptual explanatory artwork versus a precise schematic, navigable map or editable diagram.\n2. For static conceptual graphics, define nodes, labels, arrows, constraints, hierarchy and legend before rendering.\n3. For real routes, geographic locations, map distances or accurate quantitative positioning, use real map/data tools instead of drawing fictional coordinates.\n4. Keep process order, directions and labels consistent. Check graph edges, arrow semantics and relationships against the source.\n5. Use `../../references/diagrams-and-geography.md`; disclose when visual is illustrative/not to scale.\n6. Generate a static visual only if it can meet the output contract; otherwise use structured diagrams/tooling and say why.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}