unity-data-oriented-design-skills

Architecture guide for High Performance Unity Game Development (Using data-oriented design) by Nitzan Wilnai (Manning). Use this skill whenever working on a Unity project that follows the book's DOD architecture, or whenever the user asks to: generate DOD-compliant Unity code, scaffold a new game feature in DOD style, explain DOD concepts using the book's terminology, review code for DOD violations, or create any of the core architectural classes (Balance, GameData, Logic, Board, Game, AssetManager, GameDataIO, MetaDataIO, GUIRef, Singleton). Also trigger when the user mentions "balance data", "game data", "static logic functions", "data-in/transformation/data-out", "tooltime parsing", "ScriptableObject balance", "avoiding dictionaries", "indices at tool time", "dynamic object pool", "branchless", "branch prediction", "Unity null checks", "Unity DOTS", "Burst", "Jobs", "ECS", "TransformAccessArray", or any concept from the book.

Skill for communicating with Unity Editor via unity-agent-cli. Covers compilation checking, executing static methods, building UI prefabs, assigning assets, taking automated screenshots, verifying menus visually, and fixing errors autonomously. Use this skill whenever working on a Unity project that has the unity-agent-bridge package installed.

Use when building, modifying, or reviewing Unity UI screens and prefabs. Covers: text sizing for numbers, image stretching, layout pitfalls, safe area handling, missing sprites, ContentSizeFitter issues, and visual verification. Trigger when you see UI builder code, prefab construction, Canvas layout, or after taking screenshots that reveal visual bugs.