Interactive System Map
A map people can explore — click a region, get the detail.
Turns your AI into a map-illustration designer — turns a system, network, or territory into a clear illustrated map with clickable regions, layered views, and labels a stranger can read.
Install it in 3 steps
No sign-up. No CLI tools. Pick your AI, copy one line, paste it over.
Prefer doing it yourself? Buy the skill ($4.99), download the ZIP from your checkout confirmation, unzip it into the directory shown above, restart your AI session — same result. Already bought it? Your AI assistant can download it for you.
What’s inside
One SKILL.md (the playbook) + one starter template. A preview:
Interactive System Map
When to use
- Your product is a platform, network, or ecosystem and a static diagram keeps failing to explain how the parts connect
- A docs or onboarding page needs a map of a system — data flows, service regions, office locations, delivery zones — that readers can explore by clicking
- An editorial or explainer piece covers a territory (a city, a supply chain, a campus) and readers keep asking "where is that in relation to this?"
- A dashboard or status page needs a map view where each region or node opens its own detail
- A presentation needs a map that starts simple and reveals layers — regions, then routes, then details — instead of dumping everything at once
Workflow
- Define what the map is for (input: your topic + audience → output: one-sentence map purpose)
Write one sentence: "This map lets a {reader} find {what} and do {action}." A map for finding the nearest service point is a different map from one showing how data flows between regions. The purpose decides what gets drawn, what gets labeled, and what gets left out. If you cannot write the sentence, you do not have a map yet — you have a pile of locations. - Gather verified geography (input: purpose → output: checked location + boundary dataset)
Collect every place, boundary, route, or node the map must show, with coordinates or positions checked against a reliable source — your own product data, an official boundary file, or a published map. Never invent a border, a route, or a location to fill an empty area. Record the source and date for each dataset; a map with stale boundaries is a wrong map wearing a confident face. Decide the map's extent: show only the area the purpose needs, and say so in a caption if the map is cropped. - Draft the base map (input: verified dataset → output: static base illustration)
Draw the base first, without any interactivity: land or background, boundaries, routes, and the nodes or regions that matter. Use one consistent visual language — one line weight for boundaries, one treatment for routes, one symbol family for nodes. Labels go on the base for the handful of places every reader needs; everything else waits for interaction. Check the base at the smallest size it will be shown: if labels collide or routes blur, simplify the geometry before adding anything else.
Template preview
Interactive System Map — Build Template
One map, one purpose. Fill in the purpose first — it decides everything else.
Map purpose
This map lets a {reader} find {what} and do {action}.
Audience: {who uses this map} Map extent: {area shown} — Cropped? {yes/no — if yes, say so in the caption}
Verified dataset
Every place, boundary, route, or node the map shows. No invented geography.
Known gaps: {regions with no data — label them "no data," never leave suggestive blanks}
Base map
Background: {treatment} Boundaries: {one line weight} Routes: {one treatment} Nodes: {one symbol family} Always-labeled places (a handful): {names}
