jarvis-dotnet

Scaffold .NET 9 Clean Architecture backend solutions with Jarvis framework integration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually setting up a layered .NET 9 backend with the Jarvis framework requires hours of repetitive work creating projects, configuring dependencies, and wiring layer extensions, with high risk of misconfiguration like incorrect dependency injection ordering or missing package references. This Skill automates the entire setup process to deliver a working, standards-compliant backend solution in minutes.

Core Features & Use Cases

  • Full Solution Scaffolding: Generate a complete 5-layer Clean Architecture .NET 9 solution with all required projects, test projects, layer extensions, and pre-configured Swagger, health checks, and OpenTelemetry from an empty folder.
  • Jarvis Integration for Existing Solutions: Add Jarvis framework packages and correct dependency injection wiring to pre-existing layered .NET solutions without overwriting custom code.
  • Modular Feature Addition: Extend existing Jarvis-backed solutions with optional modules like JWT authentication, Redis caching, or Entity Framework multitenancy via dedicated, guided workflows.
  • Use Case: A developer starting a new e-commerce backend can scaffold a fully functional solution with Swagger accessible via F5 in under 5 minutes, instead of spending hours manually configuring project references, layer extensions, and core middleware.

Quick Start

Use the jarvis-dotnet skill to scaffold a new .NET 9 Clean Architecture backend with Jarvis framework pre-configured, then run the host project to access Swagger and test the ping endpoint.

Frequently Asked Questions about jarvis-dotnet

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

FAQPage Schema
How do I scaffold a .NET 9 Clean Architecture backend without manual project setup?

Scaffolding a .NET 9 Clean Architecture backend is automated by generating a complete 5-layer solution with pre-configured Swagger, health checks, and OpenTelemetry from an empty folder in minutes. This eliminates repetitive project creation, dependency configuration, and layer wiring.

Can I integrate the Jarvis framework into an existing layered .NET solution?

Yes, you can integrate the Jarvis framework into pre-existing layered .NET solutions. The process adds required framework packages and configures correct dependency injection wiring without overwriting your custom code or existing project structures.

How do I add JWT authentication and Redis caching to a running .NET backend?

You can add JWT authentication, Redis caching, or Entity Framework multitenancy to running Jarvis-backed solutions through dedicated guided workflows. These modular feature extensions integrate seamlessly without disrupting the existing Clean Architecture layer boundaries.

Why does my .NET Clean Architecture solution have circular dependencies and incorrect DI ordering?

Incorrect dependency injection ordering and circular dependencies often result from manual layer wiring. Automated scaffolding enforces Clean Architecture layer boundaries and correct dependency injection ordering out-of-the-box, preventing misconfiguration and missing package references.

Does Jarvis .NET scaffolding include Swagger and OpenTelemetry out of the box?

Yes, Jarvis .NET scaffolding includes pre-wired Swagger, health check endpoints, and out-of-the-box OpenTelemetry integration. You can run the host project and access Swagger via F5 immediately after solution generation.

Do I need the .NET 9 SDK to use Jarvis backend scaffolding?

Yes, .NET 9 is required because the scaffolding generates a standardized .NET 9 Clean Architecture backend solution. The automation targets .NET 9 specifically to deliver pre-configured project references and layer extensions.