skills.rest
silaslopes100
silaslopes100COMMUNITY
Explore all skills by this author →
WebsiteGitHub

reversa-screen-translator

Translate legacy COBOL, Delphi, and Win32 screens into executable specifications.

Updated May 19, 2026
Search Tags:#ui#specification#migration#modernization#legacy#reversa
One-click install
npx skills add https://github.com/silaslopes100/lojacarmenedaniel --skill reversa-screen-translator-silaslopes100
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-screen-translator
Source: https://github.com/silaslopes100/lojacarmenedaniel/tree/main/.agents/skills/reversa-screen-translator
Command: npx skills add https://github.com/silaslopes100/lojacarmenedaniel --skill reversa-screen-translator-silaslopes100

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill bridges the gap between legacy system interfaces and modern development by translating visual screens into precise, executable specifications, eliminating guesswork for developers.

Core Features & Use Cases

  • Multi-Mode Translation: Supports literal, modernized, and hybrid translation modes to balance fidelity and modernization needs.
  • Design System Integration: Maps legacy UI elements to modern design tokens, ensuring consistency.
  • Use Case: When migrating a legacy Delphi or COBOL application to a modern web stack, use this Skill to generate component trees and state definitions that guide the frontend implementation.

Quick Start

Activate the reversa-screen-translator skill to begin the phase one detection and modernization decision process for the current legacy project.

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 COBOL or Delphi screens into executable specifications?▼

To translate legacy screens into executable specifications, activate this Skill to detect interface elements and generate structured component trees, state definitions, and golden files for modern web or mobile frameworks.

What is the best way to map legacy UI elements to a modern design system during migration?▼

Mapping legacy UI elements to a modern design system is handled through design token mapping, which translates old interface components into consistent, modernized design tokens for your new architecture.

Can I maintain feature parity when migrating Win32 applications to a modern web stack?▼

Yes, you can maintain parity when migrating Win32 applications by using structured deviation logging, which tracks and records any functional differences between the original legacy screens and the translated executable specifications.

Does this tool support both literal and modernized translation modes for legacy system migration?▼

Yes, it supports literal, modernized, and hybrid translation modes, allowing you to balance exact functional fidelity with modern UI requirements during your legacy system migration process.

What are the limitations of automated screen translation for legacy codebases?▼

Automated screen translation focuses on visual interfaces and executable specs rather than backend logic, meaning you must separately handle underlying business rules and database migration for COBOL or Delphi systems.

Related Skills

Explore More Software Engineering Skills→
89jobrien89jobrien
4

spec-driven-development

Translate structured specifications into executable artifacts through a seven-phase workflow.

Community
Advanced
PeterHddPeterHdd
27

cleanui

Improve AI-generated user interfaces with design best practices and layout intelligence.

Community
Advanced
afsjrafsjr

reversa-screen-translator

Translate legacy UI screens into token-driven migration specifications with human-approved modes.

Community
Advanced
PiercingXXPiercingXX
1

refined

Generate Refined design-system component rules with tokens, accessibility criteria, and QA checklists.

Community
Intermediate