What problem does it solve? Writing consistent, correct validation logic in CoreEx-based .NET applications requires knowing which base class to use, how to chain rules, and how to handle async database checks — this Skill guides that entire workflow so validators follow CoreEx conventions every time. ## Core Features & Use Cases - Base class selection: Chooses between Validator<T, TSelf> (no injection), Validator<T> (constructor injection), and AbstractValidator<T, TSelf> (FluentValidation-style syntax) based on your needs. - Rule authoring: Covers mandatory fields, ref-data validation with .IsValid(), comparison rules, precision/scale, conditional rules (WhenEntity, WhenValue, DependsOn), and nested entity, collection, and dictionary validators. - Async validation: Implements OnValidateAsync overrides with context.HasErrors guards for database lookups and cross-field checks. - Use Case: You need a validator for a Product contract that checks SKU length, validates a ref-data category, and asynchronously confirms products exist in the database — the Skill scaffolds the validator, wires the async check, and generates the matching unit test class. ## Quick Start Ask the AI to create a CoreEx validator for your contract type, listing the properties to validate and any async database checks needed.