Skip to main content
skill CX Codex

console-anywhere — Claude Code skill for PS2Recomp ports

console-anywhere is a Claude Code skill that prepares a PS2Recomp build for a target device and packages it for players. It runs on requests to build for Steam Deck, Android, Mac, or another supported target.

MIT ★ 449 updated 2026-10-22

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add Jakeschincariol/console-skill
/plugin install console-skill@console-skill
Open on GitHub

What console-anywhere does

The skill checks which tools are available for the chosen target and prints installation commands for missing ones. It then lays out build steps from PS2Recomp instructions and packages the runner with its libraries, an empty game/ directory, PLAYERS.md, and a launch script.

Before packaging, it scans the folder and refuses to continue if it finds a disc image, PS2 ELF, IRX module, or other game data. Each player supplies a dump from their own disc. The Android build has no on-screen controls yet; Mac, Linux, Android, and Vita builds receive less testing than the Windows path.

What it helps with

  • check build tools for a selected device
  • derive port build steps from PS2Recomp instructions
  • assemble a player folder with the runner and launch files
  • reject a package folder containing game data

Example prompts for the agent

  • Prepare the port build for Steam Deck and list the required steps.
  • Build an Android APK from the existing port.
  • Check console/dist/mygame-linux before it is archived.

How to install console-anywhere

1Plugin marketplace

/plugin marketplace add Jakeschincariol/console-skill
/plugin install console-skill@console-skill

This installs the whole console-skill plugin with all its skills

2Skills CLI (Vercel)

npx skills add Jakeschincariol/console-skill --skill console-anywhere -a claude-code

3Manually: put the files in place

~/.claude/skills/console-anywhere/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/console-anywhere/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about console-anywhere

How do I install console-anywhere in Claude Code?

Run /plugin marketplace add Jakeschincariol/console-skill, then run /plugin install console-skill@console-skill.

What does console-anywhere do?

It checks tools for a target, lays out the build steps, and packages the runner for players. Before packaging, it rejects folders containing disc images or other game data.

Does console-anywhere provide on-screen controls for Android?

No. The Android build does not currently include on-screen controls.

Source text

SKILL.md · MIT
---
name: console-anywhere
description: >-
  Play Anywhere. Builds the port for Windows, Mac, Linux, Steam Deck, Android and PS Vita and
  packages it without any game files inside. doctor checks this machine's tools for a target and
  prints the exact install command for anything missing; plan prints the build steps taken from
  PS2Recomp's own README, android/README.md and vita scripts; package makes a player folder in
  console/dist/ (the runner, its libraries, an empty game/ folder, PLAYERS.md, a launch script,
  .recomp.json) and refuses outright if a disc image, PS2 ELF, IRX module, recompiled runner source
  or other game data is inside; guard runs that check on any folder; recomp-json writes the
  project's optional .recomp.json. Use when the user says "put it on my Steam Deck", "build it for
  Android", "play it on my phone", "on my TV", "Vita build", "Mac build", "package it", "make a
  release folder", "is it safe to zip this", or after the port plays on the machine it was built on.
argument-hint: "doctor|plan|package|guard|recomp-json --target windows|macos|linux|steamdeck|android|vita|web"
---

# console-anywhere

A PS2Recomp port is a normal native program (`ps2EntryRunner`) built from the recompiled game code
plus the runtime, drawn with raylib. The same CMake project builds it on Windows, macOS (Apple
silicon through sse2neon), Linux and the Steam Deck; `android/` makes an APK and `vita/` makes a
vpk. This skill checks the toolchain, prints the right steps for each device, and packages the
result so the player brings the game from their own disc.

Honest limits: PS2Recomp says it is tested mainly with MSVC, so Mac, Linux, Android and Vita builds
get less testing; the Vita is far slower than a PC; Android has no on-screen controls yet. And the
runner is compiled from your game's recompiled code, so a package is for your own devices: it
never contains the disc, but it is still derived from the game, so it is not something to upload.

`${CLAUDE_SKILL_DIR}` below is this skill's folder (where this SKILL.md lives).

