Skills · Coding

Unity Ecs Patterns

Unverified30/40

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.

Originally by wshobson · MIT

Claude CodePartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
CursorPartialPlain prose you can paste in — but no Cursor rules file
CodexPartialPlain prose you can paste in — but no AGENTS.md
Gemini CLIPartialPlain prose you can paste in
CopilotPartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add unity-ecs-patterns

This command does not work yet — the CLI is still being built. Until then, use Raw in the reader below to take the file.

Who is stuck, and on what

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.

The whole source

No sign-in, no blur, nothing truncated
unity-ecs-patterns/SKILL.md63 lines2.0 KBRawView on GitHub
Frontmatter — 2 properties
nameunity-ecs-patterns
descriptionMaster 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.
1---
2name: unity-ecs-patterns
3description: 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---A5No allowed-tools declared — no way to tell what this skill may touch
5 
6# Unity ECS Patterns
7 
8Production 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```
34Entity: Lightweight ID (no data)
35Component: Pure data (no behavior)
36System: Logic that processes components
37World: Container for entities
38Archetype: Unique combination of components
39Chunk: Memory block for same-archetype entities
40```
41 
42## Detailed patterns and worked examples
43 
44Detailed 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 

Reviews

Installed this one?Write the first review and take the Trailblazer badge.

Reviews only open after a real install, so this is empty — and we leave it empty rather than invent one.

Alternatives

Also in Coding