Verified:GitHub

reversa-screen-translator

Convert legacy UI screens into executable target specifications with human-approved modes.

Updated May 5, 2026

Search Tags:#ui specification #golden files #deviation tracking #parity testing #design-system tokens #screen migration #legacy UI translation

Ready to run

npx skills add https://github.com/AlexandrePontesjr/calculadora-Juridica --skill reversa-screen-translator-alexandrepontesjr

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It translates legacy UI screens into executable, code-ready specifications while preventing developers from guessing layout, hierarchy, messages, or styling details.

Core Features & Use Cases

Human-gated translation modes: forces an explicit choice of literal, modernized, or hybrid before generating target specs.
Executable screen specs with design-system fidelity: preserves legacy text by default and maps visual properties to design-system tokens (creating derived tokens when needed).
Parity support via golden files (when an oracle exists): emits golden capture artifacts and a manifest to enable constructive parity testing by the Inspector.

Quick Start

Choose the screen translation mode (literal, modernized, or hybrid) and run the Screen Translator to generate target_screens.md and the required decision/deviation 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 parity testing?▼

To translate legacy UI screens into executable specifications for parity testing, you must first select a human-gated modernization mode (literal, modernized, or hybrid) to deterministically generate target screen specs, decision artifacts, and deviation logs.

What is the best way to map legacy visual properties to design-system tokens during screen migration?▼

Mapping legacy visual properties to design-system tokens during screen migration involves preserving legacy text by default and automatically matching styles to existing tokens, while creating derived tokens whenever an exact match is unavailable.

How does golden-file manifest emission work for multi-platform UI migration workflows?▼

Golden-file manifest emission for multi-platform UI migration workflows works by capturing legacy oracle artifacts into a manifest, enabling constructive parity testing by the Inspector to verify screen inventory and adapter-specific spec formats.

Do I need to choose a translation mode before generating target specs from legacy screens?▼

Yes, you must choose a translation mode before generating target specs from legacy screens. The workflow enforces mandatory mode decision gating, requiring an explicit choice of literal, modernized, or hybrid to prevent developers from guessing layout and styling details.

Why does screen migration require deviation logging and two-phase orchestration?▼

Screen migration requires deviation logging and two-phase orchestration to deterministically track styling and hierarchy mismatches, ensuring that target spec generation remains auditable and aligned with the original legacy screen inventory.

Can I generate adapter-specific spec formats for different platforms from a single legacy screen?▼

Yes, you can generate adapter-specific spec formats for different platforms from a single legacy screen. The translation process deterministically produces platform-specific target_screens.md files based on your chosen modernization mode and token mappings.