skills.rest
cliffthelin
cliffthelinCOMMUNITY
Explore all skills by this author →
GitHub

reversa-screen-translator

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

Updated May 13, 2026
Search Tags:#spec generation#golden files#parity testing#screen translation#design-system tokens#legacy UI migration#human decision gating
One-click install
npx skills add https://github.com/cliffthelin/AXiomEngine --skill reversa-screen-translator-cliffthelin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-screen-translator
Source: https://github.com/cliffthelin/AXiomEngine/tree/main/skills/reversa/reversa-screen-translator
Command: npx skills add https://github.com/cliffthelin/AXiomEngine --skill reversa-screen-translator-cliffthelin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reversa-screen-translator removes the guesswork between a legacy UI and a build-ready specification by translating each legacy screen into an executable target description that preserves content and forces an explicit translation-mode decision.

Core Features & Use Cases

  • Phase-1 mode decision: Detects source/target platform, enumerates available translation modes (literal, modernized, hybrid), and pauses for human approval to produce screen_modernization_decision.md.
  • Phase-2 spec generation: Generates target_screens.md plus an append-only screen_deviation_log.md, using design-system tokens and adapter-specific spec formats for constructive parity testing.
  • Optional golden outputs: When the legacy oracle is available, emits golden files and a manifest.yaml for the Inspector to run parity checks.
  • Read-only legacy handling: Never modifies legacy sources; writes only into _reversa_sdd/migration/ and _reversa_sdd/screens/.
  • Batch/no-UI safety: Detects projects with zero screens and switches to skipped mode with minimal artifacts and an explicit note for the Inspector.

Quick Start

Run the reversa-screen-translator agent (typically via /reversa-migrate) and choose the translation mode 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 specifications for migration?▼

Legacy UI screens are translated into executable target specifications by applying a phase-gated workflow that enforces design-system tokens and adapter-specific spec formats. This process generates migration artifacts and optional golden files for constructive parity testing.

What is constructive parity testing and how does it work for UI migrations?▼

Constructive parity testing for UI migrations validates translated target specifications against optional golden files emitted from a legacy oracle. The Inspector runs these parity checks using a manifest to ensure the modernized target matches the legacy screen behavior.

How do I generate golden files for parity testing during a legacy UI migration?▼

Golden files are generated during legacy UI migration when the legacy oracle is available, emitting a manifest.yaml alongside the target specifications. These outputs allow parity checkers to verify that modernized screens preserve the original content and behavior.

Can I migrate legacy terminal TUI applications to web SPA or mobile targets?▼

Terminal TUI applications can be migrated to desktop, web SPA, and mobile or tablet UI targets. The translation process uses adapter-specific spec.kind formats to ensure the generated target specifications match the destination platform's requirements.

Do I need human approval before generating target specifications from legacy screens?▼

Human approval is required before generating target specifications because the workflow enforces a phase-gated translation mode decision. The system pauses to let you choose between literal, modernized, or hybrid modes before producing the final migration artifacts.

What happens to legacy source files during the screen translation process?▼

Legacy source files remain completely unmodified during the screen translation process. The system operates in a read-only manner on legacy sources, writing all migration artifacts and deviation logs only into designated _reversa_sdd directories.

Related Skills

Explore More Software Engineering Skills→
Markson22Markson22

reversa-screen-translator

Translate legacy UI screens into executable specifications for codifier and Inspector.

Community
Advanced
cliffthelincliffthelin

reversa-inspector

Generate paradigm-adapted parity specifications and Gherkin scenarios for Reversa migrations.

Community
Advanced
AlexandrePontesjrAlexandrePontesjr

reversa-screen-translator

Convert legacy UI screens into executable target 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