skills.rest
matteobortolazzo
matteobortolazzoCOMMUNITY
Explore all skills by this author →
GitHub

stack-dotnet

Enforce consistent ASP.NET Core backend conventions across C# projects.

1|Updated Mar 24, 2026
Search Tags:#csharp#dotnet#xunit#entity-framework#aspnet#fluentassertions#webapplicationfactory
One-click install
npx skills add https://github.com/matteobortolazzo/claude-tools --skill stack-dotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stack-dotnet
Source: https://github.com/matteobortolazzo/claude-tools/tree/main/ccflow/skills/stack-dotnet
Command: npx skills add https://github.com/matteobortolazzo/claude-tools --skill stack-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes .NET backend conventions, patterns, and test infrastructure to reduce replication, drift, and onboarding time for C# projects.

Core Features & Use Cases

  • Guidance on ASP.NET Core project structure, DI setup, middleware, and controller patterns.
  • Ready-to-use test scaffolding with xUnit and FluentAssertions, including WebApplicationFactory usage and EF in-memory testing.
  • Best practices for NuGet management, dotnet CLI workflows, and maintainable integration tests.

Quick Start

Configure a new ASP.NET Core API project with xUnit tests and EF in-memory testing to enforce backend conventions.

Frequently Asked Questions about stack-dotnet

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

FAQPage Schema
How do I enforce consistent ASP.NET Core project structure and conventions across a team?▼

You can enforce ASP.NET Core project conventions by applying standardized layouts, DI configuration, middleware patterns, and controller structures to reduce drift and onboarding time for C# backend projects.

What is the best way to scaffold xUnit integration tests for an ASP.NET Core API with Entity Framework?▼

The best way to scaffold API integration tests is using xUnit with FluentAssertions, WebApplicationFactory for bootstrapping the test server, and EF in-memory database for isolated testing.

Does this .NET backend convention guidance support WebApplicationFactory and in-memory EF testing?▼

Yes, it supports WebApplicationFactory and in-memory EF testing by providing ready-to-use test scaffolding that integrates xUnit and FluentAssertions for maintainable ASP.NET Core integration tests.

Can I use these conventions for an existing ASP.NET Core project using Entity Framework and xUnit?▼

Yes, you can apply these conventions to existing C#/.NET projects using ASP.NET Core, Entity Framework, and xUnit to standardize DI setup, controller patterns, and test infrastructure.

What are the limitations of using in-memory Entity Framework for ASP.NET Core integration testing?▼

The metadata focuses on enforcing EF in-memory testing conventions and does not detail specific limitations, but in-memory databases generally lack relational provider features like transactional consistency and constraints.

Why should I standardize .NET backend conventions and test scaffolding across my API projects?▼

Standardizing .NET backend conventions reduces replication, drift, and onboarding time by enforcing consistent project layouts, DI configuration, controller patterns, and xUnit test scaffolding across C# teams.

Related Skills

Explore More Software Engineering Skills→
jim60105jim60105
21

csharp-project-init

Initialize C# ASP.NET Core Web API projects with Entity Framework Core and configuration files.

Community
Intermediate
zenbuappszenbuapps

aibdd.auto.csharp.it.starter

Generate a C# integration test project skeleton from templates with placeholder replacement.

Official
Advanced
roberfloroberflo
1

aspnet-testing

Guide ASP.NET Core testing with xUnit, Moq, FluentAssertions, and WebApplicationFactory.

Community
Advanced
JamkrisJamkris
86

csharp-testing

Automate C# and .NET testing with xUnit, FluentAssertions, and mocking frameworks.

Community
Advanced