unity-unitask-design

Prevent double-await crashes in UniTask by enforcing strict design rules that restrict struct reuse and ensure triggers are awaited exactly once. This Skill provides guardrails to audit async APIs and eliminate runtime pitfalls before merging code.

The best way to manage cancellation propagation in UniTask is to follow documented patterns that safely route cancellation tokens through async triggers and interop points. This Skill specifies constraints to prevent forgotten Forget calls and improper timing.

Avoid resource leaks and forgotten Forget calls in Unity async programming by applying formal design constraints to all UniTask methods. This Skill serves as a code review reference to catch unsafe interop and ensure proper resource management.

Yes, you can use WhenAll and ToUniTask interop patterns safely in Unity projects by applying recommended design rules. This Skill documents safe interop constraints to prevent runtime bugs and ensure zero-allocation async behavior.

UniTask causes subtle bugs in Unity because its zero-allocation struct design allows dangerous practices like double-awaits and forgotten Forget calls. This Skill provides the necessary guardrails to prevent improper cancellation and unsafe interop.

UniTask limitations in Unity include susceptibility to double-await crashes, forgotten Forget calls, and resource leaks if not properly constrained. This Skill defines the exact practices to avoid these edge cases and maintain safe async interop.