菜单
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.
用 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.
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.
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.
| name | craft-test |
| description | 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. |
All tests are native, headless, and live in ..\craft_raylib_build\native (built by build.cmd).
Run the ones your change can touch; run all of them before a commit.
build.cmd # builds craft.exe + gen_test/phys_test/sim_test/net_test/bench_test
gen must stay a pure, deterministic, double-only function so every client on the same build generates
the same world (C↔C multiplayer determinism). The gate compares gen_test.exe output against a
committed C golden (tests/gen_golden.txt); the legacy JS ref is retired (JS cross-play dropped):
..\craft_raylib_build\native\gen_test.exe > c.txt
diff --strip-trailing-cr tests\gen_golden.txt c.txt # MUST be empty
If this diffs unintentionally, stop — something changed gen output (watch FP contraction, pow
vs x*x*sqrt(x), ToInt32 emulation, -ffp-contract=off). If the change is intentional (a new
terrain feature), re-bless the golden and commit it, calling it out in the commit message:
..\craft_raylib_build\native\gen_test.exe > tests\gen_golden.txt
..\craft_raylib_build\native\phys_test.exe # swept AABB, stats/damage/eat
..\craft_raylib_build\native\sim_test.exe # fluids / TNT / sand / crafting
..\craft_raylib_build\native\net_test.exe # proto codec golden bytes + interpolation
..\craft_raylib_build\native\craft.exe --server-test
Covers the edits-file goldens, relay goldens, the RFC 6455 accept vector, players.json round-trip, and batch split.
craft --server)bun tools\e2e_net.mjs
Exercises join order, the 20 Hz relay, replay, heartbeat, and reject against a live server.
Release-only micro-benchmarks with ms + allocation budgets; exits nonzero if any hot path (gen/mesh/light/fluids) is over its ms budget or allocates more than its ceiling:
..\craft_raylib_build\native\bench_test.exe
See the craft-bench skill to add a case or read a regression. This is the perf half of the craft-feature commit gate.
0xc0000139 at startup means a wrong runtime DLL is on
PATH (the static link should prevent it — rebuild clean).tests/<name>_test.c, wired into CMakeLists.txt
(mirror the existing add_executable blocks; link raylib if it pulls world/mesh, m if pure).