菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
| name | beads-github-sync |
| description | 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. |
GitHub Issues are a generated projection of beads for contributors, not a second source of truth. Beads (.beads/) is authoritative; never treat a GitHub issue edit as the durable record.
scripts/beads-github-publish.py is the publisher. Each in-scope bead maps to one issue keyed by a <!-- beads-id: <id> --> body marker. It keeps in sync:
vanilla-parity / enhanced / area:* / status:*.github/workflows/beads-github-publish.yml runs it automatically on every push to main that touches .beads/issues.jsonl, publishing all beads (not just roadmap-labelled ones). workflow_dispatch remains available for manual runs, where dry_run defaults to true.
Beads edits only reach GitHub once the auto-exported .beads/issues.jsonl is committed and pushed. A bead changed locally but not exported/pushed will look stale on GitHub — that's the usual cause of "my issue didn't update".
scripts/beads-github-sync.sh is independent and opt-in. It imports GitHub issues into beads, keyed on external_ref: gh-<number>.
The two directions are not a loop — don't round-trip the same issues through both.