游戏开发商
- 作者仓库星标 9,590
- 许可证 MIT
- 作者仓库 claude-skills
- 领域
- 设计与多媒体
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @Jeffallan · MIT
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# 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 | `references/performance-optimization.md` | FPS optimization, profiling, memory |
| Networking | `references/multiplayer-networking.md` | Multiplayer, client-server, lag compensation |
## Constraints
### MUST DO
- Target 60+ FPS on all platforms
- Use object pooling for frequent instantiation
- Implement LOD systems for optimization
- Profile performance regularly (CPU, GPU, memory)
- Use async loading for resources
- Implement proper state machines for game logic
- Cache component references (avoid GetComponent in Update)
- Use delta time for frame-independent movement
### MUST NOT DO
- Instantiate/Destroy in tight loops or Update()
- Skip profiling and performance testing
- Use string comparisons for tags (use CompareTag)
- Allocate memory in Update/FixedUpdate loops
- Ignore platform-specific constraints (mobile, console)
- Use Find methods in Update loops
- Hardcode game values (use ScriptableObjects/data files)
## Output Templates
When implementing game features, provide:
1. Core system implementation (ECS component, MonoBehaviour, or Actor)
2. Associated data structures (ScriptableObjects, structs, configs)
3. Performance considerations and optimizations
4. Brief explanation of architecture decisions
## Key Code Patterns
### Object Pooling (Unity C#)
```csharp
public class ObjectPool<T> where T : Component
{
private readonly Queue<T> _pool = new();
private readonly T _prefab;
private readonly Transform _parent;
public ObjectPool(T prefab, int initialSize, Transform parent = null)
{
_prefab = prefab;
_parent = parent;
for (int i = 0; i < initialSize; i++)
Release(Create());
}
public T Get()
{
T obj = _pool.Count > 0 ? _pool.Dequeue() : Create();
obj.gameObject.SetActive(true);
return obj;
}
public void Release(T obj)
{
obj.gameObject.SetActive(false);
_pool.Enqueue(obj);
}
private T Create() => Object.Instantiate(_prefab, _parent);
}
```
### Component Caching (Unity C#)
```csharp
public class PlayerController : MonoBehaviour
{
// Cache all component references in Awake — never call GetComponent in Update
private Rigidbody _rb;
private Animator _animator;
private PlayerInput _input;
private void Awake()
{
_rb = GetComponent<Rigidbody>();
_animator = GetComponent<Animator>();
_input = GetComponent<PlayerInput>();
}
private void FixedUpdate()
{
// Use cached references; use deltaTime for frame-independence
Vector3 move = _input.MoveDirection * (speed * Time.fixedDeltaTime);
_rb.MovePosition(_rb.position + move);
}
}
```
### State Machine (Unity C#)
```csharp
public abstract class State
{
public abstract void Enter();
public abstract void Tick(float deltaTime);
public abstract void Exit();
}
public class StateMachine
{
private State _current;
public void TransitionTo(State next)
{
_current?.Exit();
_current = next;
_current.Enter();
}
public void Tick(float deltaTime) => _current?.Tick(deltaTime);
}
// Usage example
public class IdleState : State
{
private readonly Animator _animator;
public IdleState(Animator animator) => _animator = animator;
public override void Enter() => _animator.SetTrigger("Idle");
public override void Tick(float deltaTime) { /* poll transitions */ }
public override void Exit() { }
}
```
[Documentation](https://jeffallan.github.io/claude-skills/skills/specialized/game-developer/)
章节与文件索引
按说明文件中的顺序排列。
核心工作流程
参考指南
必须做
绝对不能做
输出模板
文件/命令 -> references/unity-patterns.md · references/unreal-cpp.md · references/ecs-patterns.md · references/performance-optimization.md · references/multiplayer-networking.md
内容校验值 -> edff4d41db5a
当前原文的自动摘译,尚未人工审校。
核心工作流程
分析需求 — 确定类型、平台、性能目标、多人游戏需求 设计架构 — 规划 ECS/组件系统,针对目标平台进行优化 实施 — 构建核心机制、图形、物理、AI、网络 优化 — 针对 60+ FPS 进行分析和优化,最大限度地减少内存/电池使用 ✅ 验证检查点:运行 Unity Profiler 或 Unreal Insights;在继续之前验证帧时间 ≤16 ms (60 FPS)。迭代地识别并解决 CPU/GPU 瓶颈。
参考指南
根据上下文加载详细指南: 主题·参考·Unity 开发时加载·
references/unity-patterns.md·Unity C#、MonoBehaviour、可脚本化对象虚幻开发·references/unreal-cpp.md·虚幻 C++、蓝图、Actor 组件 ECS 和模式·references/ecs-patterns.md·实体组件系统、游戏模式必须做
在所有平台上以 60+ FPS 为目标 使用对象池进行频繁实例化 实施 LOD 系统进行优化 定期分析性能(CPU、GPU、内存) 对资源使用异步加载
绝对不能做
在紧密循环或 Update() 中实例化/销毁 跳过分析和性能测试 对标签使用字符串比较(使用 CompareTag) 在 Update/FixedUpdate 循环中分配内存 忽略特定于平台的约束(移动、控制台)
输出模板
实现游戏功能时,请提供: 核心系统实现(ECS 组件、MonoBehaviour 或 Actor) 相关数据结构(ScriptableObjects、结构体、配置) 性能注意事项和优化 架构决策的简要说明