Game preservation #
Many older games no longer run on current computers. Some are still on sale but have not been updated in years. This method works from the copy you bought, and records how the game works as it goes.
Understand a game from the copy you own, and rebuild it exactly. Its playbook of skills and agents runs inside your coding agent. Its toolkit of tested tools, around Ghidra, Unicorn and REA, checks every result against the original.
Copy this prompt into your coding agent (Claude Code, Codex, Cursor or another). It sets up GameFrame and starts a project for your game. It asks before it installs anything.
Set up GameFrame on this computer for me.
1. Clone https://github.com/tanepiper/game-frame into ~/code/game-frame
(or update it with git pull if it is already there).
2. Read AGENTS.md and .claude/skills/re-setup/SKILL.md.
3. Run scripts/setup.sh and show me the table of what is present and what is missing.
4. Before you install anything, tell me what scripts/setup.sh --install will install and how
large each part is. Wait for my answer, then run it.
5. Run tests/run.sh --ghidra and report how many checks passed. If any failed, show the
failures and fix the setup before going on.
6. Run scripts/setup.sh --rea and help me register REA with this agent.
7. Ask me for the name of the game and the folder of my own copy of it. Then run
scripts/new-project.sh ~/re/<short-name> "<Game Name>" "<path to the game>".
8. Open the new project, read its AGENTS.md, and start with the re-start skill.
Never copy the game's files, extracted assets or decompiled code into a git repository.
Last updated:
Each step has a skill. The steps run in order. When a check fails, you go back to the trace step.
Agents can also read this site as plain text. llms.txt lists every page with a short description, and llms-full.txt holds all of them in one file. Each page has a Markdown copy at the same address with .md at the end, such as /games/interaction.md.