Validate C# input models with layered validation boundaries in ASP.NET Core.
npx skills add https://github.com/CloudyWing/ai-dotfiles --skill csharp-validation
Please help me install this Agent Skill. Skill: csharp-validation Source: https://github.com/CloudyWing/ai-dotfiles/tree/main/skills/csharp-validation Command: npx skills add https://github.com/CloudyWing/ai-dotfiles --skill csharp-validation
This skill provides clear, production-oriented guidance to eliminate inconsistent or misplaced input validation in C# applications by defining distinct responsibilities for format validation, business-rule checks, and domain invariants and by prescribing framework-specific integration patterns.
Ask the skill to review a request model and return recommended DataAnnotations or a FluentValidation validator with Traditional Chinese error messages and integration notes for ASP.NET Core.
High-intent search queries and answers about installing and using this skill.
C# input validation should be split across layers: use model binding for format checks, the service layer for business rules, and domain constructors for invariant guards. This prevents duplication and maintains boundaries.
Choose FluentValidation or DataAnnotations based on project complexity, but never mix them within the same validation layer. This framework selection rule ensures consistent validation logic and avoids conflicting model binding checks.
For Minimal API integration, apply endpoint filters to execute FluentValidation checks before processing. You must also follow proper validator registration conventions and define consistent error message conventions for failed requests.
To enforce consistent Traditional Chinese error messages, define explicit message conventions within DataAnnotations or FluentValidation validators. This ensures consistent Traditional Chinese error messages across all ASP.NET Core validation layers.
Over-defensive validation causes unnecessary repeated checks throughout the domain model. Limit validation to constructor guards for domain invariants and perform boundary checks once at system entry points to avoid redundancy.
SaiyedMuhammadAnasMaududiblueprint for designing/maintaining complex business applications with a focus on maintainability and testability through separation of concerns and strict dependency rules. It leverages the concept of layers, where the core business logic is isolated from external details like databases and user interfaces. The result is code that is modular, easier to debug and evolvebba.
OkashanadeemEnforce REST API design principles and RFC 7807 error responses.
microsoftConvert ASP.NET MVC global filters to ASP.NET Core middleware and filter pipeline.
alexsandrocruzProvide reusable FluentValidation patterns for ABP DTO validation.
