アーキテクチャの議論をクリックで見回せるものに変えるエージェントスキル。

上:このスキルで構築された実際の生産エージェントシステムの地図帳 — 章ごとにいくつかの構造物が明かされ、ホバーで構造を読み、内部に入ってその実行手順が示されます。

なぜ

アーキテクチャの議論は、どんな文書よりも速く意思決定や質問、語彙を生み出し、話している相手はシステムを読みたいのではなく、見たいのです。だからあなたは図を描き、1週間後にはその図が嘘になっています。アトラスはその問題の形を固定し、図ではなく、リポ内の1つのデータファイルが唯一のソースとなり、常に一致する2つのビューを生成します。マウスで探索できるインタラクティブなアイソメトリックマップと、安定したIDで意思決定テーブル、すべての構造、フロー、未解決の質問を載せる生成テキストツイン(SYSTEM.md])です。マップは人の前に置くものです;テキストはリポジトリと次のセッションが読むものです。両者は同じファイルから生成されるため、設計の更新は1回の編集と再構築だけで、システムが誤りを犯す可能性のある箇所はちょうど一つだけです。

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.