What problem does it solve? When building Next.js server actions with next-safe-action, developers struggle to return, shape, and display validation errors consistently—especially when combining automatic schema validation with manual business-rule checks like "email already taken". ## Core Features & Use Cases - Manual Validation Errors: Use returnValidationErrors to throw field-level, form-level, and nested-object errors from server code after schema validation passes. - Error Shape Control: Switch between formatted (nested _errors) and flattened (formErrors/fieldErrors) shapes globally, per-action, or with fully custom shapes via handleValidationErrorsShape. - Throwing Mode: Enable throwValidationErrors to raise ActionValidationError instead of returning errors in the result object. - Use Case: In a registration form, check whether an email is already registered in the database, return a field-level error, and render it under the email input in the client component. ## Quick Start Ask the AI to add a returnValidationErrors check to your next-safe-action server action and display the resulting field errors in your React form.