Godot Production Base

Build fast without quietly losing parts of your game.

Godot Production Base is a ready-to-use Godot project built around one simple idea:

Every change should have to prove it did not break, remove or silently forget something that already worked.

That matters in normal development, but it matters even more with AI.

AI coding tools are very good at making large changes quickly. They are also perfectly capable of:

• fixing one system while breaking another
• rewriting a file and leaving out an existing feature
• removing an edge case because it looked unnecessary
• replacing a working system with a simpler one that does less
• forgetting functionality several updates later
• declaring a task finished without ever checking the full project

Production Base gives your project a persistent verification layer so those regressions are much harder to slip through unnoticed.

What it gives you

Testing, validation, diagnostics, lifecycle checks and regression protection are already wired together.

Run:

python tools/godot_tasks.py check --godot /path/to/godot

A healthy project finishes with:

PRODUCTION CHECK COMPLETE: PASS

If something breaks, disappears, leaks, fails a test, touches protected code, uses a retired API or violates a rule you have set, the project does not get a clean pass.

Your project remembers itself

Production Base does not try to make an AI remember your entire game.

Instead, the project records what matters.

As your game grows, you can protect important behaviour with:

• regression tests
• project validators
• frozen files
• retired API rules
• architecture limits
• lifecycle checks
• generated-file freshness checks

So if an AI comes back three updates later and quietly drops something that was already working, there is a much better chance the project catches it immediately.

The goal is not to pretend AI never makes mistakes.

The goal is to stop those mistakes from quietly becoming the new version of your game.

Manual use

Use it like a normal Godot project.

Make your changes, run the check, and continue if it passes.

As the game grows, add tests and rules for things you never want lost or broken again.

AI use

Give the project to ChatGPT, Claude, Codex, Cursor or whatever coding tool you already use.

Tell it:

Read AGENTS.md first. Preserve existing behaviour, tests and project rules. After meaningful changes, run the Production Base check. Do not call the task complete unless it reaches PRODUCTION CHECK COMPLETE: PASS. If a test or validator fails, fix the cause rather than deleting or weakening the check.

Then ask for the work normally.

Production Base is not the AI.

It is the part that stops “looks done” from being good enough.

What it can help catch

• working features disappearing during rewrites
• old behaviour being accidentally omitted
• previously fixed bugs coming back
• broken scripts and resources
• failed tests
• startup and teardown problems
• orphan/leak-style lifecycle regressions
• retired APIs being used again
• protected files changing during refactors
• stale generated files
• architecture drifting past limits you set
• incomplete checks being mistaken for success

What it is not

No gameplay framework. No inventory system. No quests. No combat framework. No MCP server. No AI subscription. No vendor lock-in. No giant dependency you have to keep updating.

It is a verified starting point that grows with your game.

The main improvement is that “your project remembers itself” becomes the central idea instead of explaining the same concept repeatedly in different sections. That is probably the strongest differentiator in the whole product.