skills.rest
maximoseo
maximoseoCOMMUNITY
Explore all skills by this author →
GitHub

reversa-screen-translator

Translate legacy UI screens into executable specifications with human approval.

Updated Aug 23, 2026
Search Tags:#specification#design-system#golden-files#deviations#parity-tests#legacy-ui#screen-translator
One-click install
npx skills add https://github.com/maximoseo/github-repos-radar --skill reversa-screen-translator-maximoseo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-screen-translator
Source: https://github.com/maximoseo/github-repos-radar/tree/main/.agents/skills/reversa-screen-translator
Command: npx skills add https://github.com/maximoseo/github-repos-radar --skill reversa-screen-translator-maximoseo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Traduzir telas legadas em especificações executáveis para permitir paridade com o design-system moderno e automatizar a geração de artefatos (target_screens, screen_modernization_decision, deviations e golden files), fechando a lacuna entre o catálogo de design e o código pronto.

Core Features & Use Cases

  • Detecta plataforma origem e alvo e sugere modos de tradução (literal, modernizado, híbrido) com decisão humana.
  • Gera artefatos da Fase 2 (target_screens.md, screen_deviation_log.md, inventory e golden files quando possível).
  • Mantém log de deviations e facilita parity tests para o Inspector.

Quick Start

Inicie o Screen Translator em um projeto legado com UI, siga as instruções da Fase 1 para decidir o modo de tradução e aguarde a aprovação humana antes de gerar as telas-alvo e logs.

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?▼

Translating legacy UI screens into executable specifications requires mapping each screen to a target platform and spec format using a two-phase workflow. This process generates target screens, logs deviations, and creates golden files for parity testing.

What is the best way to generate specs for legacy COBOL or VB6 interfaces?▼

Generating specs for legacy COBOL, VB6, Delphi, Android, iOS, or web frontends involves deciding between literal, modernized, or hybrid translation modes during Phase 1. Human approval is then required before proceeding to final spec generation in Phase 2.

How do I ensure design-system parity when modernizing legacy screens?▼

To ensure design-system parity when modernizing legacy screens, the translation process references design-system tokens and maintains a deviation log. This approach tracks variations and facilitates parity tests against the modern UI catalog.

Does the executable spec generation process require human approval?▼

Yes, the executable spec generation process explicitly requires human approval. After Phase 1 determines the translation mode, a human must approve the decision before Phase 2 begins generating the final target screens and deviation logs.

What artifacts are produced when converting legacy UI to an executable spec?▼

Converting legacy UI to an executable spec produces target_screens.md, screen_deviation_log.md, inventory files, and golden files. These artifacts document the modernized interfaces and enable automated parity testing against the design system.

Related Skills

Explore More Software Engineering Skills→
RdindaRdinda
1

reversa-screen-translator

Convert legacy UI screens into target screen specifications with a required translation mode selection.

Community
Advanced
stribusstribus
1

reversa-screen-translator

Translate legacy screens into executable UI specifications for parity testing.

Community
Advanced
afsjrafsjr

reversa-screen-translator

Translate legacy UI screens into token-driven migration specifications with human-approved modes.

Community
Advanced
ricardops34ricardops34

reversa-screen-translator

Translate legacy UI screens into executable target specifications with adapter-formatted contracts.

Community
Advanced