reversa-screen-translator

Translate legacy screens into executable UI specifications for parity testing.

1|Updated Nov 20, 2025

Search Tags:#automation #specification #translator #parity #screen #legacy-ui

Ready to run

npx skills add https://github.com/stribus/pygerengastos --skill reversa-screen-translator-stribus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reversa-screen-translator
Source: https://github.com/stribus/pygerengastos/tree/main/.agents/skills/reversa-screen-translator
Command: npx skills add https://github.com/stribus/pygerengastos --skill reversa-screen-translator-stribus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy software stores UI flows in non-executable formats. This Skill translates those screens into executable UI specifications usable for automated parity testing and Inspector-ready artifacts.

Core Features & Use Cases

Detects the origin of legacy UI, builds an internal screen inventory, and determines a target platform.
Executes in two phases: a human-in-the-loop modernization decision and automatic generation of per-screen specs.
Produces parity artifacts such as screen_modernization_decision.md, target_screens.md, screen_deviation_log.md, and golden manifests when an oracle is available.

Quick Start

Start by running the Screen Translator on the legacy project to produce a modernization decision and initial target screens.

Frequently Asked Questions about reversa-screen-translator

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

FAQPage Schema

How do I translate legacy UI screens into machine-readable specifications?▼

To translate legacy UI screens into machine-readable specifications, you run a screen translator that detects the origin platform, builds a screen inventory, and generates executable UI specs for parity testing.

What is UI parity testing for legacy software modernization?▼

UI parity testing for legacy software modernization validates that target screens match original legacy interfaces by comparing executable UI specifications against generated target screens and deviation logs to detect functional discrepancies.

Can I automate legacy screen inventory generation across different platforms?▼

Yes, the screen translator automates legacy screen inventory generation by detecting the origin platform of your legacy UI and building an internal inventory to prepare for target platform determination and spec generation.

How do I generate deviation logs for legacy UI modernization?▼

You generate deviation logs for legacy UI modernization by executing the two-phase translation process, which outputs parity artifacts including screen_deviation_log.md to track variations between legacy screens and target specifications.

Do I need a human-in-the-loop review for legacy UI specification translation?▼

Yes, the legacy UI specification translation process requires a human-in-the-loop review during its first phase to make modernization decisions before automatically generating per-screen executable specifications in the second phase.

What artifacts are produced when converting legacy screens to executable specs?▼

Converting legacy screens to executable specs produces artifacts including screen_modernization_decision.md, target_screens.md, screen_deviation_log.md, and golden manifests when an oracle is available for Inspector-ready validation.