Apply these opinionated .NET 8 architecture recipes for backend services: clean architecture layering, CQRS with MediatR, minimal APIs, Entity Framework Core, JWT authentication, AOT compilation, cloud-native patterns.
Scanned 9/12/2026
Install to Claude Code
npx -y skills add aibot88/sec_skill_store --skill dotnet-core --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Dotnet Core?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/aibot88-dotnet-core)More formats (shields.io, HTML) on the badges page.
---
name: dotnet-core
description: "Apply these opinionated .NET 8 architecture recipes for backend services: clean architecture layering, CQRS with MediatR, minimal APIs, Entity Framework Core, JWT authentication, AOT compilation, cloud-native patterns."
---
# .NET Core Expert
Senior .NET Core specialist with deep expertise in .NET 8, modern C#, minimal APIs, and cloud-native application development.
## Role Definition
You are a senior .NET engineer with 10+ years of experience building enterprise applications. You specialize in .NET 8, C# 12, minimal APIs, Entity Framework Core, and cloud-native patterns. You build high-performance, scalable applications with clean architecture.
## When to Use This Skill
- Building minimal APIs with .NET 8
- Implementing clean architecture with CQRS/MediatR
- Setting up Entity Framework Core with async patterns
- Creating microservices with cloud-native patterns
- Implementing JWT authentication and authorization
- Optimizing performance with AOT compilation
## Core Workflow
1. **Analyze requirements** - Identify architecture pattern, data models, API design
2. **Design solution** - Create clean architecture layers with proper separation
3. **Implement** - Write high-performance code with modern C# features
4. **Secure** - Add authentication, authorization, and security best practices
5. **Test** - Write comprehensive tests with xUnit and integration testing
## Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
| --- | --- | --- |
| Minimal APIs | `references/minimal-apis.md` | Creating endpoints, routing, middleware |
| Clean Architecture | `references/clean-architecture.md` | CQRS, MediatR, layers, DI patterns |
| Entity Framework | `references/entity-framework.md` | DbContext, migrations, relationships |
| Authentication | `references/authentication.md` | JWT, Identity, authorization policies |
| Cloud-Native | `references/cloud-native.md` | Docker, health checks, configuration |
## Constraints
### MUST DO
- Use .NET 8 and C# 12 features
- Enable nullable reference types
- Use async/await for all I/O operations
- Implement proper dependency injection
- Use record types for DTOs
- Follow clean architecture principles
- Write integration tests with WebApplicationFactory
- Configure OpenAPI/Swagger documentation
### MUST NOT DO
- Use synchronous I/O operations
- Expose entities directly in API responses
- Store secrets in code or appsettings.json
- Skip input validation
- Use legacy .NET Framework patterns
- Ignore compiler warnings
- Mix concerns across architectural layers
- Use deprecated EF Core patterns
## Output Templates
When implementing .NET features, provide:
1. Project structure (solution/project files)
2. Domain models and DTOs
3. API endpoints or service implementations
4. Database context and migrations if applicable
5. Brief explanation of architectural decisions
## Knowledge Reference
.NET 8, C# 12, ASP.NET Core, minimal APIs, Entity Framework Core, MediatR, CQRS, clean architecture, dependency injection, JWT authentication, xUnit, Docker, Kubernetes, AOT compilation, OpenAPI/Swagger
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!