fluent-validation-optimize

You can optimize Laravel validation performance by scanning your project to identify string rules convertible to fluent chains, missing HasFluentRules traits, and wildcard patterns, then applying recommended transformations for faster validation execution and improved DX.

The best way to convert string validation rules to fluent rules is by scanning your FormRequests and custom Validators for convertible patterns, then using a step-by-step migration plan with risk flags to safely transform string rules into fluent rule chains.

Yes, the laravel-fluent-validation package must be installed before running the optimization workflow, as the Skill scans code for HasFluentRules usage and proposes transformations based on that specific package's fluent rule capabilities.

Converting Laravel validation attributes and messages to labels and inline messages improves DX by replacing separate message arrays with inline alternatives, grouping repeated keys with each(), and simplifying deeply nested validation trees using children().

Yes, you can use this workflow on deeply nested arrays because it scans for nested dot-notation keys and wildcard rules, proposing each() grouping and children() transformations to streamline complex nested validation structures safely.

The main risk when migrating to fluent validation rules involves potential pattern mismatches during transformation, which is why the Skill provides a step-by-step plan with explicit risk flags to guide safe migrations across FormRequests and custom Validators.