Godot Best Practices

This is a solid reference for keeping your GDScript code clean and maintainable in Godot 4.x projects. It covers the stuff that actually matters: proper type hints everywhere, using @onready with unique node names instead of fragile paths, signal-driven architecture with the "signal up, call down" pattern, and consistent naming conventions. The quick reference table is genuinely useful for code reviews. It won't teach you game design, but if you're writing GDScript and want to avoid common pitfalls like deep node paths or autoload abuse, this gives you the patterns that scale. The script structure template alone saves time when starting new classes.

install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.: 6
skills.sh installs: 2.1K
GitHub stars: 182
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add jwynia/agent-skills --skill godot-best-practices --agent claude-code

Installs into .claude/skills of the current project.

Files

Godot 4.x GDScript Best Practices

Guide AI agents in writing high-quality GDScript code for Godot 4.x. This skill provides coding standards, architecture patterns, and templates for game development.

When to Use This Skill

Use this skill when:

Generating new GDScript code
Creating or organizing Godot scenes
Designing game architecture and node hierarchies
Implementing state machines, object pools, or save systems
Answering questions about GDScript patterns or Godot conventions
Reviewing GDScript code for quality issues

Do NOT use this skill when:

Working with C# in Godot (use C# patterns)
Working with Godot 3.x (syntax differs significantly)
Using GDExtension/C++ (different paradigm)
Working with Godot's visual scripting

Core Principles

1. Naming Conventions

Follow GDScript naming standards consistently:

# Classes: PascalCase
class_name PlayerController
extends CharacterBody2D

# Signals: past_tense_snake_case (describe what happened)
signal health_changed(new_health: int)
signal player_died
signal item_collected(item: Item)

# Constants: SCREAMING_SNAKE_CASE
const MAX_SPEED: float = 200.0
const JUMP_FORCE: int = -400

SKILL.md on GitHub