fluent-validation-migrate-messages

To migrate Laravel FormRequest messages, this Skill rewrites the messages() array overrides into inline message named arguments directly on the rule chain in rules(), removing the messages() method when all keys are portable.

During Fluent Validation migration, non-portable translation keys remain in the messages() method with a comment stub for manual review, ensuring complex patterns and translation wrappers are preserved or flagged.

Yes, you can inline FormRequest messages for rules inside each() blocks, nested arrays, and conditional when() closures, applying the message named args directly to the specific rule chain.

The best way to handle complex validation patterns is to use a dry-run to locate targets, apply inlining for portable keys, and leave unportable complex patterns in messages() for manual review.

Some Laravel FormRequest validation messages are left behind because they contain non-portable entries or complex translation wrappers that cannot be safely converted into inline message named arguments.

Migrating to inline Fluent Validation messages removes the messages() method entirely only when all message keys successfully port to the rule chain; non-portable entries remain in the method.