AI game development / journal

“Claude of Duty”: What AI Changes in Game Development

“Claude of Duty” is a useful joke because it compresses a real shift: a developer can now ask an agent to move through unfamiliar code, produce a prototype and iterate on a playable surface much faster. The joke becomes unhelpful when it confuses speed of generation with quality of the game.

By Jordan ThirklePublished 2026-08-101 min read

What changed

Agents reduce the cost of trying a small idea. They can scaffold a scene, explain an unfamiliar API, generate test fixtures, compare a diff and turn a design note into a list of implementation tasks.

That makes the loop tighter. It does not decide which mechanic is worth keeping, whether the camera feels good or whether the player understands why they failed.

The new bottleneck is judgement

As generation becomes cheaper, selection and verification become more valuable. The developer’s job shifts toward setting a sharp quality bar, curating references, playing the build and deleting work that does not earn its complexity.

The useful public record is not “AI built this.” It is what the human asked, what the agent changed, what was tested and what was rejected.

A safe working loop

Use small tasks, repository instructions, isolated branches, generated tests and a fresh-context critic. Keep credentials and production deploy authority outside the agent’s default reach.