What problem does it solve? Writing custom async validation methods in FluentValidation validators often leads to invented business logic, broken layer boundaries, and infrastructure leakage into application code. This Skill enforces a disciplined workflow where every line of validation logic is traceable to an explicit requirement in the codebase. ## Core Features & Use Cases - Custom Async Validation Implementation: Fills in or corrects custom validation method bodies in existing *Validator.cs files while preserving method signatures and IntentManaged attributes. - Layer Boundary Enforcement: Ensures validators only depend on Domain or Application layer abstractions, never on Entity Framework, Dapper, DbContexts, or other infrastructure types. - Evidence-Based Logic: Requires every validation rule to be traceable to XML documentation, comments, domain rules, value objects, or existing tests, and asks targeted questions when evidence is missing. - Use Case: When implementing a uniqueness check for a CreateCustomerCommand validator, the Skill searches for existing repository abstractions, extends them with an ExistsByAsync-style method if needed, and reports failures via validationContext.AddFailure. ## Quick Start Implement the custom async validation method in my CreateCustomerCommandValidator.cs following the existing domain patterns and repository abstractions.
