Script role planner for Unity. Use when users want to decide class responsibilities — which should be MonoBehaviour, ScriptableObject, pure C# service, or installer. Triggers: script roles, class roles, what should be MonoBehaviour, service class, presenter, installer, responsibility, 脚本职责, 类的职责,...
--- name: unity-script-roles description: Advise on assigning 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# - 确定类的职责、在类型间拆分职责、在 MonoBehaviour 与纯 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.--- name: unity-script-roles description: Advise on assigning 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# - 确定类的职责、在类型间拆分职责、在 MonoBehaviour 与纯 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.
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.