```bash
python3 "${CLAUDE_SKILL_DIR}/targets.py" doctor                       # this machine's own OS
python3 "${CLAUDE_SKILL_DIR}/targets.py" doctor --target android --target vita   # or --target all
python3 "${CLAUDE_SKILL_DIR}/targets.py" plan --target steamdeck --elf-name SLUS_203.12
python3 "${CLAUDE_SKILL_DIR}/targets.py" package --runner out/release/ps2xRuntime/ps2EntryRunner \
        --target linux --elf-name SLUS_203.12 --game "My Game" --serial SLUS-20312 \
        --out console/dist/mygame-linux
python3 "${CLAUDE_SKILL_DIR}/targets.py" guard console/dist/mygame-linux   # before you zip or push anything
python3 "${CLAUDE_SKILL_DIR}/targets.py" recomp-json --game "My Game" --serial SLUS-20312 --status playable
```

Targets: `windows`, `macos`, `linux`, `steamdeck`, `android`, `vita`, and `web` (plan and doctor
only: a separate toolchain). `plan` takes `--repo` (your PS2Recomp checkout) and `--build-dir`.
`package` takes `--lib FILE` (extra libraries), `--allow FILE`, `--replace`, `--status`, `--json`.
Exit codes: 0 ok, 1 something missing or refused, 2 bad input.

## What it reads and writes

| file | what |
| --- | --- |
| your build output | `ps2EntryRunner` (+ `.dll` / `.so` / `.dylib` next to it), `app-release.apk`, or `ps2EntryRunner.vpk` |
| `console/dist/<name>/` | the player folder: runner, libraries, `game/` (empty), `PLAYERS.md`, `play.bat` / `play.command` / `play.sh` / `install-android.sh`, `.recomp.json`, `.console-dist.json` |
| `templates/PLAYERS.md` | the player instructions template |
| `.recomp.json` | optional project description read by recomp lists (PS2Recomp itself ignores it) |
| `console/STATE.md` | read the build folder and checkout path from it; log what was built |

## Method

1. **Ask where they want to play** and on what: a PC, a Mac, a Steam Deck, an Android phone,
   tablet or TV box, a homebrew Vita. "On the TV" means an Android TV box with a Bluetooth pad, or a
   PC or Deck plugged into the TV with a controller.
2. **The port must already run here.** Build it and check it with `/console-tester` on the machine
   you develop on first. A crash on the desktop will not get better on a phone.
3. **Doctor.** `targets.py doctor --target <t>`. Install what is MISSING with the printed command,
   then run doctor again.
4. **Plan.** `targets.py plan --target <t> --elf-name <the disc's ELF>`. Follow the steps in the
   user's checkout (the one holding their recompiled code). Per-target details and the source of
   each fact: [reference/targets.md](reference/targets.md).
5. **Build** with the plan's commands. Incremental only; never clean a build folder, never
   `CLEAN=1` for the Vita. A separate release folder (`out/release`) keeps the day-to-day build intact.
6. **Package.** `targets.py package --runner <built file> --target <t> --out console/dist/<name>`.
   Add `--elf-name` (else the launch script reads `BOOT2` from the player's `SYSTEM.CNF`) and
   `--game`/`--serial` for `.recomp.json`.
7. **Read the guard's verdict.** A refusal lists each file and why. Fix the cause (wrong `--lib`,
   a disc file next to the runner). Never add an allow line for a disc image, a PS2 ELF, an IRX,
   `SYSTEM.CNF` or runner sources: the allow file is only for a false positive that is truly the
   user's own file, with the reason written next to it. Details: [reference/guard.md](reference/guard.md).
8. **Install on the device** following `PLAYERS.md`, then the player dumps their own disc into
   `game/`. Test it there, and log the result in `console/STATE.md`.

## Per target in one line

