
Getting a model to write a function is easy. Keeping a real game honest across nine months, twenty levels, a generated art pipeline, sixty-six sound effects and two app stores is the hard part, and it is what this course is about.
It comes from building and releasing Sango: The Thunder God in Godot 4 with Claude. It is organised as a catalogue of failures: the specific, expensive, non-obvious ways a production codebase, an art pipeline, an audio library, an automated test harness and a mobile build go wrong, each with the measurement that found it and the practice that stops it coming back.
Some of what is covered
The context file as the real product of an AI-assisted project, and how its documents go stale without anyone noticing
Measurement over reasoning: throwaway probes, and the exact prompts that get a model to write one
What to delegate to a model and what to keep
Six ways a tool lies to you, including a filter that matches nothing and prints the same as one with nothing to do
Engine traps: the physics flush, time scale and hit-stop, ray probes that start inside a shape, softlock guards that fire on a fight that is merely hard
Generated art as a pipeline: the generator's failure taxonomy, registration, the foot line, and the anchoring problem in full
Audio measured in numbers: four ways a sound cue fails, and how to find each one
A bot that plays your levels, and the harness bugs that make its reports wrong
The last mile: build size, secrets that end up inside exported builds, Android install failures, the App Store build that Godot cannot sign by itself, and monetisation
What's inside
17 chapters in seven parts
The invariant catalogue: 136 numbered rules you can paste into your own project's context file
Tooling patterns: working skeletons for probes, build checks and verifiers you can adapt
Real numbers throughout, from the measurements that settled each problem
Who it is for
Mid-level and senior developers who have shipped software
You already work with an AI model and find it somewhere between genuinely useful and slower than doing it yourself
Godot helps but is not required. The engine chapters are Godot; the material on measurement, delegation, pipelines and QA applies to any engine
What you get
A 144-page PDF for phone or desktop, about 42,000 words
Written against Godot 4.7
Delivered immediately after checkout
New to Godot? Read chapters 3 and 5 of Zero to Hero first, on the editor and your first scene.