find-dotnet-skills

name	find-dotnet-skills
description	Discover and navigate the available .NET enterprise skills in this project. Use when user says "what skills are available", "find skill", "list skills", "which skill should I use", or asks about .NET skill capabilities. Do NOT use for general "help me with" requests unrelated to skill discovery. Remind that API/Minimal API work uses dotnet-api-endpoint, not dotnet-mvc, unless the user explicitly chose MVC/Razor.
metadata	{"author":"Claude-DotNet-Ultimate","version":"1.2.0","category":"discovery","license":"MIT"}

.NET Enterprise Skills Directory

API vs MVC (this repository — important)

• Default: This solution is API-first (src/Api/, Minimal APIs). For new endpoints, features, and reviews, use dotnet-api-endpoint, dotnet-cqrs-feature, dotnet-ddd-entity, etc.
• dotnet-mvc is opt-in only. Use it only when the user explicitly wants MVC, Razor, Views, server-rendered UI, or a separate MVC project — not when they chose or are building an API only.
• If unclear, assume API for this repo and do not load dotnet-mvc unless the user corrects the assumption.

User / project context	Use	Do not use
REST / Minimal API / src/Api/Endpoints/	dotnet-api-endpoint + CQRS skills	dotnet-mvc
New feature on existing API codebase	dotnet-api-endpoint	dotnet-mvc
Explicit "add MVC app", "Razor views", "scaffold Controllers"	dotnet-mvc	(API skills for HTTP in src/Api/ still use dotnet-api-endpoint)

Available Skills

Skill	Use When	Trigger Phrases
dotnet-enterprise	Creating new projects, full architecture setup	"new project", "enterprise", "set up solution"
dotnet-ddd-entity	Creating entities, aggregates, value objects	"create entity", "new aggregate", "value object"
dotnet-cqrs-feature	Adding commands, queries, vertical slices	"add feature", "create command", "new query"
dotnet-api-endpoint	Creating Minimal API routes	"add endpoint", "new route", "REST API"
dotnet-integration-test	Writing unit/integration tests	"write tests", "add test", "testcontainers"
dotnet-domain-event	Domain events + MassTransit consumers	"add event", "create consumer", "MassTransit"
dotnet-ef-migration	EF Core migrations, entity configs	"add migration", "configure table", "EF Core"
dotnet-hybrid-cache	Caching with HybridCache + Redis	"add caching", "Redis", "cache invalidation"
dotnet-code-review	Code quality review	"review code", "PR review", "check quality"
dotnet-docker-deploy	Docker, Aspire, CI/CD	"dockerize", "deploy", "Aspire", "CI/CD"
dotnet-observability	OpenTelemetry, Serilog, metrics	"add logging", "tracing", "monitoring"
dotnet-mvc	Opt-in only: MVC, Razor, Views, server UI — not for API-only	User explicitly: "MVC", "Razor", "Views", AddControllersWithViews

Workflow: Adding a New Feature (API — default for this repo)

When adding a complete new feature (e.g., "Add Product management") on the API stack, use skills in this order:

1. dotnet-ddd-entity — Create the domain entity, value objects, strongly-typed ID
2. dotnet-domain-event — Define domain events for the entity
3. dotnet-ef-migration — Configure EF Core mapping and create migration
4. dotnet-cqrs-feature — Create command/query handlers
5. dotnet-api-endpoint — Expose via Minimal API (src/Api/)
6. dotnet-hybrid-cache — Add caching to queries
7. dotnet-integration-test — Write tests
8. dotnet-code-review — Review the changes

Do not include dotnet-mvc in this workflow unless the user is also (or only) building a separate MVC/Razor UI that consumes or parallels the API.

Workflow: MVC / Razor UI (only when user chose MVC)

Use dotnet-mvc in addition to domain/application skills only when the user is creating or working on a MVC or Razor front end — not for src/Api Minimal API work.

Workflow: Setting Up a New Project

Use dotnet-enterprise which orchestrates all other skills.

Example: Complete Feature Workflow

User Request: "Add Product management to the API"

Skills Used in Order:

1. dotnet-ddd-entity

   • Create Product entity with strongly-typed ProductId
   • Create Money value object for pricing
   • Add business rules (e.g., Product.Activate(), Product.Discontinue())

2. dotnet-domain-event

   • Define ProductCreatedEvent, ProductPriceChangedEvent
   • Raise events from entity methods

3. dotnet-ef-migration

   • Configure ProductConfiguration with Fluent API
   • Map value objects as owned entities
   • Run dotnet ef migrations add AddProduct

4. dotnet-cqrs-feature

   • Create CreateProductCommand + CreateProductHandler
   • Create GetProductQuery + GetProductQueryHandler
   • Add CreateProductValidator with FluentValidation

5. dotnet-api-endpoint

   • Create ProductsEndpoints.cs in src/Api/Endpoints/
   • Map POST /api/products, GET /api/products/{id}
   • Return Result<ProductDto> mapped to HTTP status

6. dotnet-hybrid-cache

   • Add caching to GetProductQueryHandler
   • Configure cache key: product-{id}
   • Set expiration: 5 minutes

7. dotnet-integration-test

   • Write CreateProductTests with Testcontainers
   • Write GetProductTests verifying cache behavior

8. dotnet-code-review

   • Review all changes for DDD compliance
   • Check performance (AsNoTracking, includes)
   • Verify no architectural violations

Result: Complete, tested, production-ready Product feature following all enterprise patterns.

Quick Reference

Project Structure

src/Core/Domain/Entities/          → dotnet-ddd-entity
src/Core/Domain/Events/            → dotnet-domain-event
src/Application/Features/          → dotnet-cqrs-feature
src/Infrastructure/Persistence/    → dotnet-ef-migration
src/Infrastructure/Caching/        → dotnet-hybrid-cache
src/Infrastructure/Messaging/      → dotnet-domain-event
src/Infrastructure/Logging/        → dotnet-observability
src/Api/Endpoints/                 → dotnet-api-endpoint
tests/                             → dotnet-integration-test