skills.rest
RLuf
RLufCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

reversa-screen-translator

Translates legacy system screens into executable specifications for target platforms.

Updated Jun 26, 2026
Search Tags:#design tokens#specification generation#cobol#legacy migration#parity testing#screen translation#ui modernization
One-click install
npx skills add https://github.com/RLuf/fzagent --skill reversa-screen-translator-rluf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-screen-translator
Source: https://github.com/RLuf/fzagent/tree/main/.agents/skills/reversa-screen-translator
Command: npx skills add https://github.com/RLuf/fzagent --skill reversa-screen-translator-rluf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Legacy system migrations leave screen translation without an owner: architects cover structure, testers cover parity, and coders end up improvising layouts, colors, and messages. This Skill closes that gap by converting every legacy screen into an executable specification the coder can implement directly. ## Core Features & Use Cases - Two-phase workflow with mandatory human decision: Phase 1 detects source/target platforms and forces an explicit choice between literal, modernized, or hybrid translation modes; Phase 2 generates target_screens.md, a deviation log, and optional golden files. - Adapter-based spec generation: Supports 28 source-to-target platform pairs (COBOL TUI to Go CLI, Delphi VCL to web SPA, Android XML to Flutter, and more) with canonical spec formats like ansi-byte-stream, component-tree, route-component, and composable. - Deviation tracking and golden files: Every divergence between legacy and generated spec is logged with approval status, and deterministic golden file manifests feed downstream parity testing. - Use Case: Migrating a COBOL banking terminal to a Go CLI: the agent inventories all DISPLAY/ACCEPT screens, presents translation mode trade-offs, and after approval emits byte-exact ANSI stream specs with interpolation points and transition maps. ## Quick Start Invoke /reversa-screen-translator after the Designer phase of your migration to detect the legacy UI platform and generate executable screen specifications.

Frequently Asked Questions about reversa-screen-translator

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

FAQPage Schema
How do I migrate legacy COBOL screens to a modern CLI?▼

The agent detects COBOL ANSI TUI screens from DISPLAY/ACCEPT paragraphs, inventories them, and generates ansi-byte-stream specs with literal bytes and ANSI escape sequences. You first approve a translation mode (literal, modernized, or hybrid), then receive target_screens.md ready for a Go or Rust CLI implementation.

What is the difference between literal and modernized screen translation modes?▼

Literal mode preserves byte-a-byte or pixel-equivalent parity with the legacy UI, enabling constructive parity tests against golden files. Modernized mode redesigns screens idiomatically for the target platform with explicit idle, loading, error, and success states, trading visual fidelity for lower technical debt.

Which legacy platforms are supported for screen migration?▼

Version 1 supports 28 source-to-target pairs including COBOL TUI, ncurses C, Delphi VCL, VB6, WinForms, WPF, Win32/MFC, ASP classic, ASP.NET WebForms, JSP, PHP, legacy jQuery HTML, Android XML, and iOS XIB/Storyboard. Unsupported pairs return error EC-01 with a raw prose template fallback.

Can the agent run if the legacy system has no user interface?▼

Yes. When the inventory detects zero screens, such as batch jobs, pure APIs, or daemons, the agent emits a minimal decision file with mode skipped, a note in target_screens.md, and an empty deviation log. The Inspector then skips visual parity checks automatically.

Why does the agent block before generating screen specifications?▼

Phase 2 generation is blocked until a human approves the screen_modernization_decision.md file and the orchestrator state confirms screenModeApproved is true. This prevents silent modernization and mirrors the approval pattern used for paradigm and topology decisions.

How are visual deviations between legacy and new screens tracked?▼

Every divergence is recorded in screen_deviation_log.md with a DEV-NNN identifier, a type (technical, modernization, platform, or correction), and an approval status. Pending deviations block handoff to the Inspector, while approved ones propagate into the parity specs exceptions section.

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
Marcu-LoretoMarcu-Loreto

reversa-screen-translator

Convert legacy system screens into executable specifications with generated spec and golden files.

Community
Advanced
maximoseomaximoseo

reversa-design-system

Extract design tokens and guidelines from CSS variables, theme files, and screenshots.

Community
Intermediate
webn77webn77

화면 흐름도

Generate screen transition flowcharts and user scenarios from feature descriptions.

Community
Intermediate