Unity Pattern Selector

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 which pattern fits a problem
• Structuring decoupled systems
• Choosing event/state-machine/pool approaches
• 判断哪种模式适合某问题、构建解耦系统、在事件/状态机/对象池方案间抉择

Unity Pattern Selector

Use this skill to decide whether a pattern is justified. Do not recommend every pattern at once.

Guardrails

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

• Recommend at most 1-3 patterns, and explain why simpler options are not enough.

Pattern Guide

• ScriptableObject

  • Use for authored config, shared static data, event channels, and reusable data assets.
  • Avoid as the default home for per-run mutable gameplay state.

• C# events / delegates

  • Use for one-to-many notifications with clear ownership and unsubscribe points.
  • Avoid for imperative flows that need ordering, return values, or complex debugging.

• Global event bus / observer hub

  • Use sparingly and only when many systems truly need broad decoupled notifications.
  • Avoid as the default answer to coupling. It often hides ownership and makes debugging harder.

• Interfaces

  • Use when multiple implementations or clearer dependency boundaries are needed.
  • Avoid adding interfaces around every class without a real seam.

• State machine

  • Use for actors with mutually exclusive states and explicit transitions.
  • Avoid when a few booleans or a small command flow is enough.