rails

To build a Rails feature, you plan ActiveRecord domain modeling, wire Turbo Streams for real-time UI updates, and verify changes using RSpec testing patterns. This involves choosing architecture patterns for CRUD development and implementing structured Stimulus JavaScript controllers for interactive frontend updates.

Avoiding N+1 queries in ActiveRecord requires applying query optimization, batching, and safe bulk operations. You should follow evidence-driven verification and anti-pattern safeguards during implementation to ensure unsafe query construction is caught and resolved.

Setting up Turbo Streams in Ruby on Rails involves configuring Turbo Drive and Frames, then applying specific controller and view patterns for real-time UI updates. You pair this with Stimulus controllers to manage interactive features and partial page updates efficiently.

Use service objects instead of ActiveRecord callbacks when you need to prevent callbacks misuse and extract complex domain logic. Choosing appropriate architecture patterns for domain logic helps avoid anti-patterns, ensuring your CRUD development and background jobs remain maintainable and safely queryable.

Yes, this Rails guidance directly applies to Rails 7 and 8 tasks, including deployment architecture patterns for Kamal 2. It covers modern framework-specific implementation details for CRUD development, background jobs, caching strategy selection, and Hotwire UI behavior verification.

Testing ActiveRecord models and Hotwire behavior with RSpec requires applying specific testing patterns and evidence-driven review steps. You generate verification checklists for the critical path, ensuring your domain modeling and real-time UI updates pass RSpec coverage safeguards for correctness.