reversa-visor

Extract components, layouts, navigation flows, and screen states from screenshots into a UI specification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document interface details from screenshots to enable rapid UI spec creation for legacy systems.

Core Features & Use Cases

  • Extract components, layouts, navigation flows, and screen states from screenshots to generate a structured UI specification.
  • Produce design-ready documentation to support reviews, handoffs, and audits without running the system.
  • Use case: given a set of system screenshots, generate a complete UI spec that can guide redesign or maintenance work.

Quick Start

Provide a set of legacy-system screenshots to generate a complete UI spec including components, layouts, flows, and screen states.

Frequently Asked Questions about reversa-visor

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

FAQPage Schema
How do I create a UI specification from screenshots of a legacy system?

You can reverse-engineer interface details from screenshots to generate a precise UI specification, capturing components, layouts, and navigation flows without needing a running system instance.

Can I extract components and layout mapping from legacy interface screenshots without accessing the live system?

Yes, you can extract components and map layouts directly from screenshots to produce design-ready documentation, supporting reviews and audits without a running system instance.

What is the best way to document navigation flows and screen states for a complex system redesign?

The best way to document navigation flows and screen states is capturing multiple screenshots to generate a complete UI spec, producing design-ready documentation to guide redesign or maintenance work.

Does generating UI documentation from screenshots require any dependencies or specific environment setup?

Generating UI documentation from screenshots requires no dependencies or environment setup, as the process reverse-engineers interface details directly from provided image files to output structured documentation.

When should I use screenshot reverse-engineering for UI documentation instead of inspecting a live application?

Use screenshot reverse-engineering for legacy or complex systems where no running instance is required, allowing you to capture multiple screens and states to output structured UI specifications.