SKILL

unity-ecs

Build scalable Unity games with Entity Component System (ECS): systems, queries, jobs, burst compilation, and DOTS patterns. Use for high-performance Unity.

Target: Target not categorized. Automatically collected · unverified.

Excerpt from the author’s documentation

Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.

Read the original English text

Topics in the source

  • Unity ECS
  • Quick Start
  • When to Use
  • Step-by-Step
  • 1. Design Components (Data)
  • 2. Create Systems (Logic)
  • 3. Use Jobs for Parallelism
  • 4. Entity Queries

Building high-performance Unity games with Entity Component System and DOTS. Building games with thousands of similar entities (bullets, particles, NPCs) When MonoBehaviour performance is not enough Need for data-oriented design and cache-friendly code Large-scale simulations or strategy games Keep components small and focused: Systems operate on entities with specific component combinations: Keep components small — single responsibility Avoid managed references in components (use Entity references) Use Burst for math-heavy jobs Batch entities by shared components for rendering Profile with Unity Profiler — measure before optimizing Forgetting to mark jobs with [BurstCompile] Using foreach instead of IJobEntity for large datasets Creating too many systems — group related logic Not disposing NativeArrays and other native containers

Source repository
ssrjkk/agent-skills
Source file
.claude/skills/gamedev/unity-ecs/SKILL.md
Fixed revision
868975614072b553f929cb32c52c5e7dc4ba8734
Read the complete original documentation ↗

Sources and evidence

This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.

Author: ssrjkk/agent-skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-11T03:01:42.721Z.

Categories are inferred from names, descriptions and paths. They do not establish compatibility.

License and attribution

MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.

Original license ↗

Synchronization, copying and user-reported success do not mark a resource as runtime-tested.

Limitations and notes

  • Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.