skills.rest
lacsousa
lacsousaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

reversa-screen-translator

Translates legacy system screens into executable target-platform specifications with human-approved modernization modes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Legacy migration projects lack an owner for visual translation: architects cover structure, testers cover parity, and coders end up improvising layouts, colors, and messages. This Skill closes that gap by converting each legacy screen into an executable specification while forcing an explicit human decision on the translation mode (literal, modernized, or hybrid) before any spec is generated. ## Core Features & Use Cases - Two-phase workflow: Phase 1 detects source/target platforms (COBOL TUI, Delphi VCL, VB6, WinForms, ASP, JSP, PHP, Android XML, iOS XIB, and more), inventories screens, and presents literal/modernized/hybrid modes with graded trade-offs for mandatory human approval. Phase 2 generates target_screens.md, a deviation log, and optional golden files. - Adapter-based spec generation: Uses a source-to-target pair table (e.g., cobol-ansi-tui to go-cli, delphi-vcl to web-spa) to emit specs in canonical formats such as ansi-byte-stream, component-tree, route-component, or composable, with design-system tokens instead of hardcoded literals. - Deviation tracking and golden files: Every divergence between legacy and generated spec is logged as an append-only DEV entry that blocks handoff until approved, and golden files with a manifest.yaml enable constructive parity testing when the legacy oracle is executable. - Use Case: Migrating a COBOL banking terminal to a Go CLI: the agent detects the platform, inventories each DISPLAY/ACCEPT screen, gets human approval for literal mode, then emits byte-exact ANSI specs with interpolation points and a golden-file capture manifest. ## Quick Start Ask the agent to run the screen translator on the legacy repository so it detects the source platform, inventories the screens, and presents the literal, modernized, and hybrid translation modes for your decision.

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 or Delphi screens to a modern web or CLI application?▼

Run the screen translator after the migration designer phase. It detects the source platform from code signatures, inventories each screen, asks you to choose a literal, modernized, or hybrid mode, then generates executable specs in target_screens.md for the coder to implement.

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

Literal mode preserves byte-a-byte or pixel-equivalent parity with the legacy UI. Modernized mode redesigns screens idiomatically for the target platform with explicit idle, loading, error, and success states. Hybrid mode applies literal to some screens and modernized to others, requiring explicit per-screen lists.

Which legacy platforms are supported for screen migration?▼

Supported sources include COBOL ANSI TUI and Screen Section, ncurses C, Delphi VCL and FireMonkey, VB6, WinForms, WPF, Win32/MFC, classic ASP, ASP.NET WebForms, JSP, PHP server-rendered, legacy jQuery HTML, Android XML, and iOS XIB/Storyboard. Unsupported pairs return error EC-01 with a raw prose template fallback.

Can the screen translator run without the full reversa migration pipeline?▼

Yes, in standalone mode it skips the designer prerequisites and asks you directly for the target platform. It still requires or offers to generate the design-system tokens and UI inventory, and it never writes outside the _reversa_sdd/migration, screens, and tokens-derived paths.

What happens when the legacy system has no user interface?▼

For batch, API-only, or daemon systems, the agent emits a minimal decision file with mode set to skipped, a target_screens.md note stating no screens were detected, and an empty deviation log. The Inspector then skips visual parity checks automatically.

Why does the screen translator block handoff to the Inspector?▼

Handoff is blocked when deviation entries in screen_deviation_log.md are still pending approval, or when Phase 2 is attempted before the human approves the modernization decision. Approved deviations propagate to the Inspector's parity specs as documented exceptions.

Related Skills

Explore More Software Engineering Skills→
stribusstribus
1

reversa-screen-translator

Translate legacy screens into executable UI specifications for parity testing.

Community
Advanced
RdindaRdinda
1

reversa-screen-translator

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

Community
Advanced
ThorStarlordThorStarlord
1

ui-system

Define literal and semantic design tokens for colors, spacing, and typography.

Community
Advanced
adminsairolotech-bitadminsairolotech-bit

recreate-screenshot

Recreate UI screens from screenshots with pixel-perfect layout and CSS fidelity.

Community
Advanced