SkillAgentSearch skills...

unity-scriptableobjects

Unity 6.3 LTS data and decoupling with ScriptableObjects: CreateAssetMenu config assets, shared runtime variables, event channels and .asset files made from code. Use for replacing singletons, data-driven items or cards, or values that persist after leaving Play mode.

Install / Use

npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill unity-scriptableobjects

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

92/100

Supported Platforms

Universal

Tags

Our assessment of unity-scriptableobjects

unity-scriptableobjects scores 92/100 on our quality scale, 826th of 4,698 Development & Engineering skills we index (top 18%).

Its SKILL.md is 5.6 KB long, well organised into 10 sections with 4 code examples: a solid amount of guidance for an agent.

With 8,904 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
20/20
Description
15/15
Adoption
17/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 4 days ago, so unity-scriptableobjects is actively maintained.
  • Our last check on 2026-10-10 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-08. Automated pattern scan on 2026-10-08. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

unity-scriptableobjects compared with similar skills

All 4 of these similar skills score higher than unity-scriptableobjects; compare them before choosing.

SkillScoreStarsUpdatedFormat
unity-scriptableobjects (this skill)by gamedev-skills928.9k4d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install unity-scriptableobjects?
Run npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill unity-scriptableobjects. The install tabs above show the steps for each supported agent.
Which AI agents does unity-scriptableobjects work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is unity-scriptableobjects safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is unity-scriptableobjects still maintained?
The repository was last updated 4 days ago, so unity-scriptableobjects is actively maintained.

name: unity-scriptableobjects description: > Architect Unity 6.3 LTS data and decoupling with ScriptableObjects: config/data assets, shared runtime variables, event channels, and runtime sets/registries. Use when designing data-driven systems, replacing singletons/managers, creating .asset data with CreateAssetMenu, or when the user mentions ScriptableObject, SO architecture, or data assets.

Unity ScriptableObject Architecture

Use ScriptableObject assets to store shared data and decouple systems in Unity 6.3 LTS — configuration, event channels, and registries that live as project assets instead of being hard-wired into scenes or singletons. Targets Unity 6.3 LTS (6000.3).

When to use

  • Use when you need designer-editable config (weapon stats, level data), to share one value between unrelated systems, to decouple senders from listeners via event channels, or to build a runtime registry of active objects — without a static/singleton manager.
  • Use when the project has *.asset data files backed by : ScriptableObject classes.

When not to use: per-instance runtime state that differs per GameObject (that belongs on a MonoBehaviour) — a ScriptableObject asset is shared by everyone who references it. Saving player progress to disk → save-systems. Plain DTOs that never need to be an asset can just be [System.Serializable] classes.

Core workflow

  1. Define the class deriving from ScriptableObject and tag it with [CreateAssetMenu] so designers can create instances from the Assets menu.
  2. Create one or more .asset instances in the Project window; each is a shared, named piece of data referenced by [SerializeField] fields.
  3. Reference, don't copy. MonoBehaviours hold a reference to the asset; they all see the same data, so changing the asset changes every consumer.
  4. For decoupling, model signals and shared variables as ScriptableObjects: a "FloatVariable" the HUD reads and the player writes; an "event channel" the player raises and many systems listen to. Neither side references the other.
  5. Reset runtime mutations in OnEnable if the asset is mutated during play, because edits made in the Editor at runtime persist on the asset (a frequent source of "my values changed after I played").
  6. Verify by inspecting the asset values during Play mode and confirming consumers react.

Patterns

1. Config/data asset

using UnityEngine;

[CreateAssetMenu(fileName = "WeaponData", menuName = "Game/Weapon Data", order = 0)]
public class WeaponData : ScriptableObject
{
    public string displayName = "Pistol";
    public int    damage = 10;
    public float  fireRate = 0.25f;
    public GameObject projectilePrefab;
}
public class Weapon : MonoBehaviour
{
    [SerializeField] private WeaponData data;   // assign the shared asset in the Inspector
    private void Fire() => Debug.Log($"{data.displayName} for {data.damage}");
}

2. Shared runtime variable (decouples producer from consumer)

[CreateAssetMenu(menuName = "Game/Float Variable")]
public class FloatVariable : ScriptableObject
{
    [SerializeField] private float initialValue;
    [System.NonSerialized] public float runtimeValue;   // not saved to the asset

    private void OnEnable() => runtimeValue = initialValue;  // reset each play session
}
// Player writes playerHealth.runtimeValue; the HUD reads it — neither references the other.

3. Creating an instance at runtime (not an asset on disk)

// For transient SO data you build in code (e.g. a generated config).
var temp = ScriptableObject.CreateInstance<WeaponData>();
temp.damage = 25;
// ...use temp...  Destroy(temp);   // clean up runtime-created instances

Pitfalls

  • Editing an SO at runtime persists in the Editor — values you change during Play stay changed on the asset after you stop. Keep mutable runtime state in [NonSerialized] fields reset in OnEnable, or it will surprise you. (In a build, asset edits do not persist across launches.)
  • Disabled Domain Reload skips your OnEnable reset — with Enter Play Mode Options enabled and Reload Domain off (a Unity 6.3 LTS fast-iteration setting), already-loaded SOs are not re-created when you press Play, so OnEnable never fires and runtimeValue keeps its value from the previous session. Reset explicitly from an ISerializationCallbackReceiver or a scene-load hook instead of relying on OnEnable alone.
  • Expecting per-object state — every reference points to the same asset. If two enemies need different current HP, store HP on the MonoBehaviour, not the shared SO.
  • No frame lifecycle — ScriptableObjects have OnEnable/OnDisable/OnDestroy but no Update. Don't expect per-frame callbacks.
  • Using SOs as a save file — they're authoring assets, not runtime persistence; write progress with save-systems instead.
  • Leaking CreateInstance objects — runtime-created instances are not garbage-collected like plain C# objects; Destroy them when done.

References

  • For the event-channel pattern (a GameEvent SO + listeners, type-safe payloads) and runtime sets/registries (a shared list of active enemies), read references/event-channels.md.
  • Primary docs: Unity Manual "ScriptableObject" (/Manual/class-ScriptableObject.html) and ScriptReference/ScriptableObject, ScriptReference/CreateAssetMenuAttribute.

Related skills

  • unity-csharp-scripting — the MonoBehaviours that consume these assets.
  • save-systems — persisting state to disk (what SOs are not for).
  • card-game / rpg / survival-crafting — genres that lean on SO-driven data.

Related Skills

View on GitHub
GitHub Stars8.9k
CategoryDevelopment
Updated4d ago
Forks905

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions