0026-laravel-controller-cleanup

What problem does it solve?

Laravel controllers can grow bloated when they handle authorization, validation, and business logic in one place, making routes harder to maintain and test.

Core Features & Use Cases

• Move auth/validation into Form Requests: Centralize authorization and validation rules in dedicated Request classes so controller methods stay orchestration-only.
• Extract business logic to Actions/Services with DTOs: Encapsulate one responsibility per Action or a larger workflow per Service, passing DTOs to avoid leaking framework concerns.
• Prefer resource or single-action controllers: Use resource controllers for standard CRUD and invokable controllers for single-purpose endpoints.

Quick Start

Ask an AI to refactor the target controller by extracting validation into a Form Request, moving the core logic into an Action/Service that receives a DTO, and converting the controller to the appropriate resource or invokable style.