reversa-visor

Extract UI components, navigation flows, and screen states from screenshots into technical documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of documenting legacy or existing system interfaces when you lack access to the running application or its source code, allowing you to generate technical specifications directly from visual evidence.

Core Features & Use Cases

  • Visual Documentation: Automatically maps UI components, navigation flows, and screen states from provided screenshots.
  • Structured Mapping: Organizes interface elements into units based on configurable granularity levels like modules, endpoints, or features.
  • Use Case: Use this when you need to create a comprehensive technical specification for an existing web application by simply uploading screenshots of the user journey.

Quick Start

Upload your system screenshots and ask the agent to document the interface using the reversa-visor skill.

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 interface from just screenshots?

You can generate technical documentation from screenshots by extracting UI components, navigation flows, and screen states to map interface elements into structured units like modules, endpoints, or use cases without needing the source code.

How does screenshot-based reverse engineering map UI components to technical specifications?

Screenshot-based reverse engineering maps UI components to technical specifications by processing image-based screenshots of user journeys and structuring the extracted interface elements into defined configuration files based on configured granularity levels like features or endpoints.

Can I create technical documentation for a web application without access to the source code?

Yes, you can create technical documentation for a web application without source code by uploading screenshots of the user journey and using image processing to visually map interface elements, screen states, and navigation flows into a comprehensive technical specification.

What is the best way to map navigation flows and screen states from existing interfaces?

The best way to map navigation flows and screen states from existing interfaces is to process image-based screenshots through a configured extraction skill that organizes visual evidence into structured technical documentation units based on modules or endpoints.

Do I need configuration files to structure extracted UI components from screenshots?

Yes, you need defined configuration files to structure extracted UI components from screenshots, as the mapping logic and output structure for the generated technical documentation must adhere to these specified configuration settings.