Home › Godot Game Dev Kit
Godot Game Dev Kit
Godot 4 / GDScript 2.0 rules that stop AI writing Godot 3 and Python, with a tested starter project and headless checks.
$24 one-time · v1.1.0 · zip, 145 KB
Buy Godot Game Dev Kit: $24Placeholder: checkout is not connected yet.
Or get it in the Complete Vibe Coding Toolkit (all four kits for $99).
What's inside
- Godot 4 / GDScript 2.0 rules: static typing, a Godot 3 to 4 gotcha table with 45+ rows, architecture, physics, UI, testing.
- A starter project and
check.sh: headless parse, a 30-frame run and a smoke test. Tested on Godot 4.3 and 4.7.2. - An API probe that runs every Godot 4 API the rules mention (60/60 pass), plus /godot-check and /godot-feature skills.
Contains a ready-to-run starter project with every tool's rule files already installed.
Rules (9)
| Rule | When it applies |
|---|---|
agent-workflow | How the AI agent must plan, execute and verify work in this Godot project |
architecture | How to structure scenes, nodes, signals, autoloads and custom Resources in Godot 4 |
core | Non-negotiable Godot 4 / GDScript 2.0 rules for every task in this project |
gdscript-typing | Static typing and GDScript 2.0 syntax rules for all .gd files |
godot4-api | Table of Godot 3 APIs that must never appear and their Godot 4 replacements |
input-physics | Input actions and physics body rules for gameplay scripts |
project-structure | Where files go and how they are named in this Godot project |
testing | How to write and run automated tests for GDScript |
ui-performance | Control-node UI layout and performance rules |
Skills and slash commands (6)
| Command | What it does |
|---|---|
/commit-work | Run all checks, then stage and create a Conventional Commits commit for the current work. Only when the user explicitly asks to commit. |
/fix-bug | Diagnose and fix one bug with a regression test, smallest possible change. Use when the user reports a bug, error message, failing test or unexpected behaviour. |
/godot-check | Validate the Godot 4 project headless (parse every .gd, run the main scene 30 frames, run smoke tests) and fix errors. Use after editing any GDScript or scene, or when the user asks to verify the project. |
/godot-feature | Implement one Godot 4 gameplay feature end-to-end (plan, scene and script with typed GDScript 2.0, signals, input actions, headless check). Use when the user asks for a new mechanic, scene or component in a Godot project. |
/plan-feature | Plan a single feature before writing code. Writes or updates PLAN.md with goal, files, small steps and done-criteria. Use when starting a new feature or when the user asks for a plan. |
/review-changes | Review the current uncommitted diff or branch for bugs, security issues, missing tests and rule violations before committing. Use when asked to review, check or audit changes. |
Every tool, native format
- Cursor:
.cursor/rules/*.mdcwith description/globs/alwaysApply frontmatter. Workflows ship as manual @rules. - Claude Code:
CLAUDE.md(under 200 lines), path-scoped.claude/rulesand.claude/skills/*/SKILL.mdslash commands. - Codex:
AGENTS.md(well under the 32 KiB default cap) and.agents/skills. - Windsurf:
.windsurf/ruleswith trigger frontmatter (each file under 12,000 characters) and.windsurf/workflows. - GitHub Copilot:
.github/copilot-instructions.md,.github/instructions/*.instructions.mdwith applyTo, and.github/prompts/*.prompt.md.
Every file is generated from one master source and checked by a format validator, so the five versions never drift apart.
Install
Unzip, then copy your tool's folder to the project root. See the docs for your tool.