action-controller-best-practices

To refactor a Rails controller with complex business logic, this Skill extracts lengthy action logic into design patterns like service objects, query objects, and form objects to restore the "thin controller" principle and improve maintainability.

You should extract service objects from Rails controllers when actions exceed approximately ten lines, contain multiple business rules, or include custom non-RESTful actions that make the file difficult to understand and maintain.

The best way to organize a Rails controller with filtering and sorting logic is to apply query objects and presenters, moving the heavy data retrieval and presentation logic out of the controller actions into dedicated, reusable classes.

Yes, you can use controller concerns to slim down large Rails controller files. This Skill applies concerns alongside form objects and service objects to break down complex controllers into clean, manageable components.

Yes, this Rails controller refactoring approach explicitly handles non-RESTful actions by extracting their custom logic into appropriate design patterns such as service objects, ensuring the controller remains clean and organized.