laravel-actions

Refactoring a large Laravel service class involves breaking monolithic logic into single-purpose action classes. This standardizes business logic into reusable, testable units organized in `app/Actions` or domain-specific directories using verb-led naming conventions.

The one-class-one-task principle in Laravel isolates specific business operations into distinct action classes. This approach enforces single responsibility, container resolvability, and consistent invocation using `::run()` for simplified unit testing and maintenance.

The laravel-actions approach distinguishes action classes from native Laravel Jobs for queued tasks. Actions standardize synchronous business logic execution via `::run()`, while native Laravel Jobs should remain the primary mechanism for handling queued asynchronous operations.

You can use laravel-actions to simplify testing and mocking of business logic. The standardized action classes provide package-native mocking and spying capabilities, making unit and integration testing significantly easier when validating isolated tasks.

You should not use action classes in your PHP application for queued tasks or cross-cutting concerns. Actions are designed for standardizing synchronous business logic, while native Laravel Jobs are better suited for asynchronous queued operations.