菜单
Bootstrap a new contributor (or a fresh machine) into the craft_raylib project — install the toolchain, build, and verify everything works. Use when setting up the project for the first time, or when a clean-machine setup / environment problem needs fixing. Windows is the primary target.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
The end-to-end harness for building a requested feature in craft autonomously — design it, implement it, test it, gate it on determinism + performance + memory, verify it renders, update docs, and commit. Use whenever the user requests a new gameplay/engine feature (a block, item, mob, mechanic, fluid, UI panel, protocol message) rather than a trivial fix. Defines the required steps and quality gates so the work is reliable and doesn't regress.
Build and run craft's full headless test battery — the terrain determinism gate, the phys/sim/net unit exes, the server self-test, the live-wire e2e, and the bench_test perf+memory gate. Use after changing anything in src/ to check for regressions before committing. All must stay green.
craft's Release-only micro-benchmark + memory harness (bench_test.exe). Use when adding or changing a hot path (gen, mesh, light, fluids), setting a CPU or memory budget, or investigating a ms/allocation regression. Run it before commit as the perf+memory gate; complements CRAFT_PROF (whole render loop) and the F3 metrics overlay (live).
Build the native craft client, run it headless, and capture an in-game screenshot to visually confirm a rendering or gameplay change looks right (not just that it compiled). Use when asked to build and run, screenshot the game, or verify a change on screen. Drives the built-in CRAFT_SHOT one-shot screenshot hook and the CRAFT_POS/TIME/CMD scene-staging hooks.
Keep the project's documentation current after a code change — the root CLAUDE.md and the memory/ dir. Use at the end of any feature or structural change (it's the final step of craft-feature), or whenever commands, architecture, conventions, gotchas, or machine/deploy facts shift. Keep everything lean — CLAUDE.md loads into context every session.
Scaffold a new single-responsibility C module (header + source) in src/, wired into the craft target and any test/bench exe that needs it, following craft's style and build conventions. Use when adding a new system or subsystem so it follows the project's SRP, C11 style, and CMake wiring.
| name | craft-onboard |
| description | Bootstrap a new contributor (or a fresh machine) into the craft_raylib project — install the toolchain, build, and verify everything works. Use when setting up the project for the first time, or when a clean-machine setup / environment problem needs fixing. Windows is the primary target. |
Goal: from nothing to a green build + running client + green tests. Do the steps in order; each ends in a check.
winget install BrechtSanders.WinLibs.POSIX.UCRT.
gcc/mingw32-make are off-PATH in most shells; build.cmd locates them under
%LOCALAPPDATA%\Microsoft\WinGet\... automatically, so you rarely need them on PATH.winget install Oven-sh.Bun...\emsdk sibling of this repo:
git clone https://github.com/emscripten-core/emsdk ..\emsdk
..\emsdk\emsdk install latest && ..\emsdk\emsdk activate latest
Verify: cmake --version, git --version, bun --version. (See the win-toolchain-paths memory
for the exact gcc/emsdk/bun paths on this machine.)
build.cmd # native client + test exes -> ..\craft_raylib_build\native
build.cmd web # optional wasm build (needs emsdk) -> ..\craft_raylib_build\web
Artifacts land out of tree in ..\craft_raylib_build\ (relative paths only).
# determinism gate (the critical one)
bun tools\terrain_ref.mjs > ref.txt
..\craft_raylib_build\native\gen_test.exe > c.txt
diff --strip-trailing-cr ref.txt c.txt # empty
# unit + integration + perf/memory
..\craft_raylib_build\native\phys_test.exe
..\craft_raylib_build\native\sim_test.exe
..\craft_raylib_build\native\net_test.exe
..\craft_raylib_build\native\craft.exe --server-test
..\craft_raylib_build\native\bench_test.exe
bun tools\e2e_net.mjs
# run the client (F3 cycles the metrics overlay)
..\craft_raylib_build\native\craft.exe
Expected: determinism diff empty; every test PASS / exit 0; bench all within budget; a window shows
the voxel world. serve.cmd runs the server + browser client on http://localhost:8080/ .
CLAUDE.md (root) — quick start, build, tests, architecture map, gotchas.memory/ dir (MEMORY.md index) — machine paths, port history, deploy host.gcc not found → install WinLibs (step 1); build.cmd prints the exact winget command.gen.c must build
-ffp-contract=off (CMakeLists sets it) and never with -ffast-math.0xc0000139 running a test → a wrong MinGW runtime DLL is on PATH; the static link should prevent
it — rebuild clean.FETCHCONTENT_UPDATES_DISCONNECTED ON).