@GarshytHoel: system-atlas: a skill that builds an explorable isometric map of your codebase / agent / pipeline from one data file ar…

system-atlas: a skill that builds an explorable isometric map of your codebase / agent / pipeline from one data file

arranging the system visually does something for my brain that a wall of text doesn’t

i’ve found it way more useful to build up understanding of a system or a large change through these progressive disclosure style atlases than through docs.

hover to read, click to pin, step inside a box to watch it run, click a packet to see the actual payload. chapters reveal the system a few boxes at a time instead of all at once. the md twin is generated from the same file so it can’t drift

works from both sides.

• building a new architecture and moving pieces around visually before anything is written
• pointed it at a 67 pr stack (don’t ask how i got there) and finally understood how the thing fit together

it also keeps track of every open question in the system. as you clarify or improve things the answers land in the atlas, so “wait did we decide that” has an answer instead of a scroll through slack.

FleetingBits (@fleetingbits): i’ve started having claude turn my codebases into visual diagrams so i can discuss the codebases with claude more easily - the moving dots are data snippets that i can inspect