agentleFS
G1JoshiG1Joshi/Agent-Skills/skills/frameworks/rails/SKILL.md

rails

Skill15 starsChanged 42 days agoMITView on GitHub

Expert Ruby on Rails assistance covering ActiveRecord, MVC architecture, migrations, background jobs (Sidekiq/SolidQueue), and Hotwire. Use when building full-stack web apps with convention over configuration.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always use strong parameters (params.require(:order).permit(...)) in controllers.

    line 120
  2. Very specific:

    Use includes or strict_loading to prevent N+1 query performance degradation.

    line 121
  3. Distinctive:

    Put business logic or complex database queries inside view templates or controllers.

    line 126
  4. Distinctive:

    Run long-running tasks synchronously inside HTTP controller actions.

    line 127

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ruby on Rails

Ruby on Rails is a full-stack web application framework emphasizing convention over configuration, featuring Active Record ORM, integrated asset bundling, and streamlined deployment tooling.

When to Use

  • High-Velocity Full-Stack Web Development: Building robust SaaS products with convention over configuration.
  • Modern Monoliths with Hotwire / Turbo: Delivering reactive, SPA-like user experiences without heavy frontend frameworks.
  • Database-Driven Business Applications: Leveraging Active Record associations, scopes, and validations.
  • Background Jobs & Real-Time WebSockets: Utilizing Solid Queue, Solid Cache, and Action Cable in Rails 7.2 / 8.

Quick Start

# app/controllers/posts_controller.rb
class PostsController < ApplicationController
  def index
    @posts = Post.all
  end
end

Core Concepts

Active Record Models with Scopes & Validations

Defining business logic and relational constraints:

class Order < ApplicationRecord
  belongs_to :customer
  has_many :line_items, dependent: :destroy

  validates :total_amount, presence: true, numericality: { greater_than: 0 }
  validates :status, inclusion: { in: %w[pending paid shipped canceled] }

  scope :recent, -> { order(created_at: :desc) }
  scope :paid, -> { where(status: 'paid') }

  after_commit :enqueue_fulfillment, on: :create

  private

  def enqueue_fulfillment
    FulfillmentJob.perform_later(id)
  end
end

Hotwire & Turbo Streams for Real-Time Updates

Server-rendered partials pushed over WebSockets or response streams:

# app/controllers/messages_controller.rb
class MessagesController < ApplicationController
  def create
    @message = Message.create!(message_params)

    respond_to do |format|
      format.turbo_stream do
        render turbo_stream: turbo_stream.append(
          'messages_list',
          partial: 'messages/message',
          locals: { message: @message }
        )
      end
      format.html { redirect_to @message.room }
    end
  end
end

Background Processing with Active Job

Asynchronous queue job execution:

class FulfillmentJob < ApplicationJob
  queue_as :default

  retry_on Net::OpenTimeout, wait: :exponentially_longer, attempts: 3

  def perform(order_id)
    order = Order.find(order_id)
    OrderFulfillmentService.new(order).process!
  end
end

Common Patterns

Turbo Stream Real-Time Dom Updates (Hotwire)

Problem: Needing single-page app reactivity without complex React/Vue frontend builds.

Solution: Broadcast model updates via Turbo Streams:

# app/models/message.rb
class Message < ApplicationRecord
  belongs_to :room
  after_create_commit -> {
    broadcast_append_to room, target: "messages", partial: "messages/message", locals: { message: self }
  }
end

Best Practices

Do:

  • Target Rails 7.2 / 8 with Propshaft asset pipeline and built-in Solid Queue / Solid Cache.
  • Always use strong parameters (params.require(:order).permit(...)) in controllers.
  • Use includes or strict_loading to prevent N+1 query performance degradation.
  • Encapsulate complex multi-model business logic inside Plain Old Ruby Object (PORO) service objects.

Don't:

  • Put business logic or complex database queries inside view templates or controllers.
  • Run long-running tasks synchronously inside HTTP controller actions; offload to Active Job.
  • Skip database indexes on foreign keys; declare them explicitly in migrations.

Troubleshooting

ErrorCauseSolution
ActiveRecord::RecordNotFoundfind(id) called with non-existent primary key.Use find_by(id: ...) or handle rescue in ApplicationController.
ActionController::InvalidAuthenticityTokenCSRF token missing or mismatch in POST/PATCH request.Include <%= csrf_meta_tags %> in layout or verify headers.
PendingMigrationError: Migrations are pendingDatabase schema out of date with migration files.Run bin/rails db:migrate.

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.