reversa-visor

Extract screens, UI components, and navigation flows from legacy system screenshots.

Updated May 16, 2026
One-click install
npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-visor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-visor
Source: https://github.com/ricardops34/rcg-crm/tree/main/.agents/skills/reversa-visor
Command: npx skills add https://github.com/ricardops34/rcg-crm --skill reversa-visor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams accurately reconstruct a legacy system’s user interface—screens, layouts, navigation, and states—using screenshots alone, without needing the system to be running.

Core Features & Use Cases

  • Legacy UI documentation from images: Inventories screens and captures purpose, usage context, and UI states (loading, empty, filled, error, confirmation).
  • Structured extraction of UI elements: Identifies form fields, validations, table columns and actions, navigation structure, feedback messages, modals, and tooltips.
  • Navigation and state mapping: Maps flows between screens and produces per-unit screen documentation plus global inventory and navigation flow outputs.

Quick Start

Send screenshots of the main system screens (one or multiple at a time) so the skill can document each screen and map it to the correct unit.

Frequently Asked Questions about reversa-visor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document a legacy system UI from screenshots without runtime access?

To document a legacy system UI from screenshots without runtime access, you provide images of the main system screens. The skill extracts screens, UI components, navigation flows, and visible states to reverse-engineer the interface purely from images.

What UI elements can be extracted from screenshot analysis for UI documentation?

Screenshot analysis for UI documentation can extract form fields, validations, table columns, actions, navigation structure, feedback messages, modals, and tooltips. It also captures UI states like loading, empty, filled, error, and confirmation.

Does reversa-visor require specific configuration files to map screen states?

Yes, reversa-visor requires reading reversa configuration and context files to map screen states deterministically. It uses repository-specific configuration files to support screen-to-unit mapping and produce structured outputs under a configured folder.

How do I map navigation flows between screens from legacy interface images?

To map navigation flows between screens from legacy interface images, you submit screenshots of the main system screens. The skill inventories each screen and maps the flows between them to produce per-unit screen documentation and global navigation flow outputs.

Are the outputs from screenshot reverse engineering destructive to the existing repository?

No, the outputs from screenshot reverse engineering are non-destructive. The skill produces per-unit screen documentation, a global inventory, and navigation flow outputs strictly under the configured output folder without altering existing repository files.