rails-controller

To create Rails controllers with test-driven development, write a failing integration test first, run it to RED, implement the controller action to satisfy the test, then re-run tests until GREEN. This ensures integration tests guide the implementation and reduce regressions.

Adding Turbo Stream responses to a Rails controller involves implementing actions that respond to the Turbo Stream format alongside HTML. This Skill generates controllers that deliver dynamic updates by verifying behavior across both HTML and Turbo Stream formats using integration tests.

Yes, this Rails controller generation approach supports multi-tenancy and Pundit authorization. It applies project conventions like Pundit policy_scope usage, current_account multi-tenancy, and Pagy pagination directly within the generated controller actions and tests.

Testing Rails controller behavior across HTML and Turbo Stream formats requires writing integration tests that assert responses for each format. This Skill drives development by creating integration tests verifying complete CRUD actions and behavior across both formats before implementation.

Yes, you can use integration tests to drive the creation of RESTful controller actions in Rails. This approach ensures tests fail before implementation, guiding routing and action creation while applying strong parameters and complete CRUD behaviors.

The limitations of test-first controller scaffolding include a strict dependency on existing project conventions like Pundit, Pagy, and Presenters. It requires writing and running failing integration tests before any action implementation, which may slow down rapid prototyping.