wave4-burst-compilation-contract

Apply BurstCompile attributes to Unity DOTS ISystem methods and job struct Execute paths.

6|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/dyCuong03/unity-agent-team --skill wave4-burst-compilation-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wave4-burst-compilation-contract
Source: https://github.com/dyCuong03/unity-agent-team/tree/main/.claude/skills/unity-dots/wave4-burst-compilation-contract
Command: npx skills add https://github.com/dyCuong03/unity-agent-team --skill wave4-burst-compilation-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents hidden performance regressions by ensuring Unity DOTS code actually compiles down to Burst native code where you expect it, rather than silently falling back to non-Burst execution.

Core Features & Use Cases

  • BurstCompile everywhere it matters: Applies [BurstCompile] to both ISystem methods and job struct Execute() paths to cover scheduling and execution.
  • Safe opt-out guidance: Clarifies when to avoid Burst (managed APIs, SystemBase.OnUpdate) and how to isolate managed calls with [BurstDiscard].
  • Reviewable contract: Provides a senior checklist so teams can audit missing Burst attributes and reduce compile-time surprises.

Quick Start

Ask an AI to apply the Burst Compilation Contract to your DOTS ISystem and job structs, ensuring every relevant method and Execute() is correctly annotated to achieve consistent Burst compilation.

Frequently Asked Questions about wave4-burst-compilation-contract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I guarantee Burst compilation for Unity DOTS ISystem methods?

Guarantee Burst compilation for Unity DOTS ISystem methods by applying the [BurstCompile] attribute to relevant methods and job struct Execute paths. This audits scheduling workflows to prevent silent non-Burst fallbacks.

Why does my Unity DOTS job struct silently fall back to non-Burst execution?

Unity DOTS job structs silently fall back to non-Burst execution when missing [BurstCompile] attributes or using managed APIs. Applying Burst attributes to Execute paths and avoiding SystemBase OnUpdate prevents these hidden performance regressions.

How do I apply BurstCompile correctly to IJobEntity job structs in Unity DOTS?

Apply [BurstCompile] correctly to IJobEntity job structs by annotating the Execute path and related ISystem methods. This covers scheduling and execution workflows, enforcing audit rules to ensure consistent Burst-native compilation across the codebase.

When should I avoid using Burst compilation in Unity DOTS systems?

Avoid using Burst compilation in Unity DOTS systems when relying on managed APIs or SystemBase OnUpdate. Isolate necessary managed calls using [BurstDiscard] to safely opt out without breaking the native execution contract.

Does using SystemBase OnUpdate prevent Burst compilation in Unity DOTS?

Using SystemBase OnUpdate prevents Burst compilation in Unity DOTS because it relies on managed APIs. Transitioning to ISystem implementations and applying [BurstCompile] ensures your scheduling and execution workflows compile down to native code.

What is the best way to audit Unity DOTS code for missing Burst attributes?

The best way to audit Unity DOTS code for missing Burst attributes is using a senior checklist that targets ISystem implementations and job structs. This reviewable contract enforces audit rules to reduce compile-time surprises and catch missing annotations.