dotnet-core-expert

Name: dotnet-core-expert
Availability: InStock
Author: jeffallan

Build .NET 8 minimal APIs with EF Core, CQRS, and JWT authentication.

10.9k|1.0k|Updated Oct 20, 2025

Search Tags:#dotnet #JWT #CQRS #MediatR #minimal-api #EF-core #net8

Ready to run

npx skills add https://github.com/Jeffallan/claude-skills --skill dotnet-core-expert

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-core-expert
Source: https://github.com/Jeffallan/claude-skills/tree/main/skills/dotnet-core-expert
Command: npx skills add https://github.com/Jeffallan/claude-skills --skill dotnet-core-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides building modern .NET 8 apps with minimal APIs, clean architecture, EF Core, CQRS, JWT authentication, and cloud-native patterns to deliver scalable, maintainable services.

Core Features & Use Cases

Minimal APIs & CQRS: Lightweight endpoints with MediatR and clean separation of concerns
EF Core & Migrations: Robust data access with migrations and patterns
Authentication & Authorization: JWT-based security and policy-driven access
Cloud-Native: Docker, health checks, configuration management, and observability

Quick Start

Create a minimal API project with EF Core and JWT authentication and expose a /health endpoint.

Frequently Asked Questions about dotnet-core-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I build a scalable .NET 8 application with minimal APIs?▼

Minimal APIs in .NET 8 let you create lightweight endpoints without controllers. Use Entity Framework Core for data access, implement CQRS with MediatR for clean separation of concerns, add JWT authentication for security, and configure OpenAPI/Swagger documentation to build scalable, maintainable services.

What's the best way to implement clean architecture in .NET 8?▼

Clean architecture in .NET 8 separates concerns across layers: use minimal APIs for endpoints, MediatR for command/query handling, Entity Framework Core for persistence, and dependency injection for loose coupling. Apply record types for DTOs, enable nullable reference types, and write integration tests to validate your design.

How do I add JWT authentication and authorization to a .NET 8 API?▼

Implement JWT authentication by configuring bearer token validation in your minimal API, defining authorization policies, and validating tokens on protected endpoints. .NET 8's built-in authentication middleware handles token verification, and policy-driven access control enforces role and claim-based authorization.

Can I use Entity Framework Core with CQRS and MediatR in .NET 8?▼

Yes. Use Entity Framework Core for all data access operations, implement command handlers via MediatR for writes and query handlers for reads, and inject DbContext through dependency injection. This pattern separates read and write concerns while maintaining a single data access layer.

What cloud-native patterns should I implement in my .NET 8 microservice?▼

Deploy .NET 8 apps in Docker containers, expose health check endpoints for orchestration, externalize configuration via environment variables, enable structured logging for observability, and use async/await throughout for efficient resource use in cloud-native environments.

Do I need C# 12 features and nullable reference types for modern .NET 8 development?▼

Nullable reference types catch null-reference bugs at compile time and are recommended for maintainability. C# 12 features like primary constructors and collection expressions reduce boilerplate in .NET 8 projects, but aren't strictly required—adopt them to align with clean architecture best practices.