菜单
Bootstrap a new contributor (or a fresh machine) into the Adventure project — install the toolchain, set environment variables, build, and verify everything works. Use when someone is setting up the project for the first time, or when a clean-machine setup / environment problem needs fixing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Add or change a player input action (a key/mouse-driven control) the right way — routed through the rebindable input action map, never a hard-coded key. Use whenever you introduce a new control (a new key/button the player presses) or change how an existing control is read, so it stays rebindable via keybindings.cfg.
Build and run the Adventure headless unit-test suite (doctest via CTest). Use after changing anything in adventure_lib (Lua engine, metrics, systems) to check for regressions before committing.
Authoritative reference for the TrenchBroom/Quake Valve 220 .map format and Adventure's map conventions. Use when authoring, generating, editing, debugging, or validating a .map file, or wiring TrenchBroom to the project. TrenchBroom has no MCP server or CLI/scripting API — .map is plain text, so we generate/validate it ourselves (parser: src/world/MapParser).
Produce/export game sprites (billboard atlases, viewmodels) with Aseprite via the ASEPRITE env var, so scripts stay machine-independent. Use when creating or batch-exporting sprite sheets, or setting up Aseprite CLI automation for the asset pipeline.
Keep the project's documentation current after a code change — the subsystem CLAUDE.md files, the root CLAUDE.md, and docs/design. Use at the end of any feature or structural change (it's the final step of adv-feature), or whenever architecture, commands, conventions, or milestone status shift.
The end-to-end harness for building a requested feature in Adventure autonomously — design it, implement it under SRP, test it thoroughly, gate it on performance, verify it, and commit. Use this whenever the user requests a new gameplay/engine feature (a system, mechanic, weapon, enemy, level element, etc.) rather than a trivial fix. It defines the required steps and quality gates so the work is reliable and doesn't regress performance.
| name | adv-onboard |
| description | Bootstrap a new contributor (or a fresh machine) into the Adventure project — install the toolchain, set environment variables, build, and verify everything works. Use when someone is setting up the project for the first time, or when a clean-machine setup / environment problem needs fixing. |
Goal: from nothing to a green build + running game. Windows is the primary target. Do the steps in order; each ends in a check.
winget install BrechtSanders.WinLibs.POSIX.UCRT (gcc on PATH), orcmake --version, git --version, and gcc --version (MinGW) or a VS Developer prompt (MSVC).git clone https://github.com/Xian55/Adventure.git
cd Adventure
Note: assets/ binaries are gitignored (kept local); the build still works (only the .gitkeep skeleton
is tracked).
Set the tool paths the skills reference — adjust to your install locations:
# Aseprite (only if you'll export sprites) — used by adv-sprite / the asset pipeline
[Environment]::SetEnvironmentVariable("ASEPRITE","C:\Program Files\Aseprite\Aseprite.exe","User")
Open a new shell so the variables take effect. Verify: $env:ASEPRITE.
(See memory/docs for the current canonical list; keep this in sync when a new tool env var is added.)
cmake --preset mingw-debug # or: msvc-debug
cmake --build build/mingw-debug
# unit tests (headless)
ctest --test-dir build/mingw-debug --output-on-failure
# perf gate (Release)
cmake --preset mingw-release && cmake --build build/mingw-release
ctest --test-dir build/mingw-release -C Release --output-on-failure
# run the game (F3 = metrics overlay)
./build/mingw-debug/adventure.exe
Expected: tests + bench green; a window shows a pixelated, fogged scene; console prints
ScriptEngine selfTest OK.
pip install clang-format==19.1.5) so adv-format and the
CI format gate agree. Enable "format on save" pointed at the repo .clang-format if your editor supports it..editorconfig is respected by most editors (tabs, LF, final newline).CLAUDE.md (root) — commands, layout, conventions, gotchas.docs/design/VISION.md, ARCHITECTURE.md, ROADMAP.md, DEVELOPMENT_LOOP.md.src/<name>/CLAUDE.md for whatever you'll touch.adv-feature (the dev loop), adv-test, adv-build, adv-new-module, adv-format, adv-docs,
adv-map, adv-sprite.0xc0000139 running tests → wrong MinGW runtime DLL on PATH; the static link should prevent it (rebuild).mingw-* vs msvc-*); for MSVC run
from a Developer prompt or via vcvars64.bat.