unity-workflowlisted

# Unity Development Workflow A design-first process for building Unity features with Hades Graph and memory. Follow all four phases in order. Do not skip phases — tasks that seem simple often reveal hidden complexity once the project context is loaded. This is a **process skill**. It defines how to approach Unity work, not what specific patterns to use. Load domain skills (`hades:unity-architect`, `hades:scene-authoring`, etc.) during the relevant phases for decision frameworks and tool sequences. ## When to Apply - When starting any non-trivial Unity feature (new system, new component type, cross-scene work) - When the feature touches multiple existing systems and you need to understand impact before designing - When `superpowers:brainstorming` is not available — this skill provides the same structure for Unity-specific work ## Project Context Check Used during Phase 1 (Analyze). Run these before designing anything: ``` get_project_summary() — understand overall project structure recall_memory("<feature_domain>") — find relevant prior decisions and patterns ``` ## Decision Framework ### Phase 1: Analyze Before doing anything, understand the scope. **Use Hades Graph tools to explore the project:** ``` get_project_summary() — overall structure: scenes, assemblies, major systems get_scene_summary("<scene>") — current scene hierarchy and component counts search_by_name("<keyword>") — find existing scripts, prefabs, or assets by