reversa-screen-translator

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

Updated May 11, 2026
One-click install
npx skills add https://github.com/Marcu-Loreto/Skill_v1 --skill reversa-screen-translator-marcu-loreto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-screen-translator
Source: https://github.com/Marcu-Loreto/Skill_v1/tree/main/.agents/skills/reversa-screen-translator
Command: npx skills add https://github.com/Marcu-Loreto/Skill_v1 --skill reversa-screen-translator-marcu-loreto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill transforms legacy system screens into executable specifications, bridging the gap between design-system catalogs and ready-to-code implementations. It operates in two phases, ensuring human decision-making and generating necessary artifacts for further development.

Core Features & Use Cases

  • Screen Detection and Decision: Automatically detects screen types and allows human input to choose translation modes.
  • Spec Generation: Generates target_screens.md, screen_deviation_log.md, and golden files for parity testing.
  • Use Case: When transitioning a legacy system to a modern UI, use this Skill to convert system screens into executable specifications for developers to work with.

Quick Start

Activate the skill with the command: /reversa-screen-translator

Frequently Asked Questions about reversa-screen-translator

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

FAQPage Schema
How do I convert legacy system screens into executable specifications?

To convert legacy system screens into executable specifications, activate this Skill to automatically detect screen types and generate spec files like target_screens.md for developers to implement.

What is screen translation for legacy system migration?

Screen translation for legacy system migration is the process of transforming old UI screens into ready-to-code executable specifications, bridging the gap between design-system catalogs and modern implementation.

How do I generate golden files for parity testing during system migration?

Generate golden files for parity testing by running the screen translation process, which produces these artifacts alongside screen_deviation_log.md to verify UI consistency during system migration.

Can I manually choose translation modes for different legacy screen types?

Yes, you can manually choose translation modes for different legacy screen types because the Skill uses platform detection heuristics to identify screens and then allows human input for decision-making.

What artifacts do I need to bridge design-system catalogs and ready-to-code implementations?

To bridge design-system catalogs and ready-to-code implementations, you need generated artifacts including target_screens.md specifications, screen_deviation_log.md, and golden files for parity tests.

Does the screen translation process support automatic platform detection?

Yes, the screen translation process supports automatic platform detection by using built-in heuristics to identify legacy system screen types before generating the executable specification files.