data-modeling

Guide Unity data modeling decisions for ScriptableObject patterns and runtime state.

51|7|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/TheArcForge/UniClaude --skill data-modeling-thearcforge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-modeling
Source: https://github.com/TheArcForge/UniClaude/tree/main/Sidecar~/skills/data-modeling
Command: npx skills add https://github.com/TheArcForge/UniClaude --skill data-modeling-thearcforge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unity projects often struggle with inconsistent data design, leading to tightly coupled systems and repetitive boilerplate. This Skill provides structured decision frameworks for ScriptableObject patterns, runtime state management, serialization strategies, and data-driven architecture to unify data decisions across prototypes and shipped games.

Core Features & Use Cases

  • ScriptableObject Pattern Selection: choose between data containers, runtime sets, event channels, or enum-like SOs to match data needs and evolution.
  • Runtime State Management & Save Architecture: decide on per-instance vs centralized state, serialization strategy, and versioned save structures to enable reliable persistence.
  • Inspector Exposure & Maintainability: enforce clean inspector exposure, asset-driven configuration, and accessible design patterns for long-term maintainability.

Quick Start

Choose the appropriate ScriptableObject pattern for your data, define a clear runtime state strategy, and document your save and inspector decisions to standardize future work.

Frequently Asked Questions about data-modeling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to structure Unity data models to avoid tightly coupled systems?

To structure robust Unity data models, apply structured decision frameworks for ScriptableObject patterns and runtime state management. This prevents tightly coupled systems by standardizing data containers, event channels, and serialization workflows across prototypes and shipped games.

How do I choose the right ScriptableObject pattern for my game data?

Choosing the right ScriptableObject pattern requires evaluating data needs and evolution to select between data containers, runtime sets, event channels, or enum-like SOs. This framework matches specific data requirements to the appropriate SO structure for maintainability.

How do I manage runtime state and save architecture in Unity?

Managing runtime state and save architecture involves deciding between per-instance or centralized state, selecting serialization strategies, and implementing versioned save structures. This approach enables reliable persistence and standardized data decisions.

Can I use this data modeling approach for both prototypes and shipped Unity games?

Yes, this data modeling approach applies to both prototypes and shipped Unity games. It unifies data decisions across project lifecycles by providing consistent frameworks for inspector exposure, asset-driven configuration, and maintainable design patterns.

When should I not use a centralized runtime state strategy in Unity?

You should reconsider a centralized runtime state strategy when your Unity project requires highly autonomous per-instance behaviors. The framework guides this decision by contrasting per-instance versus centralized state, ensuring your serialization strategy matches your scaling needs.