Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

craft-build

Sterne0

Forks0

Aktualisiert17. Juli 2026 um 20:43

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.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

Xian55

Xian55/Craft

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	craft-build
description	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.

craft-build — build, run, screenshot

Confirms a change actually renders (not just compiles), headlessly, via craft's one-shot screenshot hook. No manual window closing.

Steps

Build native (first configure fetches raylib 5.5 via FetchContent — needs network):
```
build.cmd
```
Or the raw commands (gcc/mingw32-make are WinLibs, off-PATH — build.cmd locates them):
```
cmake -S . -B ..\craft_raylib_build\native -G "MinGW Makefiles" -DCMAKE_BUILD_TYPE=Release
cmake --build ..\craft_raylib_build\native -j
```
Web build: build.cmd web then serve.cmd → http://localhost:8080/ .
Run with the screenshot hook. CRAFT_SHOT=N renders N frames, writes craft_shot.png, then exit(0) — no window to close. The PNG lands in the LAUNCH cwd (raylib caches the path at InitWindow), so cd to where you want it first:
```
cd ..\craft_raylib_build\native
CRAFT_SHOT=30 ./craft.exe > run.log 2>&1
```
The client auto-connects to localhost:8080; if no server is up it still renders local terrain (async connect never blocks the frame). Add --serve to play-and-host, or --server for a headless dedicated server (no window/GPU).
Stage the scene with the debug env hooks (compose several):
- CRAFT_POS="x,y,z,yaw,pitch" — teleport + implies fly + creative (frame a specific spot).
- CRAFT_TIME=0..1 — initial day_time (0/1 = midnight, 0.5 = noon) to check the day-night shader.
- CRAFT_CMD="/cmd;/cmd" — run ;-separated chat commands at frame 30 (e.g. /slot 3, /boom 2, /zombie 4, /lang hu).
- CRAFT_METRICS=0..2 — start with the F3 metrics overlay (0 off, 1 compact, 2 graphs).
```
CRAFT_POS="8,80,8,45,-20" CRAFT_TIME=0.5 CRAFT_SHOT=40 ./craft.exe
```
View it. Read craft_shot.png.
- craft's window is 1280×720, no FLAG_WINDOW_HIGHDPI, so the shot is normally 1:1 with no borders. If it comes back with black at top/right (raylib over-capturing by the display DPI scale), crop the bottom-left 1/dpi region — this box is at 125% (dpi = 1.25). There is no ImageMagick here; crop with a Playwright+canvas snippet (see the win-toolchain-paths memory / tools/make_raylib_skill.mjs for the Edge-headless pattern).

Notes

Assets are copied next to the exe by the always-run copy_assets CMake target, and main.c anchors cwd to the exe dir — the run is self-contained wherever the exe lives.
To confirm a change (not the whole scene), screenshot before and after with the SAME CRAFT_POS/CRAFT_TIME so the frames are comparable.
Profiling the real loop (not a gate) is CRAFT_PROF=1 ./craft.exe (per-phase ms table at exit). Isolated hot-path budgets are the craft-bench skill. Full test battery is craft-test.

Mehr aus diesem Repository

gleiches Repository

craft-feature

Xian55/Craft

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.

2026-07-170

craft-test

Xian55/Craft

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.

2026-07-170

craft-bench

Xian55/Craft

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).

2026-07-170

craft-docs

Xian55/Craft

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.

2026-07-170

craft-new-module

Xian55/Craft

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.

2026-07-170

craft-onboard

Xian55/Craft

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.

2026-07-170

name	craft-build
description	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.

craft-build — build, run, screenshot

Confirms a change actually renders (not just compiles), headlessly, via craft's one-shot screenshot hook. No manual window closing.

Steps

Build native (first configure fetches raylib 5.5 via FetchContent — needs network):
```
build.cmd
```
Or the raw commands (gcc/mingw32-make are WinLibs, off-PATH — build.cmd locates them):
```
cmake -S . -B ..\craft_raylib_build\native -G "MinGW Makefiles" -DCMAKE_BUILD_TYPE=Release
cmake --build ..\craft_raylib_build\native -j
```
Web build: build.cmd web then serve.cmd → http://localhost:8080/ .
Run with the screenshot hook. CRAFT_SHOT=N renders N frames, writes craft_shot.png, then exit(0) — no window to close. The PNG lands in the LAUNCH cwd (raylib caches the path at InitWindow), so cd to where you want it first:
```
cd ..\craft_raylib_build\native
CRAFT_SHOT=30 ./craft.exe > run.log 2>&1
```
The client auto-connects to localhost:8080; if no server is up it still renders local terrain (async connect never blocks the frame). Add --serve to play-and-host, or --server for a headless dedicated server (no window/GPU).
Stage the scene with the debug env hooks (compose several):
- CRAFT_POS="x,y,z,yaw,pitch" — teleport + implies fly + creative (frame a specific spot).
- CRAFT_TIME=0..1 — initial day_time (0/1 = midnight, 0.5 = noon) to check the day-night shader.
- CRAFT_CMD="/cmd;/cmd" — run ;-separated chat commands at frame 30 (e.g. /slot 3, /boom 2, /zombie 4, /lang hu).
- CRAFT_METRICS=0..2 — start with the F3 metrics overlay (0 off, 1 compact, 2 graphs).
```
CRAFT_POS="8,80,8,45,-20" CRAFT_TIME=0.5 CRAFT_SHOT=40 ./craft.exe
```
View it. Read craft_shot.png.
- craft's window is 1280×720, no FLAG_WINDOW_HIGHDPI, so the shot is normally 1:1 with no borders. If it comes back with black at top/right (raylib over-capturing by the display DPI scale), crop the bottom-left 1/dpi region — this box is at 125% (dpi = 1.25). There is no ImageMagick here; crop with a Playwright+canvas snippet (see the win-toolchain-paths memory / tools/make_raylib_skill.mjs for the Edge-headless pattern).

Notes

Assets are copied next to the exe by the always-run copy_assets CMake target, and main.c anchors cwd to the exe dir — the run is self-contained wherever the exe lives.
To confirm a change (not the whole scene), screenshot before and after with the SAME CRAFT_POS/CRAFT_TIME so the frames are comparable.
Profiling the real loop (not a gate) is CRAFT_PROF=1 ./craft.exe (per-phase ms table at exit). Isolated hot-path budgets are the craft-bench skill. Full test battery is craft-test.