csharp-unity-majo

Enforce C# and Unity naming, XML documentation, and British spelling conventions.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/markjoshwel/skills --skill csharp-unity-majo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: csharp-unity-majo
Source: https://github.com/markjoshwel/skills/tree/main/csharp-unity-majo
Command: npx skills add https://github.com/markjoshwel/skills --skill csharp-unity-majo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies consistent C# and Unity conventions to reduce code churn, improve readability, and streamline collaboration across Mark's projects.

Core Features & Use Cases

  • Enforces naming conventions by access level (public camelCase, protected PascalCase, private _camelCase)
  • Requires XML documentation for public APIs and adheres to British spellings
  • Provides a structured framework for Unity patterns, including callback registration and event handling

Quick Start

Apply the C# and Unity standards to your project by reviewing code for naming, XML docs, and British spellings, then update files to conform.

Frequently Asked Questions about csharp-unity-majo

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

FAQPage Schema
How do I standardize C# naming conventions across a Unity project?

Standardize C# naming conventions by enforcing access-level rules: public fields use camelCase, protected fields use PascalCase, and private fields use _camelCase. This reduces code churn and improves readability across Unity projects.

What is the best way to enforce XML documentation and British spelling in C# code?

Enforce XML documentation and British spelling by applying coding standards that require XML docs for public APIs and mandate British spellings. This ensures consistent public API documentation across all project files.

How do I implement a consistent callback pattern for event handling in Unity?

Implement a consistent callback pattern in Unity by using a List-based callback registration framework. This standardizes event handling and callback registration across your C# project components.

Does this C# coding standard work for Unity projects without external dependencies?

Yes, this C# coding standard works for Unity projects without external dependencies. It applies naming conventions, XML documentation, and callback patterns directly to your Unity-based C# codebase.

Why use PascalCase for methods and _camelCase for private fields in C#?

Use PascalCase for methods and _camelCase for private fields to enforce access-level naming conventions. This distinction immediately signals field visibility, improving collaboration and reducing inconsistencies in C# code.