unity-script-roles

Before calling any skill in this module: if you are about to call a skill with parameters guessed from its name or description, STOP — read this file (or fetch its schema via GET /skills/recommend?includeSchema=true) first. If you already have the parameter definitions from recommend/schema, you may proceed straight to dryRun.

Triggers

• Deciding a class's role
• Splitting responsibilities across types
• Choosing between MonoBehaviour and plain C#
• Determine class responsibilities, split responsibilities across types, and choose between MonoBehaviour and pure C#

Unity Script Roles

Use this skill before creating a batch of gameplay scripts.

Goal

Turn a rough script list into explicit roles so AI does not generate everything as MonoBehaviour.

Output Format

• Script name
• Recommended role
• Main responsibility
• Main dependencies
• Why this role fits better than the alternatives

Common Roles

• MonoBehaviour bridge
• ScriptableObject config/data
• pure C# domain/service
• presenter / controller
• state / state machine node
• installer / bootstrap helper

Guardrails

Mode: Documentation only — no REST skills to gate; load freely under any operating mode (Approval / Auto / Bypass).

• Do not make every class a MonoBehaviour.
• Do not force ScriptableObject onto runtime state that should stay in memory-only objects.