What problem does it solve? PrimeTween's API differs significantly from DOTween and other tween libraries—its Tween handles are non-reusable structs, sequences use Chain/Group/Insert instead of Append/Join, and configuration happens at creation time rather than through fluent setters. This Skill prevents lifecycle bugs, allocation issues, and incorrect API assumptions when writing or reviewing PrimeTween animation code. ## Core Features & Use Cases - Design Rule Enforcement: Eight source-anchored rules covering factory tweens, dead handle reuse, sequence composition, cycles, callbacks, cancellation, and async waiting, each linked to exact PrimeTween 1.4.6 source locations. - Lifecycle Diagnosis: Guidance on destroyed-target detection, PrimeTweenConfig warning controls, and when to stop tweens on component disable instead of expecting a DOTween-style SetLink API. - Allocation-Aware Patterns: Direction on zero-allocation OnComplete<T> callback overloads and when to prefer Sequence over await/coroutine waiting to avoid state machine allocations. - Use Case: When reviewing a Unity script that calls Tween.Position and then tries to replay the same handle, this Skill flags that completed handles are dead and a new tween must be created. ## Quick Start Review my PrimeTween animation code and check it against the PrimeTween 1.4.6 design rules for handle reuse, sequence composition, and callback safety.
