skills.rest
erymuzuan
erymuzuanCOMMUNITY
Explore all skills by this author →
GitHub

code-standards

Standardize C# coding conventions and project structure for MotoRent codebases.

Updated Jan 7, 2026
Search Tags:#csharp#dotnet#naming-conventions#code-review#clean-code#code-standards#project-organization
One-click install
npx skills add https://github.com/erymuzuan/motorent --skill code-standards-erymuzuan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-standards
Source: https://github.com/erymuzuan/motorent/tree/main/.copilot/skills/code-standards
Command: npx skills add https://github.com/erymuzuan/motorent --skill code-standards-erymuzuan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MotoRent codebase often suffers from inconsistent C# conventions and unclear project structure, leading to longer reviews and onboarding friction. The Skill codifies conventions for coding patterns, naming, and organization to ensure a uniform, maintainable codebase.

Core Features & Use Cases

  • Establishes framework-level guidelines: .NET 10, C# 14 or latest, nullable reference types enabled.
  • Standardizes naming and organization: PascalCase for types, camelCase for locals, interfaces prefixed with I, "m_" for private fields, "s_" for static fields, "c_" or PascalCase for constants.
  • Improves maintainability and reviews: consistent structure, easier onboarding, and faster code reviews.

Quick Start

Start applying MotoRent's C# standards to new and existing code to align with the documented patterns.

Frequently Asked Questions about code-standards

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

FAQPage Schema
What are the standard C# naming conventions for fields, constants, and interfaces?▼

Standard C# naming conventions dictate PascalCase for types, camelCase for locals, interfaces prefixed with I, "m_" for private fields, "s_" for static fields, and "c_" or PascalCase for constants to ensure uniform style.

How do I enforce consistent C# coding standards across a .NET project?▼

You enforce consistent C# coding standards by applying documented patterns for nullable reference types, naming conventions, and file organization across services, models, utilities, and tests during build and review workflows.

Does this C# code standards skill require a specific .NET version?▼

Yes, the C# code standards skill requires .NET 10 and C# 14 or latest, with nullable reference types enabled to establish framework-level guidelines for predictable code layout and maintainability.

Why standardize project organization for C# codebases?▼

Standardizing project organization for C# codebases solves the problem of inconsistent conventions and unclear structure, which leads to longer code reviews, onboarding friction, and reduced maintainability.

Can I use these clean code standards for existing C# codebases?▼

Yes, you can apply these C# standards to existing codebases to align with documented patterns for project organization, pattern usage, and naming conventions to achieve a uniform and maintainable codebase.

Related Skills

Explore More Software Engineering Skills→
dotnetdotnet
5.1k

migrate-nullable-references

Migrate .NET projects to C# Nullable Reference Types and resolve CS86xx warnings.

Official
Advanced
CodenburgCodenburg

branch-pr

Validate pull requests against approved issues and branch naming conventions.

Community
Intermediate
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced
deandumdeandum
3

style

Enforce language-agnostic coding style and conventions across a codebase.

Community
Intermediate