dotnet-create-feature

Automates creation of CQRS-based .NET features with Command, Query, Handler and Validator scaffolding.

21|4|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/JotJunior/claude-ai-tips --skill dotnet-create-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-create-feature
Source: https://github.com/JotJunior/claude-ai-tips/tree/main/language-related/dotnet/skills/dotnet-create-feature
Command: npx skills add https://github.com/JotJunior/claude-ai-tips --skill dotnet-create-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a new .NET 10 feature following the CQRS pattern with Command, Query, Handler and Validator to standardize feature scaffolding and accelerate delivery.

Core Features & Use Cases

  • Standard CQRS skeleton generation including immutable Command/Query records, Handlers, Validators, and DTOs.
  • Scaffolds for tests and basic API endpoints or integration points to accelerate feature delivery.
  • Use Case: Create a new feature in a .NET project by generating the core files and wiring up basic infrastructure.

Quick Start

Crie uma nova feature seguindo o padrão CQRS com Command, Query, Handler e Validator para iniciar rapidamente uma nova funcionalidade.

Frequently Asked Questions about dotnet-create-feature

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

FAQPage Schema
How do I generate a CQRS feature skeleton in a .NET project?

To generate a CQRS feature skeleton in a .NET project, you can automate the creation of immutable Command and Query records, Handlers, Validators, and DTOs to standardize scaffolding and accelerate delivery.

What is included in a standard CQRS feature skeleton for clean architecture?

A standard CQRS feature skeleton includes immutable Command/Query records, dependency-injected Handlers, validation rules, DTOs, and scaffolds for tests and basic API endpoints to wire up basic infrastructure.

Can I scaffold both validators and API endpoints when creating a new .NET feature?

Yes, you can scaffold both validators and basic API endpoints when creating a new .NET feature. The generated skeleton includes validation rules and integration points to accelerate feature delivery.

Does this CQRS pattern generation work for enterprise .NET projects?

Yes, this CQRS pattern generation is designed for enterprise .NET projects needing a standardized feature skeleton. It meets requirements for immutable records, dependency-injected handlers, validation rules, and tests.

What's the best way to standardize feature scaffolding across a clean architecture codebase?

The best way to standardize feature scaffolding is to automate the creation of CQRS-based components. This ensures every new feature consistently includes Command, Query, Handler, and Validator files with wired-up infrastructure.

Why use immutable records for commands and queries in .NET CQRS?

Using immutable records for commands and queries in .NET CQRS ensures thread safety and predictable state changes. The generated skeleton enforces this pattern to meet enterprise architecture requirements.