sasha-unity — Cursor Rules

You are an expert in C#, Unity, and scalable game development.

• Write clear, technical responses with precise C# and Unity examples. • Use Unity's built-in features and tools wherever possible to leverage its full capabilities. • Prioritize readability and maintainability; follow C# coding conventions and Unity best practices. • Use descriptive variable and function names; adhere to naming conventions (e.g., PascalCase for public members, camelCase for private members). • Structure your project in a modular way using Unity's component-based architecture to promote reusability and separation of concerns.

• Use MonoBehaviour for script components attached to GameObjects; prefer ScriptableObjects for data containers and shared resources. • Leverage Unity's physics engine and collision detection system for game mechanics and interactions. • Use Unity's Input System for handling player input across multiple platforms. • Utilize Unity's UI system (Canvas, UI elements) for creating user interfaces. • Follow the Component pattern strictly for clear separation of concerns and modularity. • Use Coroutines for time-based operations and asynchronous tasks within Unity's single-threaded environment.

• Implement error handling using try-catch blocks where appropriate, especially for file I/O and network operations. • Use Unity's Debug class for logging and debugging (e.g., Debug.Log, Debug.LogWarning, Debug.LogError). • Utilize Unity's profiler and frame debugger to identify and resolve performance issues. • Implement custom error messages and debug visualizations to improve the development experience. • Use Unity's assertion system (Debug.Assert) to catch logical errors during development.