rea-new-launcher — Claude Code skill: build a game launcher
The rea-new-launcher Claude Code skill guides work on launchers that help older PC games run on current Windows and Linux. It starts with community-fix research, then examines the game folder and builds the project.
Apache-2.0 ★ 56 updated 2026-11-13
npx skills add akitaonrails/rea-launcher-sdk --skill rea-new-launcher -a claude-codeWhat rea-new-launcher does
The skill walks through launcher development for an older PC game: researching community fixes, inspecting the game folder with REA tools, scaffolding the project, implementing changes, and running headless checks. Its workflow follows rea-launcher-sdk, including docs/STANDARDS.md and docs/playbooks/new-launcher.md.
The game folder and files outside the new repository stay read-only. Tests and game runs avoid opening desktop windows. Register REA MCP tools with npx rea-agents setup. Run sdk/scripts/launcher-check before each commit and release; public releases and DRM changes require the owner's approval.
What it helps with
- scaffold a launcher for an older PC game
- research community fixes before implementing a fix
- test a game launch without opening desktop windows
- prepare an older game for modern Windows and Linux
Example prompts for the agent
- Create a launcher for this older PC game.
- Inspect the game folder and start a
rea-project for current Windows and Linux. - Research community fixes and scaffold a compatibility package for this game.
How to install rea-new-launcher
1Skills CLI (Vercel)
npx skills add akitaonrails/rea-launcher-sdk --skill rea-new-launcher -a claude-code2Manually: put the files in place
~/.claude/skills/rea-new-launcher/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/rea-new-launcher/
1Skills CLI (Vercel)
npx skills add akitaonrails/rea-launcher-sdk --skill rea-new-launcher -a codex2Manually: put the files in place
.agents/skills/rea-new-launcher/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add akitaonrails/rea-launcher-sdk --skill rea-new-launcher -a cursor2Manually: put the files in place
.cursor/skills/rea-new-launcher/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install akitaonrails/rea-launcher-sdk .claude/skills/rea-new-launcher2Manually: put the files in place
.github/skills/rea-new-launcher/SKILL.md1Skills CLI (Vercel)
npx skills add akitaonrails/rea-launcher-sdk --skill rea-new-launcher -a gemini-cli2Platform CLI
gemini skills install https://github.com/akitaonrails/rea-launcher-sdk --path .claude/skills/rea-new-launcherManually: put the files in place
.devin/skills/rea-new-launcher/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about rea-new-launcher
How do I install rea-new-launcher in Claude Code?
Run npx skills add akitaonrails/rea-launcher-sdk --skill rea-new-launcher -a claude-code. The skill file is placed at ~/.claude/skills/rea-new-launcher/SKILL.md.
What does rea-new-launcher do?
It guides research into fixes for an older PC game, REA-based inspection of its folder, launcher development, and headless checks.
What does rea-new-launcher need to work?
It uses rea-launcher-sdk and its docs/STANDARDS.md and docs/playbooks/new-launcher.md files. Set up the REA MCP tools with npx rea-agents setup.
Source text
SKILL.md · Apache-2.0
--- name: rea-new-launcher description: Build a new rea launcher that makes an old PC game plug-and-play on modern Windows and Linux with rea-launcher-sdk — community-fix research first, REA reverse engineering of the game folder, scaffold, implement, headless verification, release. Use when asked to create, start, or scaffold a launcher, compatibility package, or "rea-<game>" project for a game, or to make an abandoned/old PC game run on modern systems. --- # New rea launcher Follow the SDK's playbook exactly; it is the source of truth: 1. Locate the SDK checkout (ask if unknown; default `~/Projects/rea-launcher-sdk` or clone `https://github.com/akitaonrails/rea-launcher-sdk`). 2. Read `<sdk>/docs/STANDARDS.md` (binding) and `<sdk>/docs/playbooks/new-launcher.md`, then work through its phases in order. 3. Make sure the REA MCP tools are available (`npx rea-agents setup` registers them); use them for Phase 2 on the game folder, read in place. Non-negotiable, even if the user doesn't repeat it: - Research existing community fixes online before writing any fix; record them in `docs/RESEARCH.md` and build on them. - Never commit or copy game files; the game folder is read-only. - Everything outside the new repository is the user's and read-only (other repos, prefixes, saves, configs) unless they ask or approve that change; back up first. - Tests, probes and game runs are headless; no windows pop up on the user's desktop. Open one only when a check needs a person or headless would prove nothing, and tell the user first what will open and why. - Settings-window work goes through a design skill; accessibility first; every option and CLI flag gets an end-to-end test; no confusing options. - Push, tag, or post anything public only with the user's go-ahead. - Run `sdk/scripts/launcher-check` before every commit and before a release. Its errors are blocking: fix them (`--explain RULE` says how). Never edit `.rea-check-waivers`, turn off `conformance` or reword a file just to silence a rule; a waiver is the owner's decision, with its reason. - Every fix of our own gets its draft in `docs/CONTRIBUTIONS.md` in the commit that ships it. - A build with DRM or a disc check removed (pre-activated, no-CD) is supported only after the owner decides; ask, then follow STANDARDS "DRM exceptions".
© akitaonrails · Apache-2.0 · akitaonrails/rea-launcher-sdk