unity-foundations
Unity 6 core concepts and architecture guide. Use when working with GameObjects, Components, Transforms, Scenes, Prefabs, ScriptableObjects, or Unity project structure. Covers the entity-component architecture, object hierarchy, tags, layers, and project conventions. Based on Unity 6.3 LTS documentation.
Nice-Wolf-Studio · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Nice-Wolf-Studio/unity-claude-skills --skill unity-foundationsAbout this skill
name: unity-foundations description: > Unity 6 core concepts and architecture guide. Use when working with GameObjects, Components, Transforms, Scenes, Prefabs, ScriptableObjects, or Unity project structure. Covers the entity-component architecture, object hierarchy, tags, layers, and project conventions. Based on Unity 6.3 LTS documentation.
Unity Foundations
Core Concepts
GameObjects
GameObjects are the fundamental building blocks in Unity. Every object in a scene -- characters, props, scenery, cameras, lights -- is a GameObject. GameObjects are containers: they cannot function alone and require Components to gain functionality. Every GameObject automatically includes a Transform component that cannot be removed.
Components
Components are the functional pieces of every GameObject. Unity uses a composition-over-inheritance architecture: you build behavior by attaching multiple components to a GameObject rather than inheriting from deep class hierarchies. Each GameObject must have exactly one Transform component. Additional components (Rigidbody, Collider, MeshRenderer, custom MonoBehaviours) define what the object does.
Constraints from the docs:
- Components must reside in the same project as their target GameObject
- Components cannot be sourced from separate projects, unattached scripts, or uninstalled packages
Transforms
The Transform component stores position, rotation, and scale -- each relative to the parent (local coordinates) or to the world origin (world coordinates). Key points from the docs:
- Child Transforms display values relative to their parent
- Root GameObjects (no parent) show world coordinates
- The physics engine assumes 1 unit = 1 meter
- Set parent location to
(0,0,0)before adding children so local coords match global coords - Avoid adjusting Transform Scale at runtime; model assets at real-life scale instead. Non-uniform scaling causes issues with Colliders, Lights, and Audio Sources
Scenes
Scenes are assets that contain all or part of a game or application. A default new scene includes a Camera and a directional Light. Projects can use a single scene or multiple scenes (e.g., one per level). Scene Templates serve as blueprints for creating new scenes.
Prefabs
Prefabs are reusable asset templates that store a complete GameObject configuration (all components, property values, and child GameObjects). Key features:
- Nested Prefabs: Include prefab instances within other prefabs
- Prefab Variants: Create predefined variations that maintain a base prefab relationship
- Overrides: Modify components/data on specific instances without affecting the template
- Unpacking: Convert prefab instances back to standalone GameObjects
ScriptableObjects
ScriptableObject is a serializable Unity type derived from UnityEngine.Object that serves as a data container independent of GameObjects. Unlike MonoBehaviours, ScriptableObjects exist as project-level .asset files. Primary use cases:
- Shared data containers (reduces memory by referencing one asset instead of duplicating data across prefabs)
- Editor tool foundations (EditorTool, EditorWindow derive from ScriptableObject)
- Runtime configuration storage
Critical: Unity does not automatically save changes to a ScriptableObject made via script in Edit mode. You must call EditorUtility.SetDirty() after modifications.
Tags
Tags are reference identifiers assigned to GameObjects for scripting purposes. Each GameObject can have only one tag, but multiple GameObjects can share the same tag. Built-in tags: Untagged, Respawn, Finish, EditorOnly, MainCamera, Player, GameController.
MainCamera: The Editor caches these;Camera.mainreturns the first valid resultEditorOnly: GameObjects tagged this way are destroyed during builds- Tag names cannot be renamed once created
Layers
Layers separate GameObjects for selective processing including camera rendering, lighting, physics collisions, and custom code logic. Unity supports up to 32 layers. LayerMasks define which layers an API call interacts with.
Common Patterns
Creating and Accessing Components
using UnityEngine;
public class ComponentAccess : MonoBehaviour
{
void Start()
{
// Get a component on this GameObject
Rigidbody rb = GetComponent<Rigidbody>();
// Get a component on a child GameObject
Collider childCollider = GetComponentInChildren<Collider>();
// Get all components of a type on this and children
MeshRenderer[] renderers = GetComponentsInChildren<MeshRenderer>();
// Add a component at runtime
BoxCollider box = gameObject.AddComponent<BoxCollider>();
// Remove a component (destroys it)
Destroy(box);
}
}
Finding GameObjects
using UnityEngine;
public class FindingObjects : MonoBehaviour
{
void Start()
{
// Find by tag (returns first match)
GameObject player = GameObject.FindWithTag("Player");
// Find all with tag
GameObject[] enemies = GameObject.FindGameObjectsWithTag("Enemy");
// Find by name (slow -- avoid in Update)
GameObject manager = GameObject.Find("GameManager");
// Compare tags efficiently (no GC allocation)
if (gameObject.CompareTag("Player"))
{
Debug.Log("This is the player");
}
}
}
Instantiating Prefabs
From the Unity docs example:
using UnityEngine;
public class InstantiationExample : MonoBehaviour
{
// Reference to the prefab. Drag a prefab into this field in the Inspector.
public GameObject myPrefab;
void Start()
{
// Instantiate at position (0, 0, 0) and zero rotation.
Instantiate(myPrefab, new Vector3(0, 0, 0), Quaternion.identity);
}
}
Instantiating with Parent Transform
using UnityEngine;
public cl
Read the complete source ↗