.NET Core Expert sets how Claude writes .NET 8 and C# 12 backends. It follows five steps: analyze requirements, design clean architecture layers, implement with dotnet build checks, secure the API and test with dotnet test.
Five reference files cover minimal APIs, clean architecture with CQRS, Entity Framework Core, JWT authentication and authorization policies, and cloud-native patterns such as Docker, health checks, configuration and OpenTelemetry.
What You Get
- A project structure with domain, application, infrastructure and API layers
- Minimal API endpoints with OpenAPI documentation
- MediatR commands, queries and pipeline behaviors
- EF Core DbContext, entity configuration and migrations
- JWT authentication and authorization policies, plus a Dockerfile and health checks
Common Use Cases
- Starting a new .NET 8 web API with clean architecture
- Adding CQRS handlers with MediatR to an existing service
- Designing EF Core relationships and tuning queries
- Containerizing a .NET service with health checks for Kubernetes
What Makes It Unique
The rules are specific to modern .NET: record types for DTOs, nullable reference types, async everywhere, no legacy .NET Framework patterns and no deprecated EF Core patterns. The workflow builds after implementing and tests before moving on, and fixes failures before it continues.
Under The Hood
The skill is a SKILL.md with five reference files and no scripts, and the references load by topic. The workflow tells the agent to run dotnet build and dotnet test and to check endpoints with curl or a REST client. The references show dotnet ef migration commands that change a database, Docker and Kubernetes manifests, and sample code that creates and verifies JWT tokens from a secret in configuration. The skill itself does not fetch web pages.