master-dotnet-skill

Builds .NET applications with Clean Architecture and SOLID principles.

Updated Apr 9, 2024
One-click install
npx skills add https://github.com/nhonvo/Powershell --skill master-dotnet-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: master-dotnet-skill
Source: https://github.com/nhonvo/Powershell/tree/main/antigrafity-config/.agent/skills/master-dotnet-skill
Command: npx skills add https://github.com/nhonvo/Powershell --skill master-dotnet-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill standardizes building, refactoring, and optimizing .NET applications using Clean Architecture and SOLID principles, helping teams deliver maintainable and scalable software across domains.

Core Features & Use Cases

  • Architectural guidance across Domain, Application, Infrastructure, and Presentation layers.
  • Enforced coding standards, Async/Await patterns, and Dependency Injection to improve reliability and testability.
  • Use Case: design and implement a new service with well-defined boundaries, testability, and alignment to Clean Architecture.

Quick Start

Start by applying the master-dotnet-skill to scaffold a new Clean Architecture solution and implement a sample domain, application, infrastructure, and API project following the guidelines.

Frequently Asked Questions about master-dotnet-skill

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

FAQPage Schema
How do I structure a .NET application using Clean Architecture and SOLID principles?

To structure a .NET app with Clean Architecture and SOLID principles, separate your code into Domain, Application, Infrastructure, and Presentation layers. This layering ensures scalable domain-driven design, maintainable boundaries, and secure code across projects.

What is the best way to implement CQRS and EF Core in a .NET project?

Implementing CQRS and EF Core in a .NET project involves separating command and query responsibilities within your Application layer. Using Dependency Injection and async patterns ensures robust, testable data operations across your domain boundaries.

Can I use this Clean Architecture framework to refactor an existing .NET service?

Yes, you can refactor an existing .NET service using this Clean Architecture framework. It guides standardizing layers and enforcing practices like Dependency Injection and async programming to improve reliability and testability.

How do I scaffold a new .NET solution with Domain, Application, Infrastructure, and Presentation projects?

To scaffold a new .NET solution with Domain, Application, Infrastructure, and Presentation projects, apply the architectural guidelines to generate well-defined boundaries. This quick start approach aligns your API project to Clean Architecture standards.

Why does my .NET Clean Architecture need Dependency Injection and async patterns?

Your .NET Clean Architecture needs Dependency Injection and async patterns to enforce coding standards and improve reliability. These practices decouple components within the application layer, ensuring maintainable and scalable domain-driven design.