Video wird geladen...
Video konnte nicht geladen werden
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... show more
165,461 Aufrufe • vor 28 Tagen •via X (Twitter)
38 Kommentare

`npx skills add inkboard/system-atlas`

This is dope thanks for sharing. We’re increasingly using these kinds of visual support skills at No Diet (initially soured by @humanlayer_dev’s show me skill). Seeing really helps my understanding.

@humanlayer_dev 100% - i've been trying recently to read the code again but honestly w/ the pace at which these things sling code it's a losing battle. so at least understanding the basic topology is the minimum. Kind of ironic that we're all back to being eng managers again 😂

ELITE - our team gave it a go and are going to keep using your work. congrats. we did find a lil issue in the HTML template if you want to check it out:

Tysm! I’ll take a look

worked out really well fwiw

Inspiration from this

love it! we're working on something similar for Wasp, but it's coming from the compile-time spec. Will be applying much nicer color theme to it though :)

wicked!

thanks!

Super cool! Curious how you simulated the data flows? Did you just give examples yourself or is that from a live local dev server?

The agent executing the skill picks it up from it’s explorations

@deepok102

I love it

This is very, very cool. I tried building something broadly similar to this but found the diagrams the agents made weren’t entirely accurate. Do you find this skill to be accurate enough?

At least works on the scales that I’ve been testing with. Not sure how it’ll perform at bugger scales

love this! how did you give the visual animation?

just claude doing claude things :)

Please change the name. Everyone I work with has some kind of 'atlas' or 'vortex' or 'forge' and they all do different things. Don't go with the AI naming, for all of our sakes.

i think it might be a little too late now 😅 - i agree w/ you though

I see it in 2D but yes, watching the process and the code is the best way to work

Personally I prefer 2d, so I've build an open source local tool for that called HQ flow! Try it out at

Very good work

ahh this is gonna change the flow 👍🏾 cool

This is the same reason audio-first reading helps some people. The content is not always the problem; the entry point is.

the spatial thing is real, text has no persistent location so your brain re-parses it every read, a map gives each module a fixed address you recall. the hard part is layout stability, if it reflows as the code changes, the map you memorized lies to you next week.

@cosmic_yolo_bot

this is awesome

That interactive codebase map is actually sick. Being able to click through the architecture, inspect payloads, and watch the system run is way better than staring at docs.

Evaluating quantum computing requires comparing it with alternative approaches under realistic constraints in emerging economies.

you got it man

I built a similar tool using nodes instead of isometric called RPM, just runs local on all my repos I love this! going to see if I can add this as a toggle feature to RPM

Does it visualize the diff?

so cool, just starting to play around with it

Gives Jurassic Park computer scene vibes (SGI unix/IRIX FSN)

It cannot work at scale because software is way more highly dimensional that the 3 dimensions that our visual cortex can process.

This is super super cool, my brain is having trouble keeping up with complexity and ended up literally drawing squares in my notebook. Thank you!

👏🏻
