application-dotnet

Configure CQRS dispatcher and handler dependency injection for ASP.NET Core projects.

12|2|Updated May 4, 2020
One-click install
npx skills add https://github.com/hoangnh2412/jarvis --skill application-dotnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: application-dotnet
Source: https://github.com/hoangnh2412/jarvis/tree/main/.opencode/skills/application-dotnet
Command: npx skills add https://github.com/hoangnh2412/jarvis --skill application-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the tedious manual work of configuring CQRS dispatchers, registering command/query handlers, and setting up the Application layer for ASP.NET Core projects using the Jarvis Clean Architecture framework, ensuring consistent architecture adherence without repetitive boilerplate code.

Core Features & Use Cases

  • CQRS Dispatcher Registration: Automates setup of ICommandDispatcher and IQueryDispatcher for Jarvis.Application.
  • Handler Workflows: Provides step-by-step guides and code templates for creating and registering command/query handlers with proper dependency injection scoping.
  • Use Case: .NET development teams building backend services with Jarvis can reduce Application layer setup time from hours to minutes while avoiding common anti-patterns like circular dependencies or missing DI registrations.

Quick Start

Use the application-dotnet skill to initialize the Jarvis.Application CQRS configuration for your .NET project's Application layer and register your first command handler.

Frequently Asked Questions about application-dotnet

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

FAQPage Schema
How do I set up CQRS dispatchers in ASP.NET Core without writing boilerplate DI code?

You can set up CQRS dispatchers in ASP.NET Core by using a framework-specific skill to automate the registration of ICommandDispatcher and IQueryDispatcher, eliminating manual dependency injection configuration for your Application layer.

What is the best way to register command and query handlers in a Jarvis Clean Architecture project?

Registering command and query handlers in a Jarvis Clean Architecture project is best handled by automating dependency injection scoping to ensure adherence to the framework's single-direction dependency rules and avoid circular dependencies.

How do I initialize the Application layer for a .NET backend service using CQRS?

Initializing the Application layer for a .NET backend service involves configuring the CQRS dispatcher and creating command/query handlers with proper DI scoping, which can be automated to reduce setup time from hours to minutes.

Can I use this CQRS configuration approach for any ASP.NET Core project?

This CQRS configuration approach applies specifically to ASP.NET Core projects using the Jarvis Clean Architecture framework, ensuring consistent architecture adherence and proper integration of the Jarvis.Application component.

Why does my .NET CQRS setup have circular dependencies or missing DI registrations?

Circular dependencies or missing DI registrations in .NET CQRS setups often occur when manual configuration violates single-direction dependency rules, an issue preventable by automating handler registration and dispatcher setup.

What is Jarvis.Application and when do I need it for .NET development?

Jarvis.Application is a component of the Jarvis Clean Architecture framework needed when building .NET backend services that require structured CQRS dispatcher integration and command/query handler management.