unity-dotween-design

Codify DOTween best practices for safe lifecycle management in Unity.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/krl76/MP-Study-Projects --skill unity-dotween-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-dotween-design
Source: https://github.com/krl76/MP-Study-Projects/tree/main/Practice1/.codex/skills/unity-skills/skills/dotween-design
Command: npx skills add https://github.com/krl76/MP-Study-Projects --skill unity-dotween-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Design Rules Skill codifies best practices and guardrails for using DOTween in Unity, helping teams avoid missing-target NREs, tween leaks, Safe Mode pitfalls, and lifecycle issues across Init, Module usage, and teardown.

Core Features & Use Cases

  • Establishes a canonical bootstrap and module-loading sequence to ensure stable tween lifecycles.
  • Documents lifecycle behaviors (Init, AutoKill, SetLink, SetAutoKill, Safe Mode) and recommended patterns for replayable and deterministic scenarios.
  • Provides guidelines for safe teardown with DOTween.Clear and per-scene lifecycle management.

Quick Start

Load this design rules guide before writing any DOTween code to ensure correct, safe usage.

Frequently Asked Questions about unity-dotween-design

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

FAQPage Schema
How do I prevent missing-target NREs and tween leaks when using DOTween in Unity?

To prevent missing-target NREs and tween leaks in DOTween, follow codified lifecycle best practices for initialization, module usage, and teardown, ensuring stable tween behavior across scenes.

What is the correct way to manage DOTween lifecycle and Safe Mode during scene teardown?

Managing DOTween lifecycle during teardown requires applying DOTween.Clear and per-scene management rules, which safely handle AutoKill, SetLink, and SetAutoKill behaviors to avoid Safe Mode pitfalls.

How do I initialize DOTween safely for replayable and deterministic Unity scenarios?

Initialize DOTween safely by establishing a canonical bootstrap and module-loading sequence, ensuring deterministic tween lifecycles and stable replayable scenarios across Unity scene patterns.

Does DOTween Safe Mode prevent lifecycle issues across different scene loading patterns?

DOTween Safe Mode helps mitigate lifecycle issues, but avoiding pitfalls across scene patterns requires applying specific guardrails for SetLink, SetAutoKill, and teardown to ensure stable behavior.

What are the limitations of relying on DOTween AutoKill without explicit teardown rules?

Relying solely on DOTween AutoKill risks tween leaks and missing-target NREs, so explicit teardown rules and per-scene lifecycle management are necessary to maintain stable behavior.