- Home
- Skills
- Jeffallan
- Claude Skills
- Dotnet Core Expert
dotnet-core-expert_skill
- HTML
110
GitHub Stars
1
Bundled Files
3 weeks ago
Catalog Refreshed
2 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstart where the catalogue uses aiagentskills.
npx veilstart add skill jeffallan/claude-skills --skill dotnet-core-expert- SKILL.md3.5 KB
Overview
This skill is a .NET 8 expert designed to help build high-performance, cloud-ready applications using minimal APIs, clean architecture, and modern C# patterns. It focuses on practical implementation: Entity Framework Core, CQRS with MediatR, JWT authentication, AOT compilation, and scalable microservice patterns. Use it as an expert pair programmer to produce production-ready projects and tests.
How this skill works
I inspect your requirements and propose a clear solution architecture with layered projects (API, Application, Domain, Infrastructure, Tests). I provide concrete code snippets and templates: minimal API endpoints, DbContext and EF Core migrations, MediatR request/handler patterns, JWT setup, DI configuration, and AOT build integration. I also recommend testing strategies (xUnit, WebApplicationFactory) and deployable artifacts (Dockerfiles, health checks, OpenAPI).
When to use it
- Starting a new .NET 8 service with minimal APIs and clean architecture
- Implementing CQRS patterns using MediatR for complex business logic
- Setting up Entity Framework Core with migrations and async repositories
- Adding JWT authentication and authorization policies to APIs
- Optimizing startup and runtime with AOT compilation for small images
Best practices
- Enable nullable reference types and use async/await for all I/O
- Keep domain models separate from API DTOs; return DTOs, not entities
- Use record types for DTOs and immutable domain objects where appropriate
- Centralize DI in the API project and avoid mixing layers’ responsibilities
- Store secrets in a secure store (Azure Key Vault, AWS Secrets Manager) and never in code
- Write integration tests with WebApplicationFactory and cover end-to-end flows
Example use cases
- Create a minimal API service with CRUD endpoints, paging, and EF Core migrations
- Implement a CQRS flow: Commands + Handlers for writes and Queries + Projections for reads using MediatR
- Add JWT-based auth with role/claim policies and refresh token handling
- Containerize a microservice, add health checks, OpenAPI docs, and Kubernetes readiness probes
- Prepare an AOT-compiled self-contained image to reduce cold-start time in serverless environments
FAQ
No. All I/O should be async. Legacy .NET Framework patterns and synchronous DB calls are avoided.
How do you handle secrets and configuration?
I recommend using environment-specific configuration plus a managed secret store; never store secrets in source or appsettings.json for production.