How does this skill handle business logic?

It enforces 'Thin Controllers' by delegating all business logic to intention-revealing model methods and ActiveSupport concerns, ensuring controllers only handle request/response flow.

Does this skill support the latest Rails features?

Yes, it specifically promotes Rails 8+ patterns, such as using params.expect() instead of the older require/permit syntax for strong parameters.

Why should I avoid custom actions like post :close?

Custom actions break the standard RESTful pattern and lead to bloated, hard-to-maintain controllers. Treating state changes as resources keeps your routing clean and your logic modular.

What is the 37signals pattern for controllers?

It is a philosophy where every state change (like archiving or pinning) is modeled as its own resource with a dedicated controller, typically using only create and destroy actions.

Vanilla Rails Controllers

Name: Vanilla Rails Controllers
Author: ZempTime

byZempTime

•

API Development

Enforces the RESTful 'State as Resource' pattern in Ruby on Rails to eliminate custom controller actions and improve maintainability.

About

This skill guides developers in implementing the 37signals-inspired 'Vanilla Rails' approach to controllers, where model state changes—such as closing, archiving, or pinning—are treated as first-class resources rather than custom routes. By enforcing CRUD operations on specific resource controllers and delegating business logic to model concerns, it ensures a clean, RESTful architecture. It also implements Rails 8+ best practices, including the use of params.expect() and standardized migration patterns for state tracking.

Key Features

Thin controller enforcement with model-level delegation
Resource extraction pattern for model state changes
Templates for common state patterns like archival and publication
Standardized Rails 8+ params.expect() implementation
1 GitHub stars
Automated migration patterns for state-tracking join tables

Use Cases

Implementing auditable state transitions (who changed what and when) using resource controllers
Modernizing legacy Rails applications to follow Rails 8+ best practices and RESTful conventions
Refactoring bloated Rails controllers containing numerous custom member routes

About

Key Features

Thin controller enforcement with model-level delegation
Resource extraction pattern for model state changes
Templates for common state patterns like archival and publication
Standardized Rails 8+ params.expect() implementation
1 GitHub stars
Automated migration patterns for state-tracking join tables

Use Cases

Implementing auditable state transitions (who changed what and when) using resource controllers
Modernizing legacy Rails applications to follow Rails 8+ best practices and RESTful conventions
Refactoring bloated Rails controllers containing numerous custom member routes