Master Unity ECS with DOTS, Jobs

Unity ecs patterns

by wshobson · MIT license · ★ 39,857 on GitHub · updated Sep 21

Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large entity counts.

---
name: unity-ecs-patterns
description: Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large entity counts.
---

# Unity ECS Patterns

Production patterns for Unity's Data-Oriented Technology Stack (DOTS) including Entity Component System, Job System, and Burst Compiler.

## When to Use This Skill

- Building high-performance Unity games
- Managing thousands of entities efficiently
- Implementing data-oriented game systems
- Optimizing CPU-bound game logic
- Converting OOP game code to ECS
- Using Jobs and Burst for parallelization

Overview

Production patterns for Unity's Data-Oriented Technology Stack (DOTS) including Entity Component System, Job System, and Burst Compiler.

Manual install (npx, ZIP)

Claude Codenpx skills add wshobson/agents --skill unity-ecs-patterns -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/wshobson/agents/tar.gz/4236bb91f839 \
  | tar -xz -C ~/.claude/skills --strip-components=4 agents-4236bb91f839/plugins/game-development/skills/unity-ecs-patterns

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/7b49b97ceab6eb7a0d99/unity-ecs-patterns.zip" -OutFile "$env:TEMP\unity-ecs-patterns.zip"; Expand-Archive "$env:TEMP\unity-ecs-patterns.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md2.0 KB
references/1 file · 14.1 KB

Read the files here

wshobson/4236bb92 files

SKILL.md2.0 KB

SKILL.md

Show the full text63 lines

unity-ecs-patterns/SKILL.md63 lines · 2.0 KB

PreviewCode

Outline

RawView on GitHub

Unity ECS Patterns

Production patterns for Unity's Data-Oriented Technology Stack (DOTS) including Entity Component System, Job System, and Burst Compiler.

When to Use This Skill

Building high-performance Unity games
Managing thousands of entities efficiently
Implementing data-oriented game systems
Optimizing CPU-bound game logic
Converting OOP game code to ECS
Using Jobs and Burst for parallelization

Core Concepts

1. ECS vs OOP

Aspect	Traditional OOP	ECS/DOTS
Data layout	Object-oriented	Data-oriented
Memory	Scattered	Contiguous
Processing	Per-object	Batched
Scaling	Poor with count	Linear scaling
Best for	Complex behaviors	Mass simulation

2. DOTS Components

Entity: Lightweight ID (no data)
Component: Pure data (no behavior)
System: Logic that processes components
World: Container for entities
Archetype: Unique combination of components
Chunk: Memory block for same-archetype entities

Detailed patterns and worked examples

Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.

Best Practices

Do's

Use ISystem over SystemBase - Better performance
Burst compile everything - Massive speedup
Batch structural changes - Use ECB
Profile with Profiler - Identify bottlenecks
Use Aspects - Clean component grouping

Don'ts

Don't use managed types - Breaks Burst
Don't structural change in jobs - Use ECB
Don't over-architect - Start simple
Don't ignore chunk utilization - Group similar entities
Don't forget disposal - Native collections leak

1	---
2	name: unity-ecs-patterns
3	description: Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large entity counts.
4	---
5
6	# Unity ECS Patterns
7
8	Production patterns for Unity's Data-Oriented Technology Stack (DOTS) including Entity Component System, Job System, and Burst Compiler.
9
10	## When to Use This Skill
11
12	- Building high-performance Unity games
13	- Managing thousands of entities efficiently
14	- Implementing data-oriented game systems
15	- Optimizing CPU-bound game logic
16	- Converting OOP game code to ECS
17	- Using Jobs and Burst for parallelization
18
19	## Core Concepts
20
21	### 1. ECS vs OOP
22
23	\| Aspect \| Traditional OOP \| ECS/DOTS \|
24	\| ----------- \| ----------------- \| --------------- \|
25	\| Data layout \| Object-oriented \| Data-oriented \|
26	\| Memory \| Scattered \| Contiguous \|
27	\| Processing \| Per-object \| Batched \|
28	\| Scaling \| Poor with count \| Linear scaling \|
29	\| Best for \| Complex behaviors \| Mass simulation \|
30
31	### 2. DOTS Components
32
33	```
34	Entity: Lightweight ID (no data)
35	Component: Pure data (no behavior)
36	System: Logic that processes components
37	World: Container for entities
38	Archetype: Unique combination of components
39	Chunk: Memory block for same-archetype entities
40	```
41
42	## Detailed patterns and worked examples
43
44	Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
45
46	## Best Practices
47
48	### Do's
49
50	- Use ISystem over SystemBase - Better performance
51	- Burst compile everything - Massive speedup
52	- Batch structural changes - Use ECB
53	- Profile with Profiler - Identify bottlenecks
54	- Use Aspects - Clean component grouping
55
56	### Don'ts
57
58	- Don't use managed types - Breaks Burst
59	- Don't structural change in jobs - Use ECB
60	- Don't over-architect - Start simple
61	- Don't ignore chunk utilization - Group similar entities
62	- Don't forget disposal - Native collections leak
63