Identify and prevent production C# pitfalls like async/await deadlocks and nullability mistakes.
npx skills add https://github.com/WTFox/dotfiles --skill csharp-wtfox
Please help me install this Agent Skill. Skill: csharp Source: https://github.com/WTFox/dotfiles/tree/main/claude/.claude/skills/csharp Command: npx skills add https://github.com/WTFox/dotfiles --skill csharp-wtfox
This skill helps developers avoid and remediate the most dangerous, production-grade C# pitfalls that show up in real-world code, such as async/await deadlocks, improper cancellation propagation, nullable reference type pitfalls, DI mispatterns, and LINQ vs loops, ensuring more reliable and maintainable software.
Read this guide before writing or reviewing any production C# code to apply the patterns consistently.
High-intent search queries and answers about installing and using this skill.
Prevent async/await deadlocks by avoiding .Result or .Wait() in production ASP.NET Core apps and ensuring async flows all the way through call chains. Library code should apply ConfigureAwait(false) to avoid synchronization context capture.
Proper CancellationToken propagation threads the token through every asynchronous method signature and layer, ensuring data access methods and I/O operations receive and respect the token for safe cancellation.
Enable nullable reference types and use required or init properties to enforce safe state initialization at compile time. This prevents nullability pitfalls and guarantees immutable data structures are fully populated.
Use records for immutable data transfer objects where value equality matters, and use classes for entities with identity and mutable state. This distinction ensures maintainable and reliable domain models.
Yes, this guidance applies to EF Core by enforcing constructor-based dependency injection for testability. It ensures data access contexts and services are properly injected rather than manually instantiated.
Using .Result or .Wait in asynchronous I/O operations causes thread pool starvation and deadlocks by blocking the calling thread. These limitations make synchronous blocking highly discouraged in production C# environments.
jim60105Initialize C# ASP.NET Core Web API projects with Entity Framework Core and configuration files.
macaughDetects injection, memory safety and authorization flaws in multiple languages.
JeffallanDesign and implement .NET 8+ C# applications with ASP.NET Core APIs, Blazor, and EF Core.
sunzhkEnforce Google's C# Style Guide rules via Roslyn analyzers and .editorconfig.
