More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Unity ECS and DOTS Patterns

    1

    Production patterns for Unity ECS: when to adopt it, archetypes and components, Burst jobs, EntityCommandBuffer discipline, and a ship checklist.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Unity ECS and DOTS Patterns

    Unity ECS and DOTS Patterns

    Example session with this skill installed

    Our prototype has 6,000 flocking birds as MonoBehaviours and runs at 19 fps. The profiler blames per-object Update calls and neighbor searches. Should this be ECS, and if so, what does the design look like?

    • Read your context and instructions
    • Compiled the unity ecs

    Verdict: adopt ECS for the flock — hybrid overall. 6,000 similar entities with per-frame logic and a cache-bound profile is the textbook adopt signal. The birds convert; the player, camera, and UI stay GameObjects.

    Components: LocalTransform (built in), Velocity (float3, blittable), FlockSettings (shared tuning: cohesion / separation / alignment weights), BoidTag (marker so generic movers skip birds), and an enableable Alive component for death state. Neighbor data is deliberately not a component — it's rebuilt per frame into a transient spatial hash and discarded.

    Systems, in order: BuildSpatialHashJob (parallel, writes the hash) → SteeringJob (parallel, reads hash, writes Velocity — chained by dependency, never completed early) → the movement system → BirdDeathSystem. Dead birds are disabled and recycled by the spawner instead of destroyed, so there's no per-frame structural churn; the death system's ECB is the frame's single playback point.

    Bridge: one small system copies the player's position into a singleton component each frame — three floats across the boundary, nothing more.

    Checks before calling it done: archetype count holds at two; chunks near-full in the Entity Debugger; no playback stalls; the native hash map is disposed every frame. And one honest caveat from the decision table: if the converted build is still slow, the suspect is the neighbor-search radius — an algorithm problem to optimize in place, not a reason to add more ECS.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Unity's Entities package can turn a choking simulation into a smooth one — or turn a simple game into months of self-inflicted complexity. This skill is the judgment layer: it starts with whether you need ECS at all, then gives you the patterns that survive contact with real projects.

    It opens with an adopt / hybrid / stay decision table driven by profiler signals, because ECS earns its keep at thousands of similar entities with cache-bound profiles — and is pure overhead for a few hundred objects or one heavy algorithm. Then it builds the mental model (entities as numbers, components as blittable data contracts, archetypes and chunks as the memory layout everything follows from), and walks the code shapes with annotated examples: a Burst-compiled ISystem movement loop, component design rules, IJobEntity parallel jobs with correct scheduling discipline, and EntityCommandBuffer structural changes with deliberate playback points. Aspects, Entity Debugger profiling, and a MonoBehaviour-to-ECS conversion path (profile first, lift the data, keep a frame of parity) are all covered.

    A full worked example designs a 6,000-bird flocking system end to end — components, job chain, ECB strategy, and the GameObject bridge — and the skill closes with the failure modes that burn the most time: archetype splintering from tag-component state machines, premature Complete() calls serializing the frame, safety-system exceptions misread as bugs, and native-collection leaks. A pre-ship checklist turns all of it into a gate you can run before a build goes out.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Game Development.

    • API shapes follow current Entities releases; older Entities versions (pre-1.0 ComponentSystem-era code) differ substantially and are not covered.
    • It teaches architecture and patterns, not rendering — pair it with your render pipeline's own instancing guidance for draw-call questions.
    • Performance outcomes depend on your data and hardware; the skill gives you the decision framework and the checks, not a guaranteed frame rate.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Permissions

    No special permissions declared or detected

    Listed24 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    Production patterns for Unity ECS: when to adopt it, archetypes and components, Burst jobs, EntityCommandBuffer discipline, and a ship checklist.

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use Unity ECS and DOTS Patterns on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.

    New in Game Development