unity-code-conventions

Implement Unity C# coding standards and naming conventions.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/tranvietanh0/StackTheRing --skill unity-code-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-code-conventions
Source: https://github.com/tranvietanh0/StackTheRing/tree/main/.claude/skills/unity-code-conventions
Command: npx skills add https://github.com/tranvietanh0/StackTheRing --skill unity-code-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to Unity C# coding conventions, ensuring code consistency and maintainability.

Core Features & Use Cases

  • Code Standards: Enforce consistent naming conventions, structure, and best practices.
  • Security Guidelines: Safeguard against common security pitfalls in Unity development.
  • Anti-Patterns: Avoid bad coding habits and promote clean, efficient code.
  • Use Case: Utilize this Skill when starting a new Unity project or conducting a code review to ensure adherence to established standards.

Quick Start

Review the 'SKILL.md' for Unity C# code conventions, including naming rules, no-hardcoded-values, and DOTS-specific rules.

Frequently Asked Questions about unity-code-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the standard naming conventions for Unity C# scripts?

Reviewing the provided guidelines ensures your Unity C# scripts avoid hardcoded values and follow established naming rules, preventing common anti-patterns during code reviews.

How do I avoid anti-patterns and hardcoded values in Unity C# development?

By adhering to standardized coding practices, you eliminate bad coding habits and ensure your Unity project remains modular, secure, and easy to maintain.

When do I need to apply specific coding standards for Unity DOTS?

The guidelines include DOTS-specific rules that help structure your C# code efficiently, avoiding anti-patterns unique to entity-component-system architectures.

Can I use these Unity C# coding conventions for an existing project code review?

The guidelines provide a comprehensive checklist for naming rules, security, and anti-patterns, making them highly effective for auditing and improving legacy Unity codebases.

Does this Unity C# best practices guide require any specific dependencies?

It functions purely as a reference for coding standards and anti-patterns, seamlessly integrating into your workflow without requiring additional packages or tools.