reversa-visor

You can document a legacy application's UI from screenshots by extracting screen states, interface elements, and navigation flow. This process builds audit-defensible Context-as-Code outputs directly from visual evidence without needing the live system.

Mapping navigation flow from images involves reconstructing main and alternative routes between screens. The process produces a global inventory file and a Mermaid flow diagram to visualize the unit-traversing flow for later design.

Yes, you can extract interface elements from UI screenshots. The documentation process captures form fields, validations, buttons, table columns, row actions, pagination, and feedback UI like modals and tooltips directly from the provided images.

Yes, you need a configuration file to organize extracted screens into units. Screen assignment uses granularity rules sourced from a `.reversa/config.toml` file, optionally overridden by `.reversa/config.user.toml`, to generate per-unit documentation.

The tool handles ambiguous screen mappings by requesting clarification on unclear unit assignments. It preserves existing existing files during generation, ensuring no data is overwritten while appending new screen documentation, inventory, and flow outputs.