legacy

Convert legacy Vista plan JSON files into current architecture diagrams and domain requirements.

Updated Feb 17, 2026

Search Tags:#documentation #architecture diagrams #code conversion #legacy code #reverse engineering #vista

Ready to run

npx skills add https://github.com/ribeec20/vista-marketplace --skill legacy-ribeec20

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: legacy
Source: https://github.com/ribeec20/vista-marketplace/tree/main/vista/skills/legacy
Command: npx skills add https://github.com/ribeec20/vista-marketplace --skill legacy-ribeec20

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill bridges the gap between older development practices and the modern Vista planning framework, ensuring your existing codebase is compatible and well-documented within the Vista ecosystem.

Core Features & Use Cases

Reverse-Engineering: Analyze existing codebases to generate Vista planning artifacts like architecture diagrams and domain requirements.
Format Conversion: Transform legacy Vista feature files (e.g., _plan.json) into the current arch/ directory structure with native Mermaid diagrams.
Use Case: You've inherited a project with features built before Vista's current architecture. Use this Skill to automatically generate up-to-date architecture diagrams and documentation from the existing code, making it easier to understand and maintain.

Quick Start

Use the legacy skill to convert the existing feature named 'user-auth' into the current Vista architecture schema.

Frequently Asked Questions about legacy

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

FAQPage Schema

How do I reverse-engineer an existing codebase into architecture diagrams and domain requirements?▼

Reverse-engineering existing codebases into architecture diagrams and domain requirements is done by scanning the code to automatically generate Mermaid diagrams and update Vista feature manifests. This extracts structural data to map out the current architecture.

How do I convert old Vista _plan.json files into the current arch/ directory structure?▼

Converting old Vista _plan.json files into the current arch/ directory structure involves automated extraction from the legacy JSON format. The process transforms old planning data into native Mermaid diagrams and updated feature manifests.

Does Vista support automated extraction from legacy plan JSON formats for code conversion?▼

Vista supports automated extraction from legacy plan JSON formats through this code conversion process. It parses the old JSON structures to generate current Vista planning artifacts and native Mermaid architecture diagrams.

What is the best way to generate Mermaid diagrams from legacy code for Vista planning?▼

Generating Mermaid diagrams from legacy code for Vista planning is best handled by reverse-engineering the codebase. The Skill scans existing code to automatically produce architecture diagrams and update feature manifests.

Do I need an existing codebase to generate Vista planning artifacts and domain requirements?▼

An existing codebase or legacy Vista feature files are required to generate Vista planning artifacts and domain requirements. The tool relies on scanning current code or extracting data from old _plan.json formats to produce architecture diagrams.

When should I not use reverse engineering to update feature manifests?▼

Reverse engineering to update feature manifests is not suitable for projects built natively within the current Vista architecture. It is specifically designed for legacy codebases or older plan JSON formats that require format conversion.