unity ecs patterns
- Repo stars 36,312
- Author repo agents
- Domain
- Data
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @wshobson · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Detailed patterns and worked examples
Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
# 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
Sections and files
Listed in source order.
sections -> When to Use This Skill → Core Concepts → 1. ECS vs OOP → 2. DOTS Components → Detailed patterns and worked examples → Best Practices
terms -> Use ISystem over SystemBase · Burst compile everything · Batch structural changes · Profile with Profiler · Use Aspects · Don't use managed types · Don't structural change in jobs · Don't over-architect
files/cmd -> references/details.md · ECS/DOTS
body sha256 -> 0c5bdb0b4b8e
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
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
Detailed patterns and worked examples
Detailed pattern documentation lives in
references/details.md. Read that file when the navigation tier above is insufficient.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