About unity-ecs-patterns
A skill with production patterns for Unity DOTS, including ECS, the Job System, and Burst Compiler. It is for developers building high-performance games, optimizing CPU-bound logic, or moving object-oriented game code to ECS.
Key features
- 01Unity ECS and DOTS patterns
- 02Job System parallelization
- 03Burst Compiler optimization
- 04Convert object-oriented code to ECS
- 05Manage large entity counts efficiently
Use cases
- 01Build high-performance Unity games
- 02Optimize CPU-bound game logic
- 03Convert existing game code to ECS
- 04Design data-oriented systems for many entities
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ sickn33/ agentic-awesome-skills --skill unity-ecs-patternsAfter installing, type/unity-ecs-patternsin Claude Code to confirm it loaded.
Bundled filesresources/implementation-playbook.md
Details
From the project READMEUnity ECS Patterns
Production patterns for Unity's Data-Oriented Technology Stack (DOTS) including Entity Component System, Job System, and Burst Compiler.
Use this skill when
- 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
Do not use this skill when
- The task is unrelated to unity ecs patterns
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
Example
Implement Speed plus a MovementSystem using the pinned Entities package. Profile a fixed entity cohort before/after; verify movement once per frame and job dependencies before enabling parallel execution.
Resources
resources/implementation-playbook.mdfor detailed patterns and examples.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Comments
Markdown supported