菜单
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.
用 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).
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.
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-sprite |
| description | 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. |
Aseprite is referenced via the ASEPRITE environment variable (User scope), not a hardcoded path, so
this works on any machine that sets it. Current value points at Aseprite.exe.
ASEPRITE must be set. Check / set (PowerShell):
[Environment]::GetEnvironmentVariable("ASEPRITE","User")
# if empty:
[Environment]::SetEnvironmentVariable("ASEPRITE","C:\Program Files\Aseprite\Aseprite.exe","User")
A new shell picks it up. In bash it's "$ASEPRITE"; in PowerShell $env:ASEPRITE.
"$ASEPRITE" -b sprites_src/skeleton.aseprite \
--sheet assets/sprites/skeleton.png \
--data assets/sprites/skeleton.json \
--sheet-type packed --list-tags
-b = batch (headless, no GUI). --sheet packed PNG, --data frame/anim JSON (tags = animations)..aseprite in a folder:
for f in sprites_src/*.aseprite; do
"$ASEPRITE" -b "$f" --sheet "assets/sprites/$(basename "${f%.aseprite}").png" \
--data "assets/sprites/$(basename "${f%.aseprite}").json" --sheet-type packed --list-tags
done
assets/ (gitignored — assets stay local for now); the build stages it next to the exe.--script foo.lua) for custom batch pipelines if needed.