legacy-lookup

Search Gamebryo 2.3 source code for legacy classes and functions.

10|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/matiaszanolli/ByroRedux --skill legacy-lookup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legacy-lookup
Source: https://github.com/matiaszanolli/ByroRedux/tree/main/.claude/commands/legacy-lookup
Command: npx skills add https://github.com/matiaszanolli/ByroRedux --skill legacy-lookup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of locating and understanding legacy Gamebryo engine classes, functions, and patterns when rebuilding or translating older engine architectures.

Core Features & Use Cases

  • Legacy Source Search: Finds relevant Gamebryo 2.3 headers, implementations, and declarations for requested classes or functions.
  • Architecture Mapping: Compares legacy APIs with Redux components and documentation to identify existing equivalents or missing pieces.
  • Use Case: When recreating a Gamebryo subsystem, use this Skill to inspect a legacy class hierarchy and determine how it should map into the modern Rust engine design.

Quick Start

Ask the legacy-lookup skill to find the NiTriShape class and explain how it maps to the Redux engine.

Frequently Asked Questions about legacy-lookup

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

FAQPage Schema
How do I map Gamebryo 2.3 legacy classes to a modern Rust engine architecture?

Legacy API investigation in Gamebryo involves searching the 2.3 source tree for specific classes and functions, then comparing their declarations and implementations against Redux code references to determine equivalent components for engine reconstruction.

How do I find legacy Gamebryo engine functions when rebuilding a subsystem?

Finding legacy Gamebryo engine functions requires searching the 2.3 source tree headers and implementations for requested patterns, then applying architecture mapping to translate the discovered class hierarchies into the new engine design.

Do I need the Gamebryo source tree to investigate legacy API mappings?

Yes, legacy API investigation requires access to the Gamebryo 2.3 source tree and Redux code references. Without these, comparing legacy declarations and identifying modern equivalent components for architecture translation is not possible.

What is the best way to analyze a Gamebryo class hierarchy for engine reconstruction?

Analyzing a Gamebryo class hierarchy for engine reconstruction involves searching legacy source code for class definitions and comparing them against Redux documentation to identify missing pieces and map equivalents into the modern Rust engine design.

Can I use this approach to find equivalent components in the Redux engine?

Yes, architecture mapping compares legacy Gamebryo APIs with Redux components and documentation to identify existing equivalents. This determines how legacy classes should map into the modern Rust engine design.