godot-navigation-pathfinding — Claude Code skill: overview
Teaches your AI assistant to handle path planning, crowd movement, and runtime navmesh generation in Godot. Prevents stuttering and silent bugs in RTS or stealth projects.
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-navigation-pathfinding -a claude-codeWhat godot-navigation-pathfinding does
The skill equips assistants with hard rules for NavigationServer2D and NavigationServer3D. Synchronous mesh baking during gameplay freezes frames for over 100 milliseconds. Silent failures ruin navigation quickly. Setting destinations in _ready() fails without awaiting a physics frame. The guidance enforces asynchronous geometry baking and deferred target assignment.
It provides modular GDScript helpers for tricky mechanics. async_dynamic_baking.gd offloads polygon generation to background threads. For thousands of units, standard nodes create heavy overhead. Direct server RIDs solve that problem. Helpers like agent_stuck_detection.gd detect immobilized bots, while query pooling prevents garbage collection spikes.
What it helps with
- bake navigation meshes asynchronously to eliminate runtime frame drops
- manage large crowds with direct NavigationServer RIDs instead of heavy nodes
- detect and recover stuck AI agents in complex geometry
- configure RVO collision radius and avoidance callbacks properly
- prevent memory allocation spikes by reusing navigation query objects
Example prompts for the agent
- Write an enemy chase script in Godot that updates target position using a distance threshold instead of running every frame
- Show how to set up server-side RVO crowd avoidance without NavigationAgent nodes using low_level_avoidance.gd
- Implement runtime asynchronous navmesh generation in Godot using async_dynamic_baking.gd
How to install godot-navigation-pathfinding
1Skills CLI (Vercel)
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-navigation-pathfinding -a claude-code2Manually: put the files in place
~/.claude/skills/godot-navigation-pathfinding/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/godot-navigation-pathfinding/
1Skills CLI (Vercel)
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-navigation-pathfinding -a codex2Manually: put the files in place
.agents/skills/godot-navigation-pathfinding/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-navigation-pathfinding -a cursor2Manually: put the files in place
.cursor/skills/godot-navigation-pathfinding/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install thedivergentai/Game-Dev-Agentic-Skills godot-navigation-pathfinding2Manually: put the files in place
.github/skills/godot-navigation-pathfinding/SKILL.md1Skills CLI (Vercel)
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-navigation-pathfinding -a gemini-cli2Platform CLI
gemini skills install https://github.com/thedivergentai/Game-Dev-Agentic-Skills --path skills/godot-navigation-pathfindingManually: put the files in place
.devin/skills/godot-navigation-pathfinding/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-navigation-pathfinding -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about godot-navigation-pathfinding
How do I install godot-navigation-pathfinding in Claude Code?
Run npx skills add thedivergentai/Game-Dev-Agentic-Skills --skill godot-navigation-pathfinding -a claude-code in your terminal. This imports the skill rules and GDScript reference files into your agent environment.
What does godot-navigation-pathfinding do?
It supplies coding assistants with verified implementation patterns and scripts for Godot pathfinding. It steers the agent away from common traps like synchronous navmesh baking and per-frame path recalculation.
Why should you avoid setting target_position every physics frame?
Updating the target 60 times per second triggers continuous path queries and wastes CPU time. The skill prescribes updating targets on a timer around 0.2 seconds or when the objective moves past a distance threshold.