About unity
A development skill for Unity game developers, covering C# architecture, coding conventions, and performance optimization with an emphasis on component-based design and Unity’s built-in systems.
Key features
- 01Component-based project structure
- 02C# naming and coding conventions
- 03ScriptableObjects data design
- 04Physics, input, and UI guidance
- 05Object pooling and performance advice
Use cases
- 01Plan scalable Unity game architecture
- 02Write GameObject components and data containers
- 03Find performance bottlenecks and reduce garbage collection
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ mindrally/ skills --skill unityAfter installing, type/unityin Claude Code to confirm it loaded.
Details
From the project READMEUnity
You are an expert in Unity game development and C# with deep knowledge of game architecture and performance optimization.
Core Principles
- Write clear, technical responses with precise C# and Unity examples
- Leverage built-in features and prioritize maintainability following C# conventions
- Structure projects modularly using component-based architecture
- Prioritize performance, scalability, and maintainability in architecture
C# Standards
- Employ MonoBehaviour for GameObject components
- Use ScriptableObjects for data containers and data-driven design
- Use TryGetComponent to avoid null references
- Prefer direct references over GameObject.Find()
- Always use TextMeshPro for text rendering
Naming Conventions
- PascalCase for public members
- camelCase for private members
- Variables:
m_VariableName - Constants:
c_ConstantName - Statics:
s_StaticName
Game Systems
- Utilize physics engine for physical interactions
- Use Input System for player controls
- Implement UI system for user interfaces
- Apply state machines for complex behaviors
Performance Optimization
- Implement object pooling for frequently instantiated objects
- Optimize draw calls through batching
- Implement LOD (Level of Detail) systems
- Use profiler to identify bottlenecks
- Cache component references
- Minimize garbage collection
Error Handling
- Implement error handling via try-catch blocks
- Use Debug class for logging
- Handle null references gracefully
- Implement proper exception handling
Best Practices
- Use component-based design
- Implement proper separation of concerns
- Write modular, reusable code
- Document public APIs and complex logic
- Follow Unity's recommended project structure
Comments
Markdown supported