reversa-visor

Documents legacy system interfaces from screenshots by extracting components, layouts, and navigation flows.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/lacsousa/mediclaw-system --skill reversa-visor-lacsousa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-visor
Source: https://github.com/lacsousa/mediclaw-system/tree/main/.agents/skills/reversa-visor
Command: npx skills add https://github.com/lacsousa/mediclaw-system --skill reversa-visor-lacsousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reverse-engineering a legacy system's UI normally requires running the application and manually inspecting every screen. This Skill documents the interface directly from user-provided screenshots, producing structured specs without needing the system to be running. ## Core Features & Use Cases - Screen Inventory: Catalogs each screenshot with its purpose, state (loading, empty, filled, error), and usage context. - UI Element Extraction: Identifies forms, tables, navigation menus, and feedback elements (modals, alerts, confirmations) from images. - Navigation Flow Mapping: Builds a Mermaid diagram of navigation flows across screens and maps each screen to a specification unit based on configurable granularity (module, endpoint, use-case, feature, or custom). - Use Case: A team modernizing a legacy system sends screenshots of the main screens; the Skill produces per-unit screens.md specs, a global inventory.md, and a flow.md navigation diagram for the reverse-engineering documentation set. ## Quick Start Send screenshots of the legacy system's main screens and ask the agent to document the interface from these images.

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 without running the system?▼

Provide screenshots of the system's screens to the agent, which extracts components, layouts, navigation flows, and screen states into structured Markdown specs. The system does not need to be running since all analysis is image-based.

How are screenshots mapped to specification units?▼

Each screen is mapped to a unit based on the granularity setting in the [specs] section of .reversa/config.toml, supporting module, endpoint, use-case, hybrid, feature, or custom folder mapping. Ambiguous mappings are confirmed with the user before saving.

What output files does the screenshot documentation produce?▼

It produces per-unit screens.md specs and copies of the original screenshots, plus a global inventory.md listing all screens and a flow.md Mermaid diagram of navigation flows in the output folder's ui directory.

Does this skill work with AI agents that lack image support?▼

No, it requires a model with image support since all interface analysis is performed on screenshots. It is compatible with Claude Code, Codex, Cursor, Gemini CLI, and other Agent Skills-compatible agents that support images.

What happens if I send the same screenshot twice?▼

The skill follows a non-destructive directive and never overwrites existing files. Duplicate screens are saved with a numeric suffix, such as tela.png and tela-2.png.