Files

T

AdminandClaude Opus 4.8 a3bf796f17 chore(backend): install AI agent skills for the .NET stack

Run autoskills in backend/: detects .NET/C#/ASP.NET Core/Minimal API and
installs 13 skills for universal (.agents) and claude-code (.claude) agents,
with backend/skills-lock.json. Adds ASP.NET Core, Minimal API + OpenAPI,
file-upload and containerization skills on top of the prior C#/.NET set.
Removes the stale root skills from the old layout.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-05 03:48:31 +02:00

1.8 KiB

Raw Blame History

name, description

name	description
csharp-async	Get best practices for C# async programming

C# Async Programming Best Practices

Your goal is to help me follow best practices for asynchronous programming in C#.

Naming Conventions

Use the 'Async' suffix for all async methods
Match method names with their synchronous counterparts when applicable (e.g., GetDataAsync() for GetData())

Return Types

Return Task<T> when the method returns a value
Return Task when the method doesn't return a value
Consider ValueTask<T> for high-performance scenarios to reduce allocations
Avoid returning void for async methods except for event handlers

Exception Handling

Use try/catch blocks around await expressions
Avoid swallowing exceptions in async methods
Use ConfigureAwait(false) when appropriate to prevent deadlocks in library code
Propagate exceptions with Task.FromException() instead of throwing in async Task returning methods

Performance

Use Task.WhenAll() for parallel execution of multiple tasks
Use Task.WhenAny() for implementing timeouts or taking the first completed task
Avoid unnecessary async/await when simply passing through task results
Consider cancellation tokens for long-running operations

Common Pitfalls

Never use .Wait(), .Result, or .GetAwaiter().GetResult() in async code
Avoid mixing blocking and async code
Don't create async void methods (except for event handlers)
Always await Task-returning methods

Implementation Patterns

Implement the async command pattern for long-running operations
Use async streams (IAsyncEnumerable) for processing sequences asynchronously
Consider the task-based asynchronous pattern (TAP) for public APIs

When reviewing my C# code, identify these issues and suggest improvements that follow these best practices.

1.8 KiB Raw Blame History