Cursor Rules for C#: 6 Rules That Make AI Write Enterprise C# Code
This article discusses 6 rules for C# that help AI assistants like Cursor or Claude Code write C# code that follows .NET conventions and passes code review.
Why it matters
These rules help AI-generated C# code meet enterprise-level standards and avoid common pitfalls, improving code quality and developer productivity.
Key Points
- 1Enforce async/await usage correctly - ban async void and .Result
- 2Enforce constructor injection with interfaces - ban new for services
- 3Use immutable value objects instead of mutable classes
- 4Prefer expression-bodied members over block bodies
- 5Use string interpolation instead of string concatenation
- 6Avoid LINQ queries that can be replaced with simple foreach loops
Details
The article outlines 6 key rules for writing enterprise-grade C# code using AI assistants like Cursor or Claude Code. The rules cover best practices around async/await usage, dependency injection, immutable value objects, expression-bodied members, string interpolation, and LINQ queries. Each rule includes before/after examples to illustrate the changes. Following these rules helps ensure the AI-generated C# code compiles correctly, adheres to .NET conventions, and passes code review the first time.
No comments yet
Be the first to comment