reversa-screen-translator

To translate legacy UI screens into executable specs, run the agent to initiate Phase 1, review the detected platform options, and approve the modernization decision to start Phase 2 generation. It produces markdown artifacts and golden manifests for safe handoffs.

Parity testing for legacy UI migration validates that modernized screens match the original interface behavior. This Skill generates executable specifications and deviation logs to automate this verification, bridging design-system catalogs with production-ready code.

Generating target screen definitions from a design-system catalog requires selecting appropriate adapters after the Skill detects your platforms. It then produces target_screens.md files after you approve human-in-the-loop modernization decisions.

Yes, you can use this for multi-tenant legacy UI migrations requiring human-in-the-loop decisions. It detects source and target platforms, prompts for human approvals before generation, and coordinates with designers and inspectors to ensure traceability.

Migrating legacy screens to testable specs produces screen_modernization_decision.md, target_screens.md, screen_deviation_log.md, and optional golden manifests when a legacy oracle is available, ensuring safe handoffs in multi-stage migrations.

You should not use automated spec generation for legacy UI modernization when a legacy oracle is unavailable for golden manifests, or when your project bypasses two-phase workflows and human-in-the-loop decisions for multi-tenant migrations.