- Home
- Skills
- Jeffallan
- Claude Skills
- Game Developer
game-developer_skill
- HTML
110
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill jeffallan/claude-skills --skill game-developer- SKILL.md3.9 KB
Overview
This skill helps implement robust, high-performance game systems for Unity, Unreal, and custom engines. It focuses on architecture, cross-platform optimization, multiplayer systems, and practical patterns to reach consistent 60+ FPS targets. Use it as an expert pair programmer for gameplay, rendering, physics, and networking tasks.
How this skill works
I analyze project requirements (genre, platforms, performance targets, multiplayer needs) and recommend architecture and concrete implementations: ECS components, MonoBehaviours, or Unreal Actors. I provide code-level outlines, data structures (ScriptableObjects, structs), and actionable performance measures: profiling steps, pooling strategies, LOD, and async loading. I iterate on testing and optimization with platform-specific guidance.
When to use it
- Building core game systems (ECS architecture, physics, AI)
- Implementing Unity C# or Unreal C++ features and Actor/Component design
- Designing and optimizing multiplayer networking, client prediction, lag compensation
- Profiling and optimizing CPU/GPU/memory to hit 60+ FPS targets
- Creating shaders, rendering pipelines, or LOD/occlusion strategies
- Applying game patterns: object pooling, state machines, command/observer patterns
Best practices
- Target 60+ FPS and profile early and often (CPU, GPU, memory)
- Avoid allocations in Update/FixedUpdate; cache components and use pooling
- Use deltaTime for frame-independent movement and proper fixed-step physics
- Implement asynchronous resource loading and streaming for large assets
- Use LOD, occlusion culling, and draw-call batching to reduce GPU work
- Design clear state machines and keep gameplay logic data-driven (ScriptableObjects/configs)
Example use cases
- Implement an ECS-based enemy system with optimized collision and pooled projectiles
- Convert a heavy MonoBehaviour update loop to event-driven architecture and cached references
- Design a client-server multiplayer scheme with prediction, reconciliation, and lag compensation
- Profile a scene to reduce draw calls, add LOD and occlusion to reach 60 FPS on mobile
- Create a shader and GPU-friendly material setup with batching and minimal branching
FAQ
Identify target platforms (PC, console, mobile), expected frame budget, memory limits, and file I/O/streaming constraints before optimizing or choosing assets.
How do I avoid runtime allocations?
Use object pools, reuse arrays/collections, avoid string operations in hot paths, cache component references, and allocate large buffers during loading.
When should I choose ECS over classic OOP components?
Choose ECS for many similar entities requiring cache-friendly iteration and high performance. Use classic components for complex, stateful Actors or when engine tooling is primary.