What problem does it solve?
Burst compilation and runtime can fail or silently degrade when DOTS systems jobs accidentally use managed types, reflection, logging, or unsafe patterns inside Burst-compiled code paths.
Core Features & Use Cases
- Burst-safe code rules for DOTS/Hybrid: Enforces hard constraints for what may appear inside
[BurstCompile] methods and jobs.
- Pre-verifier diagnostic checklist: Provides a concrete checklist to validate Burst compatibility before handing off to verification.
- Prevents common Burst failure modes: Targets frequent issues like BC1015 static evaluation failures, managed wrapper usage (e.g.,
Mathf/Vector3), and forbidden exceptions/debugging.
Quick Start
Use the burst-safety skill pack when triage classifies the task as domain=DOTS|Hybrid, then apply its rules to every touched system or job before signaling the verifier.