vanilla-rails-controllers

What problem does it solve?

Rails projects often accumulate ad hoc controller actions that mutate model state. This skill advocates treating state transitions as distinct resources, guiding you to extract state logic into resource-based controllers and keep business logic in models.

Core Features & Use Cases

• Resource-based state changes: convert each state transition (close, archive, publish, assign) into its own controller resource.
• Clear separation: controllers delegate to well-named model methods, reducing fat controllers and duplicated logic.
• Consistent routing patterns: use singular or plural resources to represent entering and leaving a state, with straightforward testability.

Quick Start

Define a new state resource for a model (for example, a closure state for a Card), add a matching controller under Cards::ClosuresController, and implement create to enter the state and destroy to leave it by invoking the corresponding model methods.