reversa-screen-translator

Translate legacy UI screens into executable specifications for codifier and Inspector.

Updated Nov 4, 2025

Search Tags:#automation #migration #spec-generation #parity-tests #legacy-ui #screen-translator

Ready to run

npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-screen-translator-markson22

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Translate legacy UI screens into executable specifications consumed by coders and the Inspector, preserving layout, copy, and flow.

Core Features & Use Cases

Two-phase migration: detect origin and mode with human approval, then generate target_screens.md, screen_deviation_log.md, and golden artifacts.
Outputs are organized under _reversa_sdd/migration/ and _reversa_sdd/screens/ for parity tests, with an inventory of screens and optional golden captures.
The process is read-only with respect to the legacy sources, using on-demand resources in scripts/references/assets as needed.

Quick Start

Invoke the Screen Translator to begin the two-phase migration: determine origin/target platforms and translation mode, then generate the phase-2 specifications and golden artifacts.

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 executable specifications for migration?▼

This Skill generates executable specifications by running a two-phase migration that detects origin and target platforms, applies a translation mode with human validation, and outputs target screen specs with deviation logs.

What translation modes are available for legacy UI screen modernization?▼

Available translation modes for legacy UI screen modernization include literal, modernized, and hybrid, each selected during phase one with human validation before generating the final target screen specifications.

Can I perform legacy UI migration without modifying the original source system?▼

Yes, the legacy UI migration workflow operates entirely read-only on the original source system, utilizing on-demand resources in the _reversa_sdd directory for design-system tokens and adapter mappings.

What output files are generated when converting legacy screens into specs?▼

Converting legacy screens generates target_screens.md, screen_modernization_decision.md, and screen_deviation_log.md, organized under _reversa_sdd/migration/ and _reversa_sdd/screens/ along with an inventory and optional golden captures.

How do parity tests work with migrated legacy UI specifications?▼

Parity tests utilize the generated target screen specifications and optional golden captures organized under _reversa_sdd/screens/, allowing the codifier and Inspector to verify that the migrated layout, copy, and flow match the original legacy UI.

What is the best way to inventory legacy screens before generating executable specs?▼

The best way to inventory legacy screens is to invoke the two-phase translation workflow, which automatically catalogs screens and optionally captures golden artifacts during the generation of target specifications and deviation logs.