I'm building a zork-like dungeon explorer for vibe coded projects. Ok, the zork interface is not that important, but it adds an extra layer of fun, and does ref

I'm building a zork-like dungeon explorer for vibe coded projects. Ok, the zork interface is not that important, but it adds an extra layer of fun, and does reflect the reality of how I dig through a codebase to understand it. You start at the entry point and start exploring each code path to build a map of what is going on, taking notes as you go, and using tools if you're lucky to get a sense of the overall structure. You can also go up and down a level of abstraction like going up and down a dungeon. It incorporates also complaints from a static analyzer for Python and Javascript that detects 90+ vibe slop anti-patterns using mostly ASTs, and in some cases AST + small language models. The complaints give the local class and methods a sense of how much pain they are in, so I give the code a sense of its own emotional state. I also build data flow schematics of the entire system so I can visualize the project as a wire diagram, which is very helpful to quickly see what is going on.