backend-standards

Standardize .NET 8 backend development with Clean Architecture and CQRS patterns.

2|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/Oleh-Bashtovyi/Learnix --skill backend-standards-oleh-bashtovyi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-standards
Source: https://github.com/Oleh-Bashtovyi/Learnix/tree/main/.claude/skills/backend-standards
Command: npx skills add https://github.com/Oleh-Bashtovyi/Learnix --skill backend-standards-oleh-bashtovyi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses architectural drift and inconsistency in .NET 8 backend development by providing a centralized, authoritative source for coding standards, CQRS patterns, and layer-specific rules.

Core Features & Use Cases

  • Architectural Governance: Enforces strict separation of concerns between Domain, Application, Infrastructure, and API layers.
  • Standardized Patterns: Provides templates for CQRS handlers, Specification patterns, and Result-based error handling.
  • Operational Checklists: Includes pre-task and post-task checklists to ensure compliance with ADRs, testing requirements, and formatting rules.

Quick Start

Apply the backend-standards skill to review the current implementation of the course creation handler against the defined CQRS and validation patterns.

Frequently Asked Questions about backend-standards

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

FAQPage Schema
How do I enforce clean architecture in .NET 8 applications?

You enforce clean architecture in .NET 8 by applying standardized backend practices that maintain strict separation of concerns between Domain, Application, Infrastructure, and API layers. This prevents architectural drift and ensures consistent layer-specific rules across feature modules.

What is the best way to standardize CQRS handlers and domain entities in .NET?

Standardizing CQRS handlers and domain entities in .NET involves using centralized templates for handlers, Specification patterns, and Result-based error handling. This ensures consistent implementation across feature modules and adherence to architectural decision records.

How do I validate feature compliance with architectural decision records during development?

You validate feature compliance with architectural decision records by applying pre-task and post-task operational checklists. These checklists verify adherence to ADRs, testing requirements, and formatting rules through automated validation pipelines during feature development.

Does this approach work with MediatR for implementing CQRS patterns?

Yes, this approach works with MediatR for implementing CQRS patterns in .NET 8 applications. It facilitates consistent implementation of handlers, domain entities, and infrastructure interfaces across feature modules while maintaining clean architecture standards.

Why does architectural drift occur in backend development and how can I prevent it?

Architectural drift occurs in backend development due to inconsistent implementation of patterns and lack of centralized standards. You prevent it by enforcing strict separation of concerns and providing standardized templates for CQRS handlers, Specification patterns, and Result-based error handling.