Rails Conventions

Apply Rails 7+ conventions for models, controllers, views, and Hotwire patterns.

1|Updated Jan 1, 2026
One-click install
npx skills add https://github.com/betamatt/claude-plugins --skill rails-conventions-betamatt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Rails Conventions
Source: https://github.com/betamatt/claude-plugins/tree/main/ruby-on-rails/skills/rails-conventions
Command: npx skills add https://github.com/betamatt/claude-plugins --skill rails-conventions-betamatt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Rails developers often struggle to apply consistent, production-ready conventions for Rails 7+ across models, controllers, views, and frontend integration with Hotwire.

Core Features & Use Cases

  • Idiomatic Rails 7+ conventions for models, controllers, routes, and views.
  • Hotwire integration guidance including Turbo Frames, Turbo Streams, and Stimulus controllers.
  • Directory structure templates and production patterns for credentials, environment config, initializers, and strong parameters.

Quick Start

Tell me your Rails 7+ project scenario and I will deliver production-grade conventions and a ready-to-apply structure.

Frequently Asked Questions about Rails Conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the production-ready conventions for Rails 7 models, controllers, and views?

Rails 7 conventions enforce consistent naming, directory structure, and configuration patterns across models, controllers, routes, and views. They provide explicit guidance and example templates to ensure production-grade consistency across your application's core modules.

How do I structure Turbo Frames and Turbo Streams with Hotwire in Rails 7?

Hotwire integration patterns in Rails 7 dictate specific conventions for implementing Turbo Frames, Turbo Streams, and Stimulus controllers. These conventions ensure frontend integration aligns with production-ready structural standards and controller logic.

Can I apply these Rails conventions to an existing production project?

Yes, these Rails 7 conventions apply directly to production projects. They deliver ready-to-apply directory layouts, configuration patterns for credentials and environment config, and strong parameter templates suitable for existing codebases.

What is the best way to manage environment config and initializers in Rails 7?

The best way to manage environment config and initializers is by following established Rails 7 production patterns. These conventions provide explicit guidance on directory layouts, credentials management, and initializer configurations for production readiness.

When do I need explicit conventions for Stimulus controllers in a Rails application?

You need explicit conventions for Stimulus controllers when integrating Hotwire frontend functionality in Rails 7. Applying consistent naming and structural conventions ensures your JavaScript controllers integrate seamlessly with Turbo Frames and backend views.