agentleFS
testdino-hqtestdino-hq/google-styleguides-skills/csharp/SKILL.md

csharp

Skill15 starsChanged 9 months agoMITView on GitHub

Google's official C# style guide. Covers naming conventions, formatting, LINQ, async/await, XML documentation, and .NET best practices.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use var: when type is obvious from right side

    line 16
  2. Distinctive:

    Prefer expression-bodied members: when concise

    line 17

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Google C# Style Guide

Official Google C# coding standards for consistent, maintainable .NET code.

Golden Rules

  1. Follow .NET naming conventions — PascalCase for public members
  2. Use async/await for asynchronous operations
  3. LINQ for collections — prefer declarative over imperative
  4. XML documentation for public APIs
  5. Use var when type is obvious from right side
  6. Prefer expression-bodied members when concise
  7. Use nullable reference types (C# 8.0+)

Quick Reference

Naming Conventions

ElementConventionExample
Classes/InterfacesPascalCaseUserService, IRepository
MethodsPascalCaseGetUserById
PropertiesPascalCaseUserCount
Local variablescamelCaseuserCount
ConstantsPascalCaseMaxRetries
Private fields_camelCase_userId
ParameterscamelCaseuserId
EnumsPascalCaseDirection

Variables and Types

// ✓ CORRECT - use var when type is obvious
var users = new List<User>();
var count = users.Count;

// ✓ CORRECT - explicit type when not obvious
IEnumerable<User> result = GetUsers();

// ✓ CORRECT - nullable reference types (C# 8+)
string? optionalName = null;
string requiredName = "Alice";

Properties and Fields

// ✓ CORRECT - auto-properties
public string Name { get; set; }
public int Count { get; private set; }

// ✓ CORRECT - private fields with underscore prefix
private readonly string _connectionString;
private int _retryCount;

// ✓ CORRECT - expression-bodied property
public string FullName => $"{FirstName} {LastName}";

Methods and Expressions

// ✓ CORRECT - expression-bodied method
public string GetDisplayName() => $"{FirstName} {LastName}";

// ✓ CORRECT - traditional method body
public async Task<User> GetUserAsync(int id)
{
    var user = await _repository.FindAsync(id);
    return user ?? throw new NotFoundException(id);
}

Async/Await

// ✓ CORRECT - async all the way
public async Task<IEnumerable<User>> GetActiveUsersAsync()
{
    return await _db.Users
        .Where(u => u.IsActive)
        .ToListAsync();
}

// ✓ CORRECT - ConfigureAwait in library code
var result = await SomeAsyncMethod().ConfigureAwait(false);

// ✗ INCORRECT - blocking on async code
var result = SomeAsyncMethod().Result;  // can deadlock

LINQ

// ✓ CORRECT - LINQ for queries
var activeUsers = users
    .Where(u => u.IsActive)
    .OrderBy(u => u.LastName)
    .Select(u => new UserDto(u.Id, u.Name))
    .ToList();

// ✓ CORRECT - query syntax for complex joins
var result = from u in users
             join r in roles on u.RoleId equals r.Id
             where u.IsActive
             select new { u.Name, r.Title };

XML Documentation

// ✓ CORRECT - XML docs for public API
/// <summary>
/// Retrieves a user by their unique identifier.
/// </summary>
/// <param name="id">The user's unique ID.</param>
/// <returns>The user, or null if not found.</returns>
/// <exception cref="ArgumentException">Thrown when id is negative.</exception>
public Task<User?> GetUserByIdAsync(int id)
{
    // ...
}

Interfaces and Dependency Injection

// ✓ CORRECT - depend on interfaces
public class UserService
{
    private readonly IUserRepository _repository;

    public UserService(IUserRepository repository)
    {
        _repository = repository;
    }
}

Common Mistakes

MistakeCorrect Approach
Blocking on async (.Result, .Wait())Use async/await all the way
Missing XML docs on public APIDocument with /// XML comments
public fieldsUse properties with get/set
Ignoring nullabilityEnable <Nullable>enable</Nullable>
Imperative loops for collectionsUse LINQ
Magic stringsUse nameof() or constants
Catching Exception broadlyCatch specific exception types

When to Use This Guide

  • Writing new C# code
  • Refactoring existing C#
  • Code reviews
  • Setting up .editorconfig rules
  • Onboarding new team members

Install

npx skills add testdino-hq/google-styleguides-skills/csharp

Full Guide

See csharp.md for complete details, examples, and edge cases.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.