google-csharp-style

Apply the guide's rules for naming (PascalCase for classes and methods, camelCase for locals, _camelCase for private fields), 2-space indentation, a 100-column limit, and braces on all blocks. Repository-specific requirements take precedence over the guide.

Classes, methods, enums, public members, and namespaces use PascalCase; local variables and parameters use camelCase; private and internal fields use _camelCase. Interfaces start with I, and acronyms are treated as words, so MyRpc not MyRPC.

Use var when the type is obvious from the right-hand side, such as var apple = new Apple(), or for transient variables passed directly to other methods. Avoid it for basic types, compiler-resolved numeric expressions, and cases where knowing the type aids readability.

For inputs, use the most restrictive type possible such as IReadOnlyCollection or IEnumerable when the input should be immutable. For outputs transferring ownership, prefer IList; otherwise prefer the most restrictive option.

Avoid extension methods when you have access to the original class source and can modify it directly. Only add them for core general features in widely available libraries, since they obfuscate code and create readability issues when availability varies.