unity-yooasset-design

Define YooAsset v2.3.18 design constraints for initialization, asset loading, and patch flows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

YooAsset integrations often suffer from hallucinated APIs, misapplied playmode mappings, and leaks due to improper handle lifecycles. This design guide anchors implementation to the official v2.3.18 sources, helping developers stay aligned with the canonical surface and avoid common mistakes.

Core Features & Use Cases

  • Official-aligned design: References and enforces mappings between InitializeParameters subclasses and EPlayMode, ensuring correct patch and load flows.
  • Safety-first lifecycle: Promotes proper Release/Dispose semantics for all handles to prevent resource leaks.
  • Consistent cross-cutting rules: Provides guardrails for FileSystemParameters, downloader callbacks, and patch flow order to minimize integration bugs.
  • Use Case: A new project wires ResourcePackage initialization, asset loading, and patch updates without encountering hallucinated APIs or misconfigurations.

Quick Start

Review these rules and apply them before implementing YooAsset integrations to prevent hallucinated APIs and misconfigurations.

Frequently Asked Questions about unity-yooasset-design

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

FAQPage Schema
How do I prevent YooAsset hallucinated APIs during Unity integration?

To prevent YooAsset hallucinated APIs, apply design constraints that align usage with official v2.3.18 docs across initialization, PlayMode parameter mapping, and asset loading. This ensures correct API surface usage and avoids risky patterns causing leaks.

What is the correct way to map InitializeParameters subclasses to EPlayMode in YooAsset?

Mapping InitializeParameters subclasses to EPlayMode requires enforcing official v2.3.18 alignments to ensure correct patch and load flows. Following these design guidelines prevents misapplied playmode mappings and integration bugs.

How do I manage YooAsset handle lifecycles to avoid resource leaks?

Managing YooAsset handle lifecycles requires following safety-first Release and Dispose semantics for all handles. Applying these design constraints prevents resource leaks and ensures safe memory management during asset loading.

How do I configure YooAsset patch flow and FileSystemParameters safely?

Configuring YooAsset patch flow and FileSystemParameters safely involves applying consistent cross-cutting rules for downloader callbacks and patch flow order. This minimizes integration bugs and ensures reliable package updates.

Why does my YooAsset integration fail with misconfigurations during patch updates?

YooAsset integration fails with misconfigurations when design constraints for patch flow order and FileSystemParameters are not applied. Enforcing official v2.3.18 mappings and safe handle lifecycles resolves these common integration mistakes.