csharp-dotnet

Implement C# 14 design patterns for .NET 10 applications.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/h4v1d/extension-collection-geminicli --skill csharp-dotnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: csharp-dotnet
Source: https://github.com/h4v1d/extension-collection-geminicli/tree/main/csharp-dotnet
Command: npx skills add https://github.com/h4v1d/extension-collection-geminicli --skill csharp-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides modern, high-performance C# 14 design patterns for .NET 10 projects, enabling clean architecture and productive development.

Core Features & Use Cases

  • Singleton (Thread-Safe): Demonstrates DI-friendly, lazy-initialized singleton usage with minimal boilerplate.
  • Options Pattern: Shows binding configuration to strongly-typed records and DI integration.
  • Factory & Repository Patterns: Provides modern, generic patterns with minimal API-friendly examples.
  • CQRS & Minimal APIs: Presents commands, queries, and Minimal API integration for CLI-oriented apps.
  • Use Case: Example scenario such as configuring a high-throughput service with modular monolith decisions.

Quick Start

Use the skill to generate a thread-safe Singleton in C# 14 with DI, or ask for a Minimal API pattern example.

Frequently Asked Questions about csharp-dotnet

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

FAQPage Schema
How do I implement a thread-safe Singleton in C# 14 with dependency injection?

A thread-safe Singleton in C# 14 uses lazy initialization with minimal boilerplate, integrating directly with dependency injection to ensure DI-friendly and testable architectures without manual locking code.

What is the best way to structure CQRS with Minimal APIs in .NET 10?

The best way to structure CQRS with Minimal APIs in .NET 10 involves separating commands and queries, integrating them directly into endpoint routing for CLI-oriented applications to achieve clean architecture.

How do I use the Options Pattern to bind configuration to strongly-typed records in .NET?

The Options Pattern binds configuration sections to strongly-typed C# 14 records using required members, integrating with dependency injection to provide safe, compile-time validated configuration access.

Does this repository pattern approach work with generic types and Minimal APIs?

Yes, the repository pattern works with generic types and Minimal APIs by using modern C# features like primary constructors and the field keyword to reduce boilerplate in data access layers.

When should I use a modular monolith instead of microservices for high-throughput .NET services?

Use a modular monolith for high-throughput .NET services when you need CLI-centric, clean architecture boundaries without the operational overhead of distributed microservices, leveraging C# 14 patterns.