kuluu-ffxi

Observe and drive the retail FFXI client (HorizonXI) running in the Parallels "Windows 11" VM on this macOS host — capture reference screenshots of retail behavior, send keys/clicks to the game, and compare against the Kuluu remake for feature parity. Use whenever asked to check how retail/the original client does something, capture retail reference footage/screenshots, drive the retail client, or compare remake rendering, HUD, menus, animations, or behavior with the real game.

How beads issues are projected to GitHub Issues and (optionally) imported back. Use when publishing beads to GitHub, debugging why a bead's issue is stale or missing, editing scripts/beads-github-publish.py or scripts/beads-github-sync.sh, or touching .github/workflows/beads-github-publish.yml.

For any change that adds a new entity spawn site, Bevy Resource, or work that fires at a state-transition boundary (logout, zone change, disconnect, OnEnter/OnExit, AppPhase transition, session bridge, cleanup, despawn, drain), verify the symmetric cleanup is registered. Both layers — entity markers AND Resource drains — must be considered. Activates on lifecycle keywords: logout, disconnect, OnExit, OnEnter, AppPhase, spawn, despawn, drain, cleanup, lifecycle, session boundary.

Cut a new Kuluu release and shepherd it to a published, verified GitHub release. Use whenever the user asks to make/cut/ship a release, bump the version, tag a version, publish a build, "get vX.Y.Z out", or asks why a release failed, published under the wrong tag, or is missing assets. Also use when editing .github/workflows/release.yml or auto-release-on-main.yml, or when the in-app updater stops seeing new versions. Covers the version bump, the CI gate, per-platform packaging, publish verification, and the recovery path for a bad release.

Build a release ffxi-client binary for x86_64 Linux and ship it to the paired Steam Deck over Syncthing. Use whenever the user asks to build a release/Deck/Linux binary, "push to the deck", "sync to my steam deck", test on the Deck, or update the build the Deck is running — even if they just say "build and sync" or "get the latest onto the deck". Covers the Apple-Silicon-host-to-x86_64-Linux-target cross build via Rosetta-backed Docker/colima; do not hand-roll a fresh cross-compile setup, the scripts already exist.

For any Rust symbol that crosses the LSB boundary (wire decoder, packet builder, coord transform, session-state transition, shared constant, lifecycle assumption), locate and surface the LSB C++ counterpart in vendor/server/ for side-by-side comparison. Use whenever implementing or modifying anything whose correctness depends on server-side semantics matching.

Build-time auto-extraction of LSB-shipped data into compile-time Rust constants. Apply this pattern whenever a Rust crate needs values that LSB defines in a parseable form (headers, SQL, lua tables) — never hand-maintain those values; let cargo regenerate them whenever vendor data updates.

Runtime-verify Kuluu client changes against the local LSB dev stack — pick the right surface (headless MCP drive, GUI attach, raw stdio, or live integration tests), bring the stack up, drive the change, capture evidence. Use this whenever asked to verify a change works, confirm a bug fix, run/launch/drive the client, screenshot the game, test against the local server, or observe protocol/rendering behavior live — even if the word "verify" isn't used. Also the recipe for just getting a live session up for exploration.

Print a structured report of why the FFXI agent is stuck (or confirm it isn't). Reads scene/party/diagnostics/goal/entities resources and the last-event sidecar, then names what's blocking action — empty entity list, zone=0, KO, missing party invite, etc. — without spending a play turn.