dotnet-architect

Design and validate 3-layer .NET 9 architectures with Web API, Razor Pages, and Shared library.

Updated Nov 30, 2025
One-click install
npx skills add https://github.com/gabrielsan90/FacturacionV2 --skill dotnet-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-architect
Source: https://github.com/gabrielsan90/FacturacionV2/tree/main/.claude/skills/dotnet-architect
Command: npx skills add https://github.com/gabrielsan90/FacturacionV2 --skill dotnet-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and validate 3-layer enterprise architectures for .NET 9 systems.

Core Features & Use Cases

  • Design, validate and implement Backend API, Frontend Razor Pages, and Shared library structures.
  • Enforce repository and unit-of-work patterns, action-based responses, and dependency injection.
  • Provide scaffolding guidance for new projects and architecture reviews.

Quick Start

Use this skill to blueprint and assess a new .NET 9 solution against the recommended 3-layer structure.

Frequently Asked Questions about dotnet-architect

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

FAQPage Schema
How do I validate a .NET 9 solution against a 3-layer architecture?

Validate your .NET 9 solution by reviewing its Backend Web API, Frontend Razor Pages, and Shared library structures to ensure they satisfy 3-layer architecture requirements. This includes checking for proper repository and unit-of-work patterns.

What is the recommended 3-layer structure for enterprise .NET 9 systems?

The recommended 3-layer structure for enterprise .NET 9 systems consists of a Backend Web API, Frontend Razor Pages, and a Shared library. This setup enforces repository and unit-of-work patterns, action-based responses, and dependency injection across the layers.

How do I scaffold a new .NET 9 project using repository and unit-of-work patterns?

Scaffold a new .NET 9 project by blueprinting the solution against the recommended 3-layer structure. This provides guidance to implement Backend API, Frontend Razor Pages, and Shared libraries while enforcing repository and unit-of-work patterns.

Does this architecture approach work with Razor Pages and async data access?

Yes, this architecture approach works with Razor Pages and async data access. It validates 3-layer enterprise architectures for .NET 9 systems and ensures async data access is properly implemented across the Backend Web API and Shared library structures.

Why do I need ActionResponse and dependency injection in my .NET 9 architecture?

You need ActionResponse and dependency injection in your .NET 9 architecture to satisfy the structural requirements of a clean 3-layer enterprise system. Enforcing these patterns standardizes action-based responses and decouples dependencies across Backend API and Frontend Razor Pages.