Extract screens, elements, navigation flows, and states from UI screenshots.
npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-visor-rdinda
Please help me install this Agent Skill. Skill: reversa-visor Source: https://github.com/Rdinda/FMA_Pontos/tree/main/.agents/skills/reversa-visor Command: npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-visor-rdinda
It solves the problem of not being able to clearly document a system’s UI when you only have screenshots, making it hard to recover navigation, components, and screen states without running the legacy application.
Send screenshots of the system screens you want documented for the skill reversa-visor to extract UI structure, screen states, navigation flows, and unit mappings.
High-intent search queries and answers about installing and using this skill.
You can document a legacy system UI from screenshots by extracting screens, elements, navigation flows, and screen states without needing to execute the application. This process maps each screen to a specific documentation unit based on your configuration.
Mapping navigation flows from static images requires identifying links, menus, and submenus to distinguish main and alternative paths between screens. It assigns each screen to an appropriate documentation unit based on the configured mapping granularity.
Yes, you can extract form fields and validations from screenshots for UI documentation. The process captures forms, table columns, actions, filters, and feedback elements like toasts, modals, and tooltips directly from the provided images.
Generating a UX inventory from screenshots requires reading Reversa configuration and state to determine the output folder and mapping granularity. This configuration ensures screenshots and specs are organized into proper global UI inventory outputs.
Documenting screen states using only screenshots limits you to the visual evidence provided in the images. You cannot dynamically trigger loading, empty, error, or confirmation states, meaning you must rely entirely on the states captured in the supplied screenshots.
ricardops34Extract screens, UI components, and navigation flows from legacy system screenshots.
afsjrExtract screens, UI components, navigation flows, and states from screenshots.
speednet-softwareAutomate web navigation, screenshots, and element interactions with Playwright in a sandboxed container.
jetmobsolAutomate browser interactions and capture screenshots using Chrome MCP tools.
