Unity SO-Prefab Manager

This skill enforces a strictly modular "Bridge" pattern between Data and Logic.

Core Features

1. The Bridge Pattern: Synchronizing SO data to local instance variables.
2. DataEntity Base: A generic base class (DataEntity<T>) for all data-driven objects.
3. API-First Creation: Using Unity tools to ensure GUID integrity.

Core Files (assets/code/)

• DataEntity.cs.txt: The generic base class for all data-driven objects.
• BridgeInitializer.cs.txt: Example of value-copying in Awake.

[Header("Data Reference")]
[SerializeField] private RobotSO data;

[Header("Runtime State")]
private float currentHealth;

private void Awake () {
    if ( data == null ) {
        Debug.LogError( $"[System] Fail: Missing SO data on {gameObject.name}" );
        return;
    }
    // Initialize independent state
    currentHealth = data.MaxHealth;
    
    Debug.Log( $"[{data.name}] Success: Initialized instance | Health: {currentHealth}" );
}

Advanced Usage

1. File Creation: API-First vs. YAML Power-Mode

Standard (1-10 Files) - Use Unity API

For most tasks, use mcp_unityMCP_manage_scriptable_object. This is the healthiest method as it ensures GUID integrity and immediate .meta file availability.

• Workflow: Call manage_scriptable_object -> Apply Patches.

Performance (10+ Files) - Use YAML Generation

For massive data dumps (e.g., importing 50 items), bypass the API latency by writing files directly.

• Workflow:
  1. Create a YAML template based on an existing .asset file.
  2. Write .asset files directly to Assets/Data/ via write_to_file.
  3. Call mcp_unityMCP_refresh_unity(scope="assets") to force Unity to generate .meta files.

2. Surgical YAML (Deep Debugging)

Use direct file reading/parsing for "Deep Audits" that the API can't quickly handle:

• GUID Verification: Search for a specific m_Script: {fileID: ..., guid: ...} in prefabs to find which scripts are actually attached.
• Reference Repair: Use grep_search and replace_file_content project-wide to swap broken GUIDs without opening the Editor for every file.

Reference Material

• See references/bridge-pattern.md for detailed implementation details and troubleshooting.
• See references/naming-conventions.md for the project-standard folder structure.
• See references/yaml-templates.md for standard Unity YAML boilerplate.