unity-script-roles

Classify Unity scripts into MonoBehaviour, ScriptableObject, or C# service roles.

Updated May 9, 2026
One-click install
npx skills add https://github.com/krikommp/chess-game --skill unity-script-roles-krikommp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-script-roles
Source: https://github.com/krikommp/chess-game/tree/main/.agents/skills/unity-skills/skills/script-roles
Command: npx skills add https://github.com/krikommp/chess-game --skill unity-script-roles-krikommp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users plan and categorize Unity script roles effectively, reducing confusion and ensuring proper class organization during development.

Core Features & Use Cases

  • Script Role Planning: Determines whether a script should be a MonoBehaviour, ScriptableObject, pure C# service, or installer.
  • Decision Aid: Provides guidelines for choosing the right role for each script, based on its responsibilities.
  • Use Case: Before starting a new Unity project, use this Skill to map out which scripts will be MonoBehaviour, which should be ScriptableObjects, and where to use pure C# services.

Quick Start

Run the 'unity-script-roles' skill to generate a script role plan for your Unity project.

Frequently Asked Questions about unity-script-roles

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

FAQPage Schema
How do I plan Unity script roles for a new project?

Use this framework to classify scripts as MonoBehaviour, ScriptableObject, or pure C# service based on their responsibilities, ensuring optimal code structure before starting development.

When should I use a ScriptableObject instead of a MonoBehaviour in Unity?

Choose ScriptableObject over MonoBehaviour when the script manages shared data or configuration rather than GameObject-specific behavior, following established role categorization guidelines.

What is the best way to categorize Unity scripts by responsibility?

Analyze script content and dependencies to assign roles like pure C# service or installer, reducing confusion and ensuring proper class organization during development.

How do I decide if a Unity script should be a pure C# service?

Designate a Unity script as a pure C# service when it handles logic independent of the Unity lifecycle, ensuring better code structure and maintainability across the project.

Can I use this Unity script role framework for an existing codebase?

Yes, apply this framework to an existing codebase by analyzing current script content and dependencies to refactor and reassign class roles for improved maintainability.