dotnet-clean-architecture

Personal conventions for building .NET / ASP.NET Core backend services the way I build them: Clean Architecture in 4 layers, the FoundationKit library (BaseRepository / BaseService / BaseResponse), event-driven microservices over RabbitMQ, HybridCache, and FluentValidation. Use this skill WHENEVER working on a .NET/C# backend in this style — creating or editing controllers, services, repositories, DTOs, validators, DbContext, EF Core entities, event handlers, caching, or DI wiring. Also trigger it whenever the user mentions FoundationKit, BaseService, BaseMapService, BaseRepository, BaseResponse/Result, an event handler, or asks to "scaffold a CRUD endpoint", "add an entity", "wire up messaging", "follow my conventions", or "my style". Apply proactively even when the user doesn't name the skill explicitly — if the file is a .cs backend file in a layered solution, these conventions apply.