reversa-visor

Extract UI components, layouts, and navigation flows from screenshots.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-visor-markson22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-visor
Source: https://github.com/Markson22/MKV-SYTEM/tree/main/.agents/skills/reversa-visor
Command: npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-visor-markson22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document legacy system interfaces from screenshots to capture components, layouts, navigation flows, and screen states, enabling faster UI documentation when the system is unavailable or unstable.

Core Features & Use Cases

  • Extract UI elements from screenshots (components, layouts, and states)
  • Map screens to navigation flows and generate unit-ready specs
  • Use case: quickly create design documentation for a legacy system based on images

Quick Start

Use reversa-visor to document the interface from a set of provided screenshots.

Frequently Asked Questions about reversa-visor

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

FAQPage Schema
How do I document legacy UI from screenshots when the system is no longer running?

You can extract UI components, layouts, and navigation flows directly from screenshots to generate structured markdown documentation and UI maps, avoiding the need for a live system environment.

Can I generate structured documentation from image-based UI analysis?

Yes, image-based UI analysis evaluates screenshots to extract components and layouts, producing structured frontmatter and markdown docs for documentation pipelines.

What is the best way to reverse-engineer interface layouts from images?

The best way to reverse-engineer interface layouts is by analyzing screenshots to map screen states and extract UI components, enabling rapid creation of design documentation for unavailable legacy systems.

Does this approach work for documenting legacy UI without needing the system running?

Yes, this approach is designed to document legacy UI when the system is unavailable or unstable, requiring only screenshots to capture layouts and navigation flows.

How do I map navigation flows and screen states from old system screenshots?

You map navigation flows by analyzing available screenshots to identify UI components and layouts, generating unit-ready specs and UI maps for the legacy interface.