Agent skill · Design & Presentation

game-developer

Use when building game systems, implementing Unity/Unreal Engine features, or optimizing game performance. Invoke to implement ECS architecture, configure physics systems and colliders, set up multiplayer networking with lag compensation, optimize frame rates to 60+ FPS targets, develop shaders, or apply game design patterns such as object pooling and state machines. Trigger keywords: Unity, Unreal Engine, game development, ECS architecture, game physics, multiplayer networking, game optimization, shader programming, game AI.

Jeffallangithub.com/JeffallanGitHub ↗
claude-codeMIT
Install
npx skills add Jeffallan/claude-skills --skill game-developer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 6 KB
Bundled scripts: none
Version: 1.1.0
Declared author: https://github.com/Jeffallan
Path: skills/game-developer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 10,871 · +100 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Game Developer ## Core Workflow 1. **Analyze requirements** — Identify genre, platforms, performance targets, multiplayer needs 2. **Design architecture** — Plan ECS/component systems, optimize for target platforms 3. **Implement** — Build core mechanics, graphics, physics, AI, networking 4. **Optimize** — Profile and optimize for 60+ FPS, minimize memory/battery usage - ✅ **Validation checkpoint:** Run Unity Profiler or Unreal Insights; verify frame time ≤16 ms (60 FPS) before proceeding. Identify and resolve CPU/GPU bottlenecks iteratively. 5. **Test** — Cross-platform testing, performance validation, multiplayer stress tests - ✅ **Validation checkpoint:** Confirm stable frame rate under stress load; run multiplayer latency/desync tests before shipping. ## Reference Guide Load detailed guidance based on context: | Topic | Reference | Load When | |-------|-----------|-----------| | Unity Development | `references/unity-patterns.md` | Unity C#, MonoBehaviour, Scriptable Objects | | Unreal Development | `references/unreal-cpp.md` | Unreal C++, Blueprints, Actor components | | ECS & Patterns | `references/ecs-patterns.md` | Entity Component System, game patterns | | Performance | `

What's inside
Steps it walks through
  1. Core Workflow
  2. Reference Guide
  3. Constraints
  4. MUST DO
  5. MUST NOT DO
  6. Output Templates
  7. Key Code Patterns
  8. Object Pooling (Unity C#)
  9. Component Caching (Unity C#)
  10. State Machine (Unity C#)
Ships with 5 files
  • references/ecs-patterns.md
  • references/multiplayer-networking.md
  • references/performance-optimization.md
  • references/unity-patterns.md
  • references/unreal-cpp.md
More from claude-skills
All skills →
About this skill
What does the game-developer skill do?

Use when building game systems, implementing Unity/Unreal Engine features, or optimizing game performance. Invoke to implement ECS architecture, configure physics systems and colliders, set up multiplayer networking with lag compensation, optimize frame rates to 60+ FPS targets, develop shaders, or apply game design patterns such as object pooling and state machines. Trigger keywords: Unity, Unreal Engine, game development, ECS architecture, game physics, multiplayer networking, game optimization, shader programming, game AI.

How do I install it?

Run `npx skills add Jeffallan/claude-skills --skill game-developer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Jeffallan/claude-skills, a repository with 10,871 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going