Unity Ecs Patterns

This breaks down Unity's DOTS architecture with actual production patterns you'll need when moving from GameObject-based code to ECS. It covers the core shift from object-oriented to data-oriented design, shows proper ISystem implementation with Burst compilation, and handles the tricky bits like Entity Command Buffers for structural changes and Aspects for grouping related components. The examples focus on real scenarios like movement systems, entity spawning, and query optimization. If you're dealing with thousands of entities or need serious performance gains from parallelization, this gives you the concrete patterns to structure your ECS code properly instead of fighting the paradigm shift.

install copies · 90 days. Times the install command was copied on this site in the last 90 days, bots filtered.: 10
skills.sh installs: 12.5K
GitHub stars: 42.4K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add wshobson/agents --skill unity-ecs-patterns --agent claude-code

Installs into .claude/skills of the current project.

Files

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