Verified:GitHub

reversa-screen-translator

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

1|Updated Dec 20, 2025

Search Tags:#spec generation #legacy migration #golden files #ui parity #screen translation #design system tokens #adapter formats

Ready to run

npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-screen-translator-rdinda

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the guesswork gap between a legacy system’s screens and production-ready specifications by forcing an explicit human decision on translation mode.

Core Features & Use Cases

Human-gated modernization mode: presents literal, modernized, and hybrid options and requires approval before generating specs.
Deterministic spec generation: produces target_screens.md with correct adapter formats per source→target platform pair.
Deviation tracking for parity: logs divergences in screen_deviation_log.md and blocks handoff when deviations are pending.
Optional golden files: emits screens/golden/* and screens/golden/manifest.yaml when an executable “oracle” exists for constructive parity tests.
Design-system token alignment: maps colors/spacing/typography to tokens and records derived-token deviations when needed.

Quick Start

Run reversa-screen-translator for the migration pipeline and provide your choice of translation mode (literal, modernized, or hybrid) when prompted.

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

To translate legacy UI screens into executable specs, you run the translation pipeline and explicitly select a migration mode (literal, modernized, or hybrid) to generate the target screen specifications. The process requires human approval before producing the target artifacts.

What is screen translation for legacy migration and when do I need it?▼

Screen translation for legacy migration converts existing UI screens into executable target specifications using adapter-specific formats and design-system tokens. You need it to remove the guesswork gap between a legacy system and production-ready specs during platform modernization.

How do design system tokens map to legacy UI components during spec generation?▼

Design system token alignment maps legacy colors, spacing, and typography directly to tokens during spec generation. When exact matches are not possible, the translation process records derived-token deviations to ensure accurate parity tracking across the target artifacts.

Does UI parity migration block handoff if there are pending screen deviations?▼

Yes, UI parity migration blocks handoff when deviations are pending. The process logs divergences in a screen deviation log and enforces prerequisites to prevent unsafe or unapproved parity handoffs during the legacy system modernization.

Can I generate golden files for constructive parity testing during legacy migration?▼

Yes, you can generate golden files for constructive parity testing during legacy migration. The translation process optionally emits golden files and a manifest when an executable oracle exists, allowing you to validate target screen specs against expected outcomes.