Godot Project Templates

Solid scaffolding for spinning up Godot projects across 2D platformers, top-down RPGs, and 3D FPS games. You get AutoLoad manager templates (game state, inventory, weapons), base classes for actors and levels with proper lifecycle hooks, and a subsystem locator pattern to avoid monolithic singletons. The anti-patterns section is genuinely useful: it warns against hardcoding scene paths, pausing the entire tree without process mode guards, and loading massive levels synchronously. The directory structures are opinionated but sensible, organizing by entity rather than file type. Best used when starting a new project or refactoring an existing mess into something maintainable. Assumes you understand Godot's node lifecycle and signals rather than handholding through basics.

skills.sh installs: 232
GitHub stars: 464
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add thedivergentai/gd-agentic-skills --skill godot-project-templates --agent claude-code

Installs into .claude/skills of the current project.

Files

Project Templates (Navigation)

Scaffold architecture, then adapt — never dump genre tutorials into the project verbatim.

NEVER Do (Expert Anti-Patterns)

Directory & Scaffolding

NEVER hardcode scene paths in dozens of call sites — AutoLoad constants or a scene registry.
NEVER skip .gdignore for designer asset drops outside import pipelines.
NEVER copy-paste templates as-is — Understand structure, then adapt (see checklist below).

Architecture & Lifecycle

NEVER use get_tree().paused without process-mode groups — Pause menus need PROCESS_MODE_ALWAYS. Why: pausing the tree freezes _process on menu nodes too, so buttons never receive input; set gameplay to INHERIT (paused) and menu/HUD to ALWAYS via base_menu.gd or explicit process_mode on the pause root.
NEVER skip virtual lifecycle hooks on base classes — Prefer _initialize_*() over brittle _ready() overrides.
NEVER rely on monolithic God singletons — Signal Bus or Subsystem Locator.