dotnet

Standardize ASP.NET Core backend architecture and patterns for enterprise services.

4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/leocosta/octopus --skill dotnet-leocosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet
Source: https://github.com/leocosta/octopus/tree/main/skills/dotnet
Command: npx skills add https://github.com/leocosta/octopus --skill dotnet-leocosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly provides a structured, best-practice guide for building .NET backends in ASP.NET Core, unifying patterns across API design, data access, validation, and dependency injection to accelerate development and ensure maintainable code.

Core Features & Use Cases

  • Guided ASP.NET Core Architecture: Standard patterns for Minimal APIs and Controllers, organized project structure, and consistent coding standards.
  • EF Core & Data Access: Recommended DbContext patterns, async data access, and configuration conventions.
  • DI, Validation & CQRS: Dependency injection guidelines, FluentValidation patterns, and MediatR usage to separate concerns.
  • Practical Examples: Code snippets and decision trees to choose between architectures for common scenarios.

Quick Start

Ask the AI for a starter ASP.NET Core project blueprint that follows the standard .NET backend patterns.

Frequently Asked Questions about dotnet

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

FAQPage Schema
What's the best way to structure an ASP.NET Core backend project for enterprise development?

ASP.NET Core project structure is standardized by enforcing consistent organization for API design, data access, and dependency injection to ensure maintainable enterprise code. It provides decision trees and practical code snippets to choose architectures for common scenarios.

How do I implement CQRS with MediatR in a .NET backend service?

Implement CQRS with MediatR in .NET backends by using the skill's dependency injection guidelines and pattern selection logic to separate concerns effectively. It standardizes MediatR usage alongside FluentValidation patterns to enforce a consistent architecture across refactored services.

What are the recommended EF Core data access patterns for ASP.NET Core APIs?

Recommended EF Core data access patterns for ASP.NET Core include async data access operations and specific DbContext configuration conventions. The skill standardizes these data access patterns to unify backend architecture and accelerate development across new and refactored services.

How do I set up dependency injection and FluentValidation in ASP.NET Core?

Set up dependency injection and FluentValidation in ASP.NET Core by applying the skill's specific guidelines for configuring DI and enforcing validation patterns. It unifies these concerns across your backend services to maintain consistent coding standards and support enterprise development.

Does this .NET architecture guidance apply to both Minimal APIs and Controllers?

Yes, the .NET architecture guidance applies to both Minimal APIs and Controllers. It provides standard patterns for both approaches, helping you decide between architectures for common scenarios when building or refactoring ASP.NET Core backend services.

When should I use specific .NET backend patterns over others for API design?

Decide when to use specific .NET backend patterns by utilizing the skill's decision trees to choose between architectures for common API design scenarios. It standardizes pattern selection across new and refactored services requiring architecture decisions, ensuring practical and maintainable implementations.