| target | runner | how the ELF is found | notes |
| --- | --- | --- | --- |
| Windows | `ps2EntryRunner.exe` + FFmpeg DLLs | `play.bat` passes `game\<ELF>` | MSVC, the most tested path |
| macOS | `ps2EntryRunner` | `play.command` passes `game/<ELF>` | arm64 builds through sse2neon; needs Homebrew FFmpeg unless built without it |
| Linux | `ps2EntryRunner` | `play.sh` | raylib needs X11 and GL headers to build |
| Steam Deck | the Linux build | `play.sh`, added to Steam as a non-Steam game | or the Windows build under Proton (untested here) |
| Android | `app-release.apk` | baked in with `-Pps2xBootElf=...` | files go to `/storage/emulated/0/Android/data/com.ps2x.runner/files/` with `adb push`; pair a controller |
| PS Vita | `ps2EntryRunner.vpk` | baked in by `./vita/build.sh <ux0:data/... path>` | `./vita/setup.sh` once; install with VitaShell; slow |
| web | (not a PS2Recomp target) | | `snuri00/ps2-web-recomp` is a different recompiler: a second port of the same disc, experimental |

## Guard rails

- **Bring your own game.** Every player supplies the game from a disc they own, dumped themselves.
  Never download ISOs, ELFs or BIOS files, never help find them, never ask for them. No BIOS needed.
- **Nothing from the game gets published.** `package` refuses disc images (ISO, BIN, IMG, MDF, NRG,
  CHD, CSO and ISO 9660 content under any name), PS2 ELFs and IRX modules (by magic and machine),
  disc-style names like `SLUS_203.12`, `SYSTEM.CNF`, recompiled `runner/` sources, anything in
  `game/`, and any file over 512 MB. The runner itself is built from the recompiled game code: the
  package is for the user's own devices, not for upload. Share patches, overrides and original assets.
- **Not affiliated with Sony.** PlayStation is a trademark of Sony Interactive Entertainment. PS
  Vita homebrew, Steam, Android and the other platforms belong to their owners.
- **Never destroy the user's files.** `--replace` only replaces a folder this tool made, and refuses
  while `game/` holds anything (the player's disc, saves in `mc0/`).

## Hands off to

- `/console-tester` to run the build on this machine before packaging, and after.
- `/console-controller` for the device's controls (`xbox` layout on the Steam Deck, touch zones or
  a Bluetooth pad on Android).
- `/console-saves` to move saves between devices (`mc0/` sits next to the game's ELF).

© Jake Schincariol · MIT · Jakeschincariol/console-skill

Similar skills

All skills for Game dev and 3D: Unity, Unreal, Godot, Blender →

From the same set12

The whole set →
console-skill console-skill is a Claude Code plugin with eleven skills for porting PlayStation 2 games you own to native PC builds with PS2Recomp. It covers code analysis, game changes, packaging, and testing. ★ 449repo stars console-saves console-saves is a Claude Code skill that imports PS2 memory card saves into game ports and backs them up. It activates when you ask to migrate PCSX2 saves or sync progress across devices. CX Codex +1 ★ 449repo stars console-physics console-physics is a Claude Code skill that finds game-physics values in an ELF and prints PCSX2 and PS2Recomp patches. It responds to requests about speed, gravity, jumps, grip, camera width, and frame rate. CX Codex +1 ★ 449repo stars console-levels console-levels is a Claude Code skill that maps an extracted PS2 disc, unpacks the archives holding levels and repacks them after edits. It fires on requests like "unpack this archive". CX Codex +1 ★ 449repo stars console-sound Console-sound is a Claude Code skill that rips game audio and injects custom tracks back into the files. It decodes PS2 VAG and SPU2 ADPCM formats into WAV for easy editing. CX Codex +1 ★ 449repo stars console-controller console-controller is a Claude Code skill that maps gamepads, keyboard, and touch input into PS2Recomp. It handles remapping, sticks, triggers, and two players. CX Codex +1 ★ 449repo stars console-tester console-tester is a Claude Code skill that automates playtesting for PS2 game ports. It executes ELFs via ps2EntryRunner, categorizes crashes, maps PCs to Ghidra symbols, and diffs PCSX2 dumps. CX Codex +1 ★ 449repo stars console-backend console-backend is a Claude Code skill that ranks missing PS2Recomp backend pieces from runtime logs. It activates after a stop or a request about syscalls, the IOP, or stubs. CX Codex +1 ★ 449repo stars

Project sponsors

Companies that keep this analytics open