reversa-docs-mapper

You can visualize legacy codebase architecture in 3D by mapping source files into a navigable Code City. This Skill extracts spatial architecture maps and renders 3D visualizations using Three.js to represent module structures and dependencies.

Generating navigable module maps from source code is best handled by extracting dependencies and producing 2D force-directed graphs. This Skill uses D3 to render module topologies into web-ready HTML artifacts for documentation pipelines.

Yes, you can generate architecture documentation as static HTML artifacts. The mapper produces web-ready HTML pages that regenerate architecture, modules, and topology visualizations directly from your existing source code.

The mapper gracefully handles missing sources during architecture extraction. It processes optional references to external assets, scripts, and dependencies while mapping the codebase without failing on incomplete project structures.

You need force-directed graphs for 2D module maps and Code City visualizations for 3D architecture representation. This Skill applies both techniques simultaneously, using D3 for module topologies and Three.js for spatial architecture rendering.

Limitations when mapping codebase dependencies involve handling incomplete or missing source files during extraction. The mapper mitigates this by gracefully processing optional asset and script references, though heavily obfuscated legacy code may reduce mapping accuracy.