Unity Component Skills

Overview

BATCH-FIRST: Use *_batch skills when operating on 2+ objects to reduce API calls from N to 1.

Common Mistakes

DO NOT (common hallucinations):

• component_create / component_get do not exist → use component_add (add) and component_get_properties (read)
• component_find does not exist → use component_list to list components on an object
• componentType is case-sensitive — Rigidbody not rigidbody, BoxCollider not boxcollider
• Custom scripts need exact class name; if namespaced, use Namespace.ClassName

Routing:

• To create a C# component script → use script module's script_create first, then component_add
• To set multiple properties at once → use component_set_property_batch
• To enable/disable a component → component_set_enabled (not component_set_property)

Object Targeting: All single-object skills accept name (string), instanceId (int, preferred), and path (string, hierarchy path). Provide at least one.

Skills Overview

Other Skills (no batch):

• component_list - List all components on an object
• component_get_properties - Get component property values
• component_set_enabled - Enable/disable a component (Behaviour, Renderer, Collider)
• component_copy - Copy a component from one object to another

Single-Object Skills

component_add

Add a component to a GameObject.

*At least one identifier required

Returns: {success, gameObject, instanceId, component, fullTypeName}

component_remove

Remove a component from a GameObject.

Returns: {success, gameObject, removed}

component_list

List all components on a GameObject.

Returns: {gameObject, instanceId, path, componentCount, components: [{type, fullType, enabled}]}

component_set_property

Set a component property value.

Provide one of: value (basic types), referencePath/referenceName (scene objects), or assetPath (project assets).

value type examples: See ../../recipes/component/component_set_property.md for value format details and C# template.

Returns: {success, gameObject, component, property, valueSet, valueType}

component_get_properties

Get all properties of a component.

Returns: {gameObject, component, fullTypeName, properties: [{name, type, value, canWrite}], fields: [{name, type, value, isSerializable}]}

Batch Skills

component_add_batch

Add components to multiple objects.

Returns: {success, totalItems, successCount, failCount, results: [{success, gameObject, componentType, added}]}

See ../../recipes/component/component_add_batch.md for C# template.

component_remove_batch

Remove components from multiple objects.

Returns: {success, totalItems, successCount, failCount, results: [{success, gameObject, componentType, removed}]}

See ../../recipes/component/component_remove_batch.md for C# template.

component_set_property_batch

Set properties on multiple objects.

Returns: {success, totalItems, successCount, failCount, results: [{success, gameObject, componentType, property, oldValue, newValue}]}

See ../../recipes/component/component_set_property_batch.md for C# template.

Common Component Types

Physics

Rendering

Audio

UI

Example: Efficient Physics Setup

See ../../recipes/component/README.md for all component recipes.

Best Practices

1. Add colliders before Rigidbody for physics
2. Use component_list to verify additions
3. Check property names with component_get_properties first
4. Some properties are read-only (will fail to set)
5. Use full type names for custom scripts (e.g., "MyNamespace.MyScript")

Additional Skills

component_copy

Copy a component from one GameObject to another.

*At least one source identifier and one target identifier required

Returns: { success, source, target, componentType }

component_set_enabled

Enable or disable a component (Behaviour, Renderer, Collider, etc.).

*At least one identifier required

Returns: { success, gameObject, componentType, enabled }

Recipe path rule: ../../recipes/component/<command>.md