reversa-screen-translator

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.

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.

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.

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.

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.

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.