Wink Pings

Giving AI 74 game development skills: the hardest part is still the jump

One skill pack, 74 game development skills, supporting 10 engines. Install it into Claude Code with one command, and afterward you can use natural language to have AI help you add a double jump, create pixel assets, and package for Steam. But after reading through the developer replies, you realize the real problem was never the number of skills: version drift, engine choice, feel tuning, and build verification are things it cannot handle.

If you want Claude Code or Codex to help you make games, a model alone is not enough. The model knows how to write loops, but it does not know the difference between Godot 4's CharacterBody2D and Unity's Rigidbody, and it certainly does not know what steps you need to go through to package for Steam.

Someone made a skill pack called awesome-gamedev-agent-skills. One command:

npx skills add gamedev-skills/awesome-gamedev-agent-skills

After installation there are 74 skills covering 10 engines: Godot, Unity, Unreal, Phaser, three.js, Roblox, and others. Everything from character movement to publishing on Steam is included.

游戏开发技能包介绍图

The way to use it is to give the AI requirements in ordinary language. After it is installed, you do not need to dig through documentation; just tell the agent “add a double jump to my Godot player,” or “make a matching set of pixel protagonist, enemies, and tiles.” The agent will figure out which engine you are using and then pick the corresponding skills to use.

This design approach is right. The problem with AI coding agents was never that they cannot write code; it is that they do not know the conventions of a specific domain. Godot's node tree, Unity's prefabs, and Unreal's Blueprints each have their own way of doing things. Packaging these conventions into skills is equivalent to giving the agent a domain handbook.

But after reading through the replies under the tweet, you realize the real problem is not the number of skills.

One developer mentioned Godot version drift: agents are already prone to writing 3.x syntax in 4.x projects, such as export var, yield, and KinematicBody2D. If the examples in the skill pack are written for 3.x, that will only push the agent further off course. So before installing, you need to confirm one thing: which version the skills target.

Another issue is engine selection. The skill pack's routing documentation says engine selection is exclusive, and one request maps to only one engine. So if a repository contains both project.godot and a three.js web build, will the agent ask you, or will it choose one itself? Someone raised this question, and no clear answer has been seen yet.

There is also an installation barrier. The skills CLI requires Node.js 22.20 or later; older versions of Node will fail before installation.

These are all still engineering-level concerns. The more fundamental doubts come from people who have made games.

Someone said that adding a double jump is the easy part; what makes agents frequently stumble is not breaking the wall-jump you wrote last week after adding it. Can the skill pack provide tests that let the agent verify its own changes after modifying the code?

Another person said that the 74 skills cover everything from character movement to publishing on Steam, but the hardest part in the middle is still “making the jump feel good.” Are these skills about game feel, or about engine plumbing?

An indie developer working on a Godot voxel city builder put it more concretely: he is very efficient at using AI to write GDScript, but chunk meshing still has to be tuned by hand. He asked whether this pack covers voxels and procedural generation, or whether it only handles classic genres.

And there is consistency. Someone pointed out that each sprite looks good on its own, but by the tenth one the palette starts to drift unless you lock the colors in code. Skills can write mechanics, but they cannot write aesthetic consistency.

My judgment: this pack is worth installing, but its value lies in reducing the time spent repeatedly looking up documentation, not in letting the agent independently make a playable game. It can solve the problem of how to write something. It cannot control whether it is written correctly or whether it is fun. Verification and feel are two things that still need a human watching them for now.

Practical advice: do not install more than seventy at once. As one netizen put it well, first pick the ones you currently need; do not finish researching seventy skills before finishing the game. Single-engine repositories are more stable than multi-engine repositories, and before installing, take a look at your Node version.

发布时间: 2026-10-25 17:27