unity-dotween-design

Codify DOTween usage guidelines for Unity projects and teams.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/YiDuandtdt/Bone-Throne --skill unity-dotween-design-yiduandtdt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-dotween-design
Source: https://github.com/YiDuandtdt/Bone-Throne/tree/main/.agents/skills/unity-skills/skills/dotween-design
Command: npx skills add https://github.com/YiDuandtdt/Bone-Throne --skill unity-dotween-design-yiduandtdt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a canonical design rule set for DOTween usage in Unity to prevent missing-target NREs, tween leaks, lifecycle confusion, and unsafe module interactions that complicate maintenance.

Core Features & Use Cases

  • Codifies init behavior, module generation, Safe Mode, capacity planning, and target lifetimes to ensure consistent tween behavior.
  • Guides cross-team consistency for sequences, parallelism (Append/Join), and replayability through SetAutoKill, SetLink, SetTarget and related lifecycles.
  • Use case: a team introduces a standard DOTween design to reduce bug rates and accelerate onboarding.

Quick Start

Follow these rules to bootstrap DOTween usage in your project.

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 NullReferenceExceptions in Unity DOTween?

Prevent missing-target NREs in Unity DOTween by codifying explicit target lifecycles and using SetLink to bind tweens to target destruction, ensuring predictable tween behavior and automatically killing tweens when targets are destroyed.

What is the best way to manage DOTween sequence composition and lifecycles in Unity?

Manage DOTween sequence composition by standardizing Append and Join usage for parallelism, and applying SetAutoKill with lifecycle flags. This prevents leaks and ensures maintainable, replayable tween behavior across scenes and builds.

Why does DOTween cause memory leaks when switching scenes in Unity?

DOTween causes memory leaks during scene switches due to unsafe lifecycles and unmanaged tween persistence. Establishing canonical capacity planning, explicit module generation, and Safe Mode guidelines prevents these leaks and ensures consistent behavior.

How do I set up DOTween initialization and capacity planning for a scalable Unity project?

Set up scalable DOTween initialization by codifying init behavior, Safe Mode, and capacity planning rules. This ensures consistent tween behavior across teams, reduces bug rates, and accelerates onboarding for large Unity projects.

Can I use standard DOTween guidelines for cross-team consistency in Unity?

Yes, you can use standard DOTween guidelines for cross-team consistency by specifying explicit defaults, lifecycle flags, and naming conventions. This ensures predictable, maintainable tween behavior across scenes and builds for the entire team.