reversa-screen-translator

Convert legacy UI screens into executable specifications for AI coding agents.

1.5k|383|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-screen-translator-sandeco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-screen-translator
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-screen-translator
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-screen-translator-sandeco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It transforms legacy UI screens into operational, executable specifications for coding agents, preventing agents from inventing layout, messages, colors, or hierarchy.

Core Features & Use Cases

  • Two-phase screen translation: forces a human-approved decision of translation mode (literal, modernized, or hybrid) before generating specs.
  • Adapter-based spec generation: produces target specs in the correct canonical format for the chosen legacy→target platform pair (including TUI/CLI and graphical targets).
  • Traceable deviations and optional golden files: records divergence between legacy and generated specs, and can emit golden artifacts for parity tests when an oracle can run.

Quick Start

Use the reversa-screen-translator to translate the legacy project’s screens by first deciding the mode (literal, modernized, or hybrid) and then generating target_screens.md and screen deviation logs for the Inspector.

Frequently Asked Questions about reversa-screen-translator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate executable specs from legacy UI screens for AI coding agents?

Screen translation prevents AI agents from inventing layout, colors, or hierarchy by converting legacy interfaces into operational specs. It enforces design-system token mapping and records deviations to maintain visual fidelity during platform migration.

How do I handle visual deviations when converting legacy screens to target platform specs?

Handling visual deviations requires append-only deviation logging that records divergence between legacy and generated specs. This log can block handoff to coding agents until a human approves the recorded visual or structural changes.

Can I generate golden files for parity testing during UI modernization?

Yes, you can generate golden files for parity testing when an oracle can run. The screen translation process emits these golden artifacts alongside target specs to verify visual and structural fidelity against the legacy platform.

Does the legacy screen translation process support TUI and CLI target platforms?

Yes, legacy screen translation supports TUI, CLI, and graphical targets through adapter-based spec generation. It produces target specs in the correct canonical format for the chosen legacy-to-target platform pair.

What is the best way to ensure design system token mapping when migrating legacy interfaces?

The best way to ensure design system token mapping is using a two-phase screen translation that mandates a human-approved modernization decision. This enforces adapter-driven spec output and traceable deviation logging for controllable parity.