# Nlelouche Unity3d Antigravityskills Advanced Design Patterns > --- - Skill: `tomevault-io/nlelouche-unity3d-antigravityskills-advanced-design-patterns` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/nlelouche-unity3d-antigravityskills-advanced-design-patterns` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/nlelouche-unity3d-antigravityskills-advanced-design-patterns/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/nlelouche-unity3d-antigravityskills-advanced-design-patterns --- --- name: advanced-design-patterns description: "Principal Architect for SOLID & GoF Patterns in Unity 3D. Activate for complex systems, scalable mechanics, decoupled architectures, or refactoring God Classes." version: 2.0.0 tags: ["architecture", "patterns", "SOLID", "GoF", "strategy", "factory", "observer", "command"] argument-hint: "pattern='strategy' name='EnemyBehavior' namespace='Game.AI'" disable-model-invocation: false user-invocable: true allowed-tools: - run_command - list_dir - write_to_file requirements: unity_version: ">=6.0" render_pipeline: "Any" dependencies: [] context_discovery: check_unity_version: true check_render_pipeline: false scan_manifest_for: [] performance_budget: gc_alloc_per_frame: "0 bytes target in hot paths" max_update_cost: "O(n) - profiler-guided" tdd_first: true # ⚠️ Updated by audit v2.0.1 - needs manual test implementation --- # Advanced Design Patterns ## Overview Transform high-level gameplay requirements into modular, testable, and maintainable systems. This skill enforces strict structural patterns (Strategy, Factory, Observer, Command) adapted for Unity's unique lifecycle. ## When to Use - Use when implementing any of the GoF design patterns - Use when refactoring "God Classes" or circular dependencies - Use when creating interchangeable behaviors (Strategy) - Use when spawning objects with pooling (Factory) - Use when implementing decoupled event systems (Observer) - Use when building undo/redo or input replay systems (Command) ## Available Patterns | Pattern | Use Case | Template | |---------|----------|----------| | **Strategy** | Interchangeable behaviors (AI, attacks) | `IStrategy.cs`, `StrategyContext.cs` | | **Factory** | Object creation with pooling | `IFactory.cs`, `PooledFactory.cs` | | **Observer** | Decoupled event notifications | `IObserver.cs` | | **Command** | Undo/redo, input recording | `ICommand.cs`, `CommandInvoker.cs` | ## Thinking Process (Mandatory) Before generating code, analyze: 1. **Identify the Axis of Change**: What varies? (Behavior, Creation, Notification) 2. **Pattern Selection**: Justify choice based on problem domain 3. **Unity Compatibility**: MonoBehaviour vs ScriptableObject vs plain C# 4. **SOLID Validation**: SRP and OCP compliance check ## Procedure 1. **Generate Architecture Plan**: Emit class diagram before implementation 2. **Define Contracts**: Create interfaces with clear API boundaries 3. **Implement Concretes**: Build decoupled implementations 4. **Inject Dependencies**: Use VContainer or SO-based injection (no static Singletons!) 5. **Audit**: Verify against constraints ## Best Practices - ✅ Use interfaces as reference types, not concrete classes - ✅ Prefer composition over inheritance - ✅ Every Factory for high-frequency objects MUST use Object Pooling - ✅ Unsubscribe from events in `OnDisable`/`OnDestroy` - ✅ Use `[SerializeField] private` with `_camelCase` naming - ❌ **NEVER** use `GameObject.Find`, `SendMessage`, `BroadcastMessage` - ❌ **NEVER** use large switch/if-else for behavior selection - ❌ **NEVER** cast interface back to concrete class ## Architecture Audit Checklist - [ ] **SRP Compliance**: Each class has single responsibility - [ ] **Memory Safety**: Events unsubscribed in OnDestroy - [ ] **Performance**: No heap allocations in Update loops ## Few-Shot Examples ### Example 1: Strategy Pattern for AI **User**: "I need different enemy AI behaviors like patrolling, chasing, and retreating." **Agent Output**: ``` 1. Generate Implementation Plan with Strategy Pattern 2. Create IEntityBehavior interface 3. Implement PatrolBehavior, ChaseBehavior, RetreatBehavior 4. Create EnemyController with SetBehavior(IBehavior) method 5. Inject behaviors via ScriptableObject references ``` ### Example 2: Factory with Pooling **User**: "Create a projectile spawning system that doesn't cause GC spikes." **Agent Output**: ``` 1. Create IProjectileFactory interface 2. Implement ProjectilePooledFactory : PooledFactory 3. Configure initial pool size based on expected max concurrent 4. Add Return() method call on projectile destruction ``` ### Example 3: Observer for UI Updates **User**: "Update the health bar when player takes damage without coupling." **Agent Output**: ``` 1. Create IHealthObserver interface 2. Create PlayerHealth : ISubject 3. Create HealthBarUI : IObserver 4. Subscribe in OnEnable, unsubscribe in OnDisable ``` --- ## TDD Contract > ⚠️ **Legacy Skill — Refactor Pending** > Este skill NO tiene tests automatizados aún. El siguiente boilerplate es un punto de partida. ```csharp // Escribe estos tests ANTES de implementar: // Test 1: should [expected behavior] when [condition] [Test] public void AdvancedDesignPatterns_Should{ExpectedBehavior}_When{Condition}() {{ // Arrange // TODO: Setup test fixtures // Act // TODO: Execute system under test // Assert Assert.Fail("Not implemented — write test first"); }} // Test 2: should handle [edge case] [Test] public void AdvancedDesignPatterns_ShouldHandle{EdgeCase}() {{ // Arrange // TODO: Setup edge case scenario // Act // TODO: Execute // Assert Assert.Fail("Not implemented"); }} // Test 3: should throw when [invalid input] [Test] public void AdvancedDesignPatterns_ShouldThrow_When{InvalidInput}() {{ // Arrange var invalidInput = default; // Act & Assert Assert.Throws(() => {{ /* execute */ }}); }} ``` ### Pasos para completar el TDD: 1. **Descomenta** los tests above 2. **Implementa** la funcionalidad mínima para que compile 3. **Ejecuta** los tests — deben fallar (RED) 4. **Implementa** la funcionalidad real 5. **Verifica** que los tests pasen (GREEN) 6. **Refactorea** manteniendo los tests verdes --- **Nota**: Este skill fue marcado como `tdd_first: false` durante la auditoría v2.0.1. La sección TDD fue agregada automáticamente pero requiere customización manual para reflejar el comportamiento real del skill. ## Related Skills - `@event-bus-system` - For global decoupled events - `@di-container-manager` - For dependency injection setup - `@scriptableobject-architecture` - For data-driven pattern implementations ## Generator Script ```bash python scripts/pattern_gen.py --pattern strategy --name EnemyAI --namespace Game.AI python scripts/pattern_gen.py --pattern factory --name Projectile --namespace Game.Combat ``` --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/nlelouche) — claim your Tome and manage your conversions.