Back to catalog
Human reviewedDesign

Skill dossier

game-developer

Source declaration

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.

The author's original description, preserved in English. It describes intent, not verified performance.

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.

designreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

A game development Skill for Unity and Unreal Engine work, covering ECS, physics, networking and performance with profiler-based validation checkpoints for frame time.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Analyzes genre, platforms, performance targets and multiplayer needs.
  • Implements mechanics using ECS or component patterns, object pooling and state machines.
  • Profiles with Unity Profiler or Unreal Insights and checks frame time against a 16 ms target.
  • Runs cross-platform and multiplayer latency and desync tests before shipping.

Limitations & scope

  • Profiling and stress tests need the actual engine and target devices; the agent cannot run them from the skill alone.
  • Code examples are Unity C# only, while Unreal guidance sits in a separate reference file.
  • A blanket 60+ FPS target may not suit every platform, and results are not verified here.

Relevant for

  • Unity developers implementing gameplay systems
  • Unreal developers optimizing performance

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
53.2 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/game-developer/references/ecs-patterns.mdReference10.1 KB
skills/game-developer/references/multiplayer-networking.mdReference12.4 KB
skills/game-developer/references/performance-optimization.mdReference10 KB
skills/game-developer/references/unity-patterns.mdReference6.3 KB
skills/game-developer/references/unreal-cpp.mdReference8.6 KB
skills/game-developer/SKILL.mdInstruction5.8 KB

SKILL.md frontmatter

{
  "name": "game-developer",
  "description": "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.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "specialized",
    "triggers": "Unity, Unreal Engine, game development, ECS architecture, game physics, multiplayer networking, game optimization, shader programming, game AI",
    "role": "specialist",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": ""
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Analyze requirements

    Identify genre, platforms, performance targets and multiplayer needs.

  2. 02
    Action

    Design and implement

    Plan ECS or component systems and build core mechanics, graphics, physics, AI and networking.

  3. 03
    Decision

    Profile against the frame budget

    Run Unity Profiler or Unreal Insights and verify frame time is at most 16 ms before proceeding.

  4. 04
    Output

    Deliver systems and rationale

    Provide the core system, data structures, performance considerations and architecture explanation.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

168 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Note

File modification is described or implemented

164 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 164 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

4 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 4 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Review any networking or save-data code for trust and validation of client input before shipping multiplayer features.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/game-developer # .claude/skills/game-developer
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/game-developer/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Ask Claude Code to write an object pool and confirm it follows the no-instantiate-in-Update rule.

Prerequisites

  • Profiling and stress tests need the actual engine and target devices; the agent cannot run them from the skill alone.
  • Code examples are Unity C# only, while Unreal guidance sits in a separate reference file.
  • A blanket 60+ FPS target may not suit every platform, and results are not verified here.

Example prompts

Representative task

Use the game-developer skill to implement a Unity object pool for projectiles and a player controller that caches components in Awake and moves with fixedDeltaTime, then list what to profile.

Inspect before use

Read the game-developer skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/game-developer/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Gives concrete performance rules such as no GetComponent in Update and no allocations in loops.
  • Includes working patterns for pooling, component caching and state machines.

Considerations

  • Fixed rules like always target 60 FPS can conflict with design needs.
  • Engine APIs change across versions, so examples need checking against your Unity or Unreal version.
Research conclusion

A solid performance-minded checklist for Unity-centric game code, though verification still depends on real profiling.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/game-developer
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.