What problem does it solve? Unity loses and corrupts asset data silently, without any console error: renamed scripts break prefab references, changed code defaults never reach serialized values, Play mode edits vanish, and scene-instance overrides block prefab changes. This Skill provides the rules and verification workflow to avoid these hidden data-loss traps when modifying Unity assets. ## Core Features & Use Cases - Rename and GUID Safety: Enforces keeping .meta files with their assets, matching .cs filenames to MonoBehaviour class names, and using [FormerlySerializedAs] when renaming serialized fields. - Prefab and Override Discipline: Directs edits to the prefab rather than scene instances, and checks for stale overrides that silently block prefab changes. - Play Mode and Code-Driven Edit Rules: Warns about Play mode changes being lost (except ScriptableObjects, which persist to disk), and restricts code-driven asset edits that bypass undo. - Use Case: Before renaming a MonoBehaviour or changing a balance value in a Unity RTS project, consult this Skill to verify actual serialized values on disk, confirm Force Text serialization, and avoid silently breaking prefab references. ## Quick Start Before modifying any Unity prefab, scene, material, or ScriptableObject, ask the assistant to apply the unity-asset-safety rules and verify the actual serialized values from disk after the edit.
