backend-conventions

Name: backend-conventions
Availability: InStock
Author: foxsilou

Establish backend coding conventions for C# projects with CQRS rules.

Updated Apr 1, 2026

Search Tags:#tdd #csharp #conventions #dotnet #error-handling #coding-standards #time-provider

Ready to run

npx skills add https://github.com/FoxSilou/ConfigurationClaude --skill backend-conventions-foxsilou

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backend-conventions
Source: https://github.com/FoxSilou/ConfigurationClaude/tree/main/backend/.claude/skills/backend-conventions
Command: npx skills add https://github.com/FoxSilou/ConfigurationClaude --skill backend-conventions-foxsilou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies the backend coding conventions, ensuring consistent naming, error handling, and test double practices across C# projects.

Core Features & Use Cases

Naming conventions: French ubiquitous language for domain code and English for infrastructure code.
Error handling & testing: global error handling strategy, and test double conventions (fakes/stubs) to support TDD and clean architecture.
Architectural guidance: strict CQRS guidance, repository naming, and ADR documentation practices; use of DateTimeOffset and TimeProvider for time.
Practical example: apply conventions when creating domain types, commands, queries, repositories, or services.

Quick Start

Apply these conventions to any new or updated backend code to ensure consistent design and testability.

Frequently Asked Questions about backend-conventions

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

FAQPage Schema

What are standard C# backend coding conventions for domain and infrastructure boundaries?▼

C# backend coding conventions separate naming by layer: French ubiquitous language for domain code and English for infrastructure code. This boundary separation ensures clear architectural alignment and consistent communication across domain, application, and infrastructure layers.

How do I handle time and null values in C# domain design?▼

Handle time and null values in C# domain design by using DateTimeOffset for all timestamps and TimeProvider for time abstraction. Apply a strict no-null domain design to eliminate null reference exceptions and enforce robust domain invariants.

How to structure test doubles for TDD in C# clean architecture?▼

Structure test doubles for TDD in C# clean architecture by using fakes and stubs rather than mocks. This test double convention supports global error handling strategies and ensures reliable, maintainable unit tests across domain and application layers.

Does this C# coding standard support CQRS architectural patterns?▼

Yes, this C# coding standard supports CQRS architectural patterns by providing strict CQRS guidance. It defines specific conventions for creating commands, queries, and repositories to maintain clear separation between read and write operations.

What is the best way to document architectural decisions in C# projects?▼

The best way to document architectural decisions in C# projects is through ADR documentation practices. This skill establishes ADR conventions to record design choices, ensuring traceability and consistent architectural alignment across backend development teams.