菜单
Look up Godot engine class APIs — methods, properties, signals, enums. Use when you need to find which class to use or look up specific API details. Supports version-specific docs — reads the correct API for the project's Godot version.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | godot-api |
| description | Look up Godot engine class APIs — methods, properties, signals, enums. Use when you need to find which class to use or look up specific API details. Supports version-specific docs — reads the correct API for the project's Godot version. |
$ARGUMENTS
Docs are stored per Godot version under doc_api/{version}/ and doc_api_csharp/{version}/.
Determine the version to use:
project.godot exists in the working directory, extract from config/featureslatestBootstrap if docs for the target version are missing:
bash ${CLAUDE_SKILL_DIR}/tools/ensure_doc_api.sh [version]
Language selection: doc_api/{version}/ contains GDScript docs. doc_api_csharp/{version}/ contains C# docs. Default to GDScript unless the caller asks about C#.
${CLAUDE_SKILL_DIR}/doc_api/{version}/_common.md — index of ~128 common classes
${CLAUDE_SKILL_DIR}/doc_api_csharp/{version}/_common.md_other.md in the same directory${CLAUDE_SKILL_DIR}/doc_api/{version}/{ClassName}.md for full API
${CLAUDE_SKILL_DIR}/doc_api_csharp/{version}/{ClassName}.mdC# syntax reference: ${CLAUDE_SKILL_DIR}/csharp.md — C# Godot syntax, patterns, and recipes.
GDScript syntax reference: ${CLAUDE_SKILL_DIR}/gdscript.md — GDScript language spec, type system, patterns.
Generate a new Godot game project with standardized ECS structure and tooling. Use when starting a new game: "create a project", "set up a new game", "scaffold", "initialize", "new project", "start building", "let's make it". Triggers after game-planner produces a confirmed plan, or when the user provides a game name + genre directly. Even for simple requests like "make me a new Godot project", use this skill to ensure proper ECS structure. Creates directory structure, project.godot, CLAUDE.md, gecs World setup, addon stubs, and template source files based on the game plan or user input.
Evaluate the current tag's quality: enforce the playable-closed-loop gate, maintain a single cross-tag e2e/ suite that always reflects the current game (add tests for new mechanics, prune tests for mechanics this tag deliberately removed), and reason about gameplay quality. Independent from the build process — fresh perspective on the final product. Explicit invocation only — use /gm-evaluate.
Reviews Godot Animation implementation for known pitfalls. Triggers AFTER implementation, when code involves AnimationPlayer, AnimationTree, AnimatedSprite2D, SpriteFrames, AnimationNodeStateMachine, BlendSpace, OneShot, callback_mode_process, or animation playback control (play/travel/start). Do NOT use this skill for planning or teaching — only for post-implementation review.
Run gdUnit4 unit tests and parse results into structured output. Use this skill after writing or modifying code to verify correctness via unit tests, when diagnosing test failures, or when writing new test files. Triggers: "run tests", "test fails", "write a test", any gdUnit4/unit test mention. Supports both GDScript (.gd) and C# (.cs) test files.
Asset stage manager. Reads current-tag ASSETS.md gaps, accepts user-provided assets, plans visual production units, dispatches asset-producer subagents, collects reports, updates ASSETS.md and the asset-generation manifest. Explicit invocation only - use /gm-asset.
Scaffold a new Godot project: project.godot + addons + base directories + e2e/conftest.py + initial git commit. Lifetime-once role — runs only on fresh projects. Explicit invocation only — use /gm-scaffold.