reversa-screen-translator

Translate legacy system screens into executable specifications using heuristic methods.

Updated May 8, 2025
One-click install
npx skills add https://github.com/ggazzo/brewpilot --skill reversa-screen-translator-ggazzo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-screen-translator
Source: https://github.com/ggazzo/brewpilot/tree/main/.agents/skills/reversa-screen-translator
Command: npx skills add https://github.com/ggazzo/brewpilot --skill reversa-screen-translator-ggazzo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires _reversa_sdd, _reversa_sdd/ui, _reversa_sdd/migration, _reversa_sdd/screens, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the translation of legacy system screens into executable specifications, bridging the gap between design-system catalogues and ready-to-code implementations.

Core Features & Use Cases

  • Screen Detection and Translation: Automatically detect screen platforms, choose translation modes (literal, modernized, hybrid), and produce decision artifacts.
  • Mode Selection: Human decision-making involved for translation modes to ensure the best approach is taken.
  • Specification Generation: Generate target specifications for screens and deviation logs based on chosen modes.

Quick Start

/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 translate legacy system screens into executable specifications?

Legacy screen translation into executable specifications uses heuristic processing to detect GUI elements and generate target specifications. It supports legacy system migration by producing ready-to-code implementations from existing interfaces.

What is the best way to automate screen detection for legacy system migration?

Legacy system migration automation uses heuristic screen detection to identify platforms and select translation modes including literal, modernized, or hybrid. It processes input/output specifications to generate decision artifacts and target specifications.

Can I choose different translation modes for legacy screen conversion?

Legacy screen conversion supports literal, modernized, and hybrid translation modes. Human decision-making guides mode selection to ensure target specifications and deviation logs match the chosen migration approach.

Do I need specific input/output specification handling for GUI screen translation?

GUI screen translation requires input/output specification handling. Heuristic processing applies to systems with GUI elements, leveraging references and scripts directories to translate legacy screens into executable specifications.

How does heuristic processing work for generating executable specifications from legacy screens?

Heuristic processing generates executable specifications by detecting legacy screen platforms and translating GUI elements using references and scripts. It outputs decision artifacts and target specifications for migration.

What limitations exist when translating legacy system screens with heuristic methods?

Legacy screen translation using heuristic methods is limited to systems with GUI elements and requires input/output specification handling. Mode selection involves human decision-making, and processing depends on references and scripts directories.