一个能把架构讨论变成你可以点击的代理技能。

上图：真实的生产代理系统地图集，基于此技能构建——章节逐个展示系统结构，悬停读取结构，进入其中展示其执行步骤。

为什么

架构讨论产生的决策、问题和词汇比任何一份文档都快，而你讨论的人想看到系统，而不是阅读它。于是你画了一个图表，一周后那个图表就是谎言。地图集修正了问题的形状，而不是图表本身：仓库中的一个数据文件是唯一的来源，它渲染的两个视图总是一致——一个交互式等距投影地图，你用鼠标探索;另一个**生成文本双胞胎*（SYSTEM.md），用稳定ID承载决策表、每个结构、流程和每个未决问题。地图是你放在一个人面前的内容;文本是仓库和你下一次会话阅读的内容;因为两者都是从同一个文件生成的，更新设计只需一次编辑和重建，系统只有一个地方可能出错。

System Atlas

An agent skill that turns an architecture discussion into something you can click around.

Above: a real atlas of a production agent system, built with this skill — chapters reveal the system a few structures at a time, hovering reads a structure, and going inside one shows its steps in execution.

npx skills add inkboard/system-atlas

Why

Architecture discussions produce decisions, questions, and vocabulary faster than any one document can hold, and the person you are discussing with wants to see the system, not read it. So you draw a diagram, and a week later the diagram is a lie. An atlas fixes the shape of that problem rather than the diagram: one data file in the repo is the single source, and it renders two views that always agree — an interactive isometric map you explore with a mouse, and a generated text twin (SYSTEM.md) that carries the decisions table, every structure, the flows, and every open question by stable ID. The map is what you put in front of a person; the text is what the repo and your next session read; because both are generated from the same file, updating the design is one edit and a rebuild, and there is exactly one place where the system can be wrong.

What you get

• An interactive isometric map — hover a structure to read it, click to pin it, arrow-right to go inside and see its steps in execution, pan and zoom the whole thing. One self-contained HTML file, no build step, no runtime dependencies.
• Progressive-disclosure chapters — a whole system at once reads as noise. Each chapter reveals at most three new structures and runs one small data flow that only touches what you have already seen; the last chapter shows everything with a flow picker.
• Moving data packets you can inspect — the dots travelling the hops are real requests. Click one and the panel shows its route and a representative JSON payload, so “how does a turn actually work” has a visual answer.
• A generated text twin — SYSTEM.md, rebuilt from the same data: the decisions table with ADR links, every structure’s what/how/steps, the flow tables, and the question index.
• Question tracking by ID — every open question gets a stable Q- and a state: open, resolved (with the answer and the date), or routed to a named next step. You can run several rounds of feedback against it without losing track of what was asked or who answered it.
• Role shapes and readable labels — the brain, the stores, the tool decks, the gates and the scheduled jobs each get their own isometric form and a name tag on the canvas, so the map is legible without a key.