← ClaudeAtlas

unity-yaml-formatlisted

Inspect, explain, diff, and carefully edit Unity text-serialized files such as .unity, .prefab, .asset, and related YAML-based project files. Use when mapping class IDs and fileIDs, tracing object references, reviewing merge conflicts, or making minimal safe edits to existing UnityYAML documents.
sator-imaging/suggest-skills · ★ 0 · Code & Development · score 70
Install: claude install-skill sator-imaging/suggest-skills
# Unity YAML Format Use this skill when working directly with Unity text-serialized files rather than higher-level C# or Editor APIs. ## First Pass - Read [references/source-summary.md](references/source-summary.md). - Identify the file type and intent: inspect, explain, diff, repair, or minimally edit. - If the task involves object or component type numbers, read [references/class-id-reference.md](references/class-id-reference.md). - If the task involves `fileID`, `guid`, `type`, script links, or external asset links, read [references/reference-semantics.md](references/reference-semantics.md). - If the task involves hand-editing, read [references/examples.md](references/examples.md) before changing anything. ## Working Rules - Treat UnityYAML as a Unity-specific serialization format, not as generic full YAML. - Prefer the Unity Editor for broad structural changes; use manual edits only for narrow, justified repairs to existing text-serialized files. - Keep edits as small and local as possible. - Preserve existing indentation, document order, anchors, `fileID` links, and scalar style unless the task requires otherwise. - Explain reference relationships explicitly when reviewing a file. ## Gotchas - UnityYAML is a custom subset and does not support the full YAML specification. - Unity docs warn against externally producing or editing UnityYAML files; only make manual edits when the narrow reference or scalar repair is justified. - Comments are not supported by UnityYAML