reversa-docs-mapper

You can visualize project architecture by processing module and dependency data to generate navigable 3D Code City visualizations and 2D module maps, revealing system structure and hotspots. This skill converts scattered code metadata into intuitive visual representations for quick comprehension of complex systems.

The best way to generate living documentation for a legacy codebase is applying architecture visualization to reveal structure, dependencies, and hotspots in seconds. This skill produces interactive architecture.html and modules.html pages to speed onboarding and refactoring reviews by converting code metadata into navigable maps.

Yes, creating architecture visualizations requires modules.json and deps.json data files as input. The skill identifies modules, dependencies, and topology from this codebase data to produce navigable architecture visualizations and generate the corresponding architecture.html and modules.html documentation pages.

Yes, you can use three.js and d3 for interactive module dependency maps through interoperability with rendering skills. The mapper leverages these frameworks to render 3D Code City visualizations and 2D module maps from extracted codebase metadata, enabling quick comprehension of complex systems.

Yes, the architecture mapper detects topology during processing and generates a topology.html file when found. This occurs alongside architecture.html and modules.html generation within the reversa-docs workflow, providing a complete navigable visualization of the project's modules and dependencies.

Automated codebase visualization for architecture documentation is not suitable when modules.json and deps.json data are unavailable, as the mapper requires these specific inputs. It also may not be ideal for very small projects where the overhead of generating 3D or 2D maps outweighs the comprehension benefits.