dotnet-architect

Design and validate .NET backend architecture for ASP.NET Core production services.

Updated May 5, 2026
One-click install
npx skills add https://github.com/Movchanets/Microservices_Learning --skill dotnet-architect-movchanets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-architect
Source: https://github.com/Movchanets/Microservices_Learning/tree/main/.agents/skills/dotnet-architect
Command: npx skills add https://github.com/Movchanets/Microservices_Learning --skill dotnet-architect-movchanets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design, review, and improve enterprise .NET backends so they are maintainable, scalable, testable, and ready for production.

Core Features & Use Cases

  • Architecture Guidance: Shape clean, modular ASP.NET Core services with strong boundaries and clear responsibilities.
  • Data Access & Performance: Choose and tune EF Core, Dapper, caching, and query patterns for reliable throughput.
  • Microservices Delivery: Apply DDD, CQRS, messaging, authentication, testing, and deployment practices to real service architectures.
  • Use Case: Use it when planning a new API, reviewing a service for bottlenecks, or deciding how to structure a microservices platform.

Quick Start

Ask the skill to evaluate your .NET service architecture and recommend practical improvements for implementation, testing, and deployment.

Frequently Asked Questions about dotnet-architect

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

FAQPage Schema
How do I design a .NET microservices architecture using clean architecture and CQRS?

Structure ASP.NET Core microservices with DDD and CQRS by establishing bounded contexts, separating commands from queries, and using messaging patterns to ensure clear responsibilities and maintainable production backends.

What's the best way to choose between EF Core and Dapper for data access in ASP.NET Core?

Choose between EF Core and Dapper by evaluating query complexity and throughput needs, tuning query patterns and caching strategies to achieve reliable performance in your .NET backend data access layers.

How do I review an existing ASP.NET Core API for architectural bottlenecks?

Review an ASP.NET Core API for bottlenecks by evaluating service boundaries, data access layers, and authentication workflows, then validating clean architecture practices to recommend targeted performance improvements.

Does this .NET architecture guidance apply to cloud-native deployment workflows?

Yes, the .NET architecture guidance applies to cloud-native deployment workflows by validating testing, authentication, and messaging practices to ensure your ASP.NET Core services are production-ready and scalable.

When should I apply DDD and CQRS patterns in a .NET backend?

Apply DDD and CQRS patterns in a .NET backend when designing microservices that require strict boundaries, complex domain logic, and clear separation between read and write operations for scalable service architectures.