Optimize Unity ECS Performance

This skill focuses specifically on production patterns for Unity's Data-Oriented Technology Stack (DOTS): the Entity Component System (ECS) for structuring game data and logic around components and systems rather than traditional object-oriented GameObjects, the Job System for splitting work across CPU cores safely, and the Burst Compiler for compiling that job code down to highly optimized native machine code. Unlike a general Unity development skill, this one is narrowly scoped to the data-oriented performance layer - it doesn't cover rendering pipelines, UI, audio, or platform deployment, just the ECS/Jobs/Burst pattern set itself and how they combine to handle very high entity counts efficiently.

Use this skill when building high-performance Unity games that need to manage thousands of entities efficiently, implementing data-oriented game systems from scratch, optimizing CPU-bound game logic that's become a bottleneck under traditional GameObject/MonoBehaviour patterns, converting existing object-oriented Unity code to ECS, or parallelizing game logic across cores with Jobs and Burst.

It is not the right skill for Unity work unrelated to this data-oriented performance layer - rendering, UI, audio, or general game architecture questions fall to broader Unity skills instead, and if the actual bottleneck isn't in bulk entity processing, the overhead of adopting ECS may not be justified for a given project.

Input is a performance-critical Unity system managing many entities (thousands or more) or CPU-bound logic that needs parallelization, or existing OOP game code being converted to a data-oriented design. Output is ECS-structured code - components, systems, and job definitions - compiled through Burst for maximum throughput on the target hardware.

Built on Unity's DOTS stack specifically: the Entity Component System, the Job System for safe multithreading, and the Burst Compiler for native code generation, with a companion resources/implementation-playbook.md for detailed patterns and worked examples beyond this overview.

Unity developers hitting CPU performance limits with traditional GameObject-based architecture who need to adopt ECS, Jobs, and Burst for games managing large numbers of entities, rather than general Unity development guidance.