Guide · Agent skill
How to use the Unity ECS Patterns agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The unity-ecs-patterns skill is a reference guide that gives your AI agent the patterns, terminology and best practices of Unity's Data-Oriented Technology Stack (DOTS), covering Entity Component System, the Job System and the Burst Compiler. This guide explains what the skill changes about the agent's advice, how to install it, how to ask for help in a way that triggers it, and where it falls short. By the end you will know whether it fits a Unity project that needs to process large numbers of objects efficiently.
Unity ECS Patternswshobson/agents · MIT Download the skill Quick start
- 1Download the ZIP. Download the skill ZIP file from this page.
- 2Unzip the skill. Unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder.
- 3Or upload it in the Claude apps. Go to Settings → Capabilities → Skills and upload the skill there.
- 4Confirm your Unity setup. Make sure your project uses the Entities, Jobs and Burst packages.
- 5Ask a Unity DOTS question. Describe your goal and mention Unity or DOTS in plain terms.
- 6Review the suggestions. Check any code the agent gives you against your Unity version and compile and test it.
What does the unity-ecs-patterns skill make the agent do?
An agent skill is a folder of instructions that an AI agent loads when a task matches the skill's description. This one covers Unity's Data-Oriented Technology Stack. Its core idea is to process large numbers of entities in batches rather than one object at a time.
With the skill loaded, the agent can explain core concepts such as entities, components, systems, archetypes and chunks, and compare ECS with traditional object-oriented code. It also applies a set of best practices to the code it suggests.
- Prefer ISystem over SystemBase
- Batch structural changes with an entity command buffer (ECB)
- Avoid managed types in Burst-compiled code
- Dispose native collections to prevent leaks
- Use Aspects for clean component grouping
- Profile with the Profiler to find bottlenecks
How do you install the unity-ecs-patterns skill?
Download the ZIP file from this page and unzip it. You can install the skill in one of two ways.
For a personal install available across your projects, unzip it into ~/.claude/skills/. To limit it to a single project, unzip it into that project's .claude/skills/ folder.
You can also upload the skill in the Claude apps by going to Settings → Capabilities → Skills.
- Personal: ~/.claude/skills/
- Single project: .claude/skills/ inside your project
- Claude apps: Settings → Capabilities → Skills
How do you trigger the skill with natural requests?
You do not need a special command. The skill is meant to load when your request matches its description, which covers building data-oriented games, optimizing performance, and working with large entity counts. Describe your goal in plain terms and mention Unity or DOTS so the match is clear.
- Help me convert this MonoBehaviour enemy spawner to ECS with ISystem.
- My game slows down with 5,000 projectiles. How can I use Jobs and Burst?
- Review this system for managed types that would break Burst compilation.
- Should I use an entity command buffer for these structural changes?
What do you need before using it?
The skill assumes you already work in Unity and C#. It is written for projects that use the Unity DOTS packages (Entities, Jobs and Burst). The files do not specify exact package versions, so check the documentation for your Unity release.
The skill does not run scripts and does not use the network. It only shapes the agent's advice and code suggestions.
- Unity with DOTS packages: Entities, Jobs, Burst
- Working knowledge of Unity and C#
- No scripts run and no network use
What are the safety notes for scripts and network access?
According to the skill's metadata, it runs no scripts and uses no network access. It is guidance only, so it cannot run your code or change your project on its own. Any code it suggests is yours to review, compile and test in your own project.
What are the limits and tips for getting good results?
The guidance is general. The files contain no tested code samples and no version details, so verify every suggestion against your Unity version and the current DOTS documentation. The skill also advises against over-architecting: ECS adds complexity that small projects do not need.
For best results, give the agent your real code and your performance symptoms, such as entity counts and where the CPU time goes.
- Verify all code against your Unity and DOTS package versions
- Share real code and profiler findings in your request
- Do not use ECS for a simple game that does not need it
What people use it for
- Converting a MonoBehaviour-based spawner or enemy controller to ISystem-based ECS.
- Simulating thousands of units, projectiles or particles when CPU time is the bottleneck.
- Checking existing system code for managed types that would break Burst compilation.
- Deciding when to batch structural changes with an entity command buffer.
- Reviewing native collections for missing disposal.
Frequently asked questions
How do I install the unity-ecs-patterns skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder. You can also upload it in the Claude apps under Settings → Capabilities → Skills.
Does the unity-ecs-patterns skill run scripts or use the internet?
No. The skill's metadata says it runs no scripts and uses no network access. It only shapes the agent's advice and code suggestions.
What do I need to use the unity-ecs-patterns skill?
You need Unity with the DOTS packages Entities, Jobs and Burst, plus working knowledge of Unity and C#. The files do not specify exact versions.
Is the unity-ecs-patterns skill free?
The skill is published under the MIT licence. This page does not list prices, so check the source repository for licence terms.
Can I use this skill for Godot or Unreal projects?
No. The content is specific to Unity DOTS, so it is not suited to Godot or Unreal.
Is the code from this skill tested?
The files show no tested code samples or version details. Treat its guidance as general and verify all code in your own project before relying on it.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits Unity developers moving performance-critical logic to DOTS, or teams hitting CPU limits with thousands of entities. Beginners building a simple game, and anyone who needs verified, version-specific answers, should look elsewhere or rely on Unity's official DOTS documentation.
Download the skill