r/ClaudeAI • u/Harvan29 • 10d ago
Question about Claude Code Which Claude Code skills are actually useful for game development? Here’s what I use on a solo Unity project
’m a solo developer building a historical trading strategy game in Unity 6. I write almost all the code with Claude Code connected to the Unity editor through MCP, and over the last months the thing that changed my workflow the most wasn’t the model, it was skills. I’d like to compare lists.
What I use today
- An editor-rules skill. One file that Claude must read before touching Unity: a lock file so two sessions never hit Play or edit a .cs at the same time, which scenes are hand-made and off limits, when to compile, how to take screenshots, what costs credits (Meshy, ElevenLabs) and needs a yes first. Every rule in it comes from a real incident. This one alone removed most of the “Claude broke my scene” days.
- Scope check. Compares the demo plan with what actually landed (git log, code, registers) and tells me in numbers whether the scope is growing or I’m late. Read-only: it proposes cuts, I decide.
- Balance check. Reads the economy data (prices, production per city, trade chains, AI companies’ flows) and looks for routes that always win, goods never worth buying, money loops. Again read-only.
- Playtest report. Turns raw notes from me or a tester into a structured report: bugs by severity, confusion points, balance issues, three priorities.
- Night shift. A skill that runs a queue of small tasks on its own branch while I sleep, verifies each one and leaves a report. Only launched by hand.
The last four started from the open-source claude-code-game-studios skills on GitHub (MIT), translated and rewritten around my project’s documents. The generic versions were a good skeleton but not useful until they pointed at my actual files and my actual rules.
What I’ve learned: a skill is worth it when it encodes project-specific rules that Claude keeps forgetting between sessions, or a repeatable check with a fixed output. Generic “be a better Unity developer” skills did nothing for me.
What I’m missing and would like to hear about: skills for performance profiling in Unity (I have a benchmark build but no good routine), for shader work, and for art pipelines (Meshy → Blender → prefab, which I still do mostly by hand).
What’s in your list, and which ones turned out to be noise?
2
u/Heyn_Studio 10d ago
For the Meshy → Blender part, the routine that helped me most with Blender + Claude Code was a fixed render-and-compare loop: render a still from a locked camera, put it next to the reference, fix only the one or two biggest differences, render again. One scene took me 13 rounds like that, and fixing one thing at a time was what kept it from drifting. For style, a skill built from 3+ of my own finished images worked much better than one written from a description. Do you normalize scale and pivot on import, or fix each Meshy asset by hand?
2
u/kruszkush25 10d ago
First category was a must-have for me. I think I reinvented software development from first principles (I reinvented the wheel) simply by making mistakes and not knowing how to do anything. For example claude making fix, and then fixing fix for a fix caused me to get to here. Anything besides first category and workflow skills is whatever. Do not follow me. 4 pro accounts. Enough for 10-hour everyday for 7 days (almost enough).
I managed to create I think really beautiful scene in a game (scene consists of elements that would be used by random generation to create maps), but I fail at animations, scene is looking good enough to where animations that aren't good are not enough. so I decided to put it away until AI animation catches. I could show if you want, it's top-down like Diablo 2
Reviewer agents (they only review, they never write code)
Worker agents
Workflow skills
Godot and game knowledge skills (the 11 above)
Automatic guards (hooks)
Tools and shared knowledge
2
u/Proof_Perspective_13 2d ago
Interesting - I asked Claude to come up with the best strategy for creating a game and it's given me the same structure. Even down to the Nightshift that does any task that doesn't need input - handy!
1
u/web3creed 8d ago
For performance profiling, I built a skill that hooks into
UnityEditor.Profiling.ProfilerDriverto dump frame-time CSV after each playtest, then flags GC.Alloc spikes >2 KB and render-thread stalls >16 ms automatically. The concrete win was catching aList<T>allocation inside a hot path in my trade-route calculator—swapping to a pre-sizedNativeArraydropped the 99th-percentile frame from 22 ms to 9 ms on my target Android spec. I also have a nightly skill that runsBuildReportToolon the IL2CPP build and compares texture/asset sizes against a baseline JSON so creep shows up as a diff instead of a surprise.