C# Developer covers modern .NET work: ASP.NET Core APIs in minimal or controller style, Entity Framework Core data access, Blazor Server and WebAssembly apps, and CQRS with MediatR.
Rules include nullable reference types, file-scoped namespaces, dependency injection, strongly typed options and a CancellationToken forwarded through every async call. After the implementation step, a migration is generated and reviewed before it is applied.
What You Get
- Domain models and DTOs
- Minimal API endpoints or controllers
- Repository and service implementations
- Program.cs and appsettings.json configuration
- xUnit tests with TestServer aimed at 80 percent coverage
Common Use Cases
- Building an ASP.NET Core REST API
- Adding EF Core data access and migrations
- Creating a Blazor component with state management
- Tuning performance with Span and Memory
- Setting up authentication and authorization
What Makes It Unique
The rules are concrete and show right and wrong forms: never block on .Result or .Wait(), never expose EF entities in API responses, always forward cancellation tokens, and use a Result pattern for errors. References cover modern C#, ASP.NET Core, Entity Framework, Blazor and performance.
Under The Hood
The skill is a SKILL.md with five reference files and no scripts. It tells the agent to read your project files and run dotnet commands, including dotnet ef migrations add and remove, which means shell commands that change your project and can touch a database when a migration is applied. It writes C# source and configuration files. It does not fetch web pages or call outside APIs.