Legends-Of-Heroes: Skill for Codex

AI Bridge Unity Skill

Invocation

Run commands from the Unity project root.

CLI Path: ./.aibridge/cli/AIBridgeCLI.exe

Example Alias: $CLI is a shorthand for the platform-appropriate AIBridge CLI invocation. Examples use $CLI for consistency; replace it with the matching invocation form when running commands directly.

Invocation Forms:

• Windows executable: ./.aibridge/cli/AIBridgeCLI.exe <command> [action] [options]
• macOS/Linux DLL: dotnet ./.aibridge/cli/AIBridgeCLI.dll <command> [action] [options]
• PowerShell call operator: & "./.aibridge/cli/AIBridgeCLI.exe" <command> [action] [options]

Most Unity-side commands require an action such as asset search or inspector set_property. CLI-only commands and helpers can differ: focus has no action, dialog uses status/click/wait, and multi uses --cmd or --stdin. Use --help or the generated command reference for the exact form.

Global Options:

• --timeout <ms> - Timeout (default: 5000)
• --on-dialog <mode> - When a Unity command is blocked by a modal dialog, optionally wait or click: none, wait, cancel, save, discard, ok, yes, no, delete, replace
• --raw / --pretty - JSON output (default: raw)
• --json <json> / --stdin - Complex parameters
• --help - Show help

Cache Directory: .aibridge/ (Editor commands/results/screenshots and Runtime targets under .aibridge/runtime/targets/)

Dialog Output Rule: dialog status omits blockedByDialog and dialogs when no blocking Unity modal dialog is detected. Missing fields mean no dialog.

Operating Rules

• Use compile unity for Unity validation. compile dotnet is an explicit extra solution-build check, not a fallback.
• For Unity assets, prefer asset search/find --format paths; use host file reads for file contents, and asset read_text only when host reads are unavailable.
• Resource edit order: use inspector set_property/set_properties for single or batched fields, aibridge-prefab-patch for complex Prefab structure edits it supports, Unity Editor scripts for high-level generated assets, and unity-yaml-editing only for unsupported serialized-file structure work.
• For scene objects, Prefabs, and serialized Unity assets, discover targets with inspector get_components/get_properties/find_property, then write with AIBridge/Unity APIs when possible; avoid raw YAML unless no supported API can express the operation.
• Direct YAML edits are acceptable only after loading unity-yaml-editing, including unsupported Scene/Prefab/ScriptableObjectTable/custom .asset operations. Preserve m_Script, fileID/guid/type references, YAML indentation, and paired .meta GUIDs; validate afterward with import, targeted inspection, compile unity, and Error logs.
• For prefab asset edits, use assetPath + objectPath + componentName or componentIndex; componentInstanceId is scene-only.
• For complex prefab asset edits, use the aibridge-prefab-patch skill and prefer prefab patch --ops <file> with dry-run first.
• In PowerShell, avoid inline complex --json; build JSON in a variable, escape embedded quotes for native EXE argument passing, and pass command parameters directly, especially inspector set_properties --values $values.
• focus is Windows CLI-only. dialog is CLI-only, uses Windows window APIs or macOS Accessibility permission, and omits dialog fields when no modal dialog is detected. screenshot game and screenshot gif require Play Mode; screenshot scene_view works in Edit mode when a Scene view is open.
• input requires Play Mode and an active EventSystem; use it with gameview, screenshot, and get_logs for UI interaction checks.
• runtime is CLI-only and talks to AIBridgeRuntime inside a Player or Play Mode target. Use runtime list_targets first, then target latest or a specific target id.
• Code Index is a separate optional Skill. Use aibridge-code-index only when that Skill is installed and project rules say Code Index is enabled; otherwise use rg, file reads, and regular AIBridge commands.