skills.rest
krl76
krl76COMMUNITY
Explore all skills by this author →
GitHub

unity-addressables-design

Codify Unity Addressables design rules across versions 1.22.3 and 2.9.1.

Updated Mar 30, 2026
Search Tags:#architecture#unity#design-principles#addressables#version-migration#api-deprecation
One-click install
npx skills add https://github.com/krl76/MP-Study-Projects --skill unity-addressables-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unity-addressables-design
Source: https://github.com/krl76/MP-Study-Projects/tree/main/Practice1/.codex/skills/unity-skills/skills/addressables-design
Command: npx skills add https://github.com/krl76/MP-Study-Projects --skill unity-addressables-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unity Addressables evolve between 1.22.3 and 2.9.1; this Skill codifies design rules to prevent deprecated APIs, leaks, and incorrect lifecycle handling that hinder stable builds and live-ops.

Core Features & Use Cases

  • Establishes version-aware guidance for InitializeAsync, LoadAssetAsync, and LoadSceneAsync usage to avoid breaking changes.
  • Documents catalog update, bundle cache, and asset reference lifecycles to prevent leaks and mis-releases in complex projects.
  • Provides migration guidance for projects porting between Unity versions, including deprecations and new SceneReleaseMode behavior.

Quick Start

Review the two version contexts and follow the canonical patch-flow for catalog updates before implementing any Addressables calls.

Frequently Asked Questions about unity-addressables-design

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

FAQPage Schema
How do I migrate Unity Addressables from 1.22.3 to 2.9.1 without breaking deprecated APIs?▼

To migrate Unity Addressables from 1.22.3 to 2.9.1, apply codified design rules for deprecated APIs, new SceneReleaseMode behavior, and lifecycle handling to ensure stable builds and live-ops.

What causes memory leaks when using Unity Addressables LoadAssetAsync and LoadSceneAsync?▼

Memory leaks in Unity Addressables LoadAssetAsync and LoadSceneAsync occur due to incorrect lifecycle handling and mis-releases; codifying asset reference lifecycles and bundle cache rules prevents these leaks.

What is the correct patch-flow for Unity Addressables UpdateCatalogs during live-ops?▼

The correct patch-flow for Unity Addressables UpdateCatalogs involves reviewing version-specific contexts and applying canonical catalog update rules before implementing any Addressables calls to prevent runtime errors.

Does Unity Addressables 2.9.1 change the behavior of InitializeAsync and AssetReference usage?▼

Yes, Unity Addressables 2.9.1 introduces new SceneReleaseMode behavior and alters InitializeAsync and AssetReference usage, requiring version-aware design rules to avoid deprecated APIs and breaking changes.

When should I apply version-aware design rules for Unity Addressables architecture?▼

You should apply version-aware design rules for Unity Addressables architecture during porting, migration, and architecture decisions to prevent deprecated APIs, leaks, and incorrect lifecycle handling.

Related Skills

Explore More Software Engineering Skills→
RayzerrekRayzerrek

unity-addressables-design

Detect and correct Unity Addressables API and lifecycle errors.

Community
Advanced
YiDuandtdtYiDuandtdt

unity-addressables-design

Provide version-aware design rules for Unity Addressables migrations across 1.22.3 and 2.9.1.

Community
Advanced
dyCuong03dyCuong03
6

unity-addressables-design

Implement Addressables 1.22.3 and 2.9.1 APIs with correct handle release and catalog sequencing.

Community
Advanced
seydakaratekeliseydakaratekeli

maui-current-apis

Detect deprecated .NET MAUI APIs in project source code.

Community
Advanced