rails-expert — Claude Code skill: what it does, how to install
Rails 7+ skill for Hotwire, Sidekiq, and Active Record optimization. Guides query tuning, Turbo Frames, and RSpec test suites.
npx skills add Jeffallan/claude-skills --skill rails-expert -a claude-codeWhat rails-expert does
The skill structures Rails 7+ workflows from resource scaffolding to schema migrations with rails db:migrate. It enforces thin controllers and moves heavy operations straight into Sidekiq workers instead of executing them synchronously inside the request cycle.
Database queries must avoid N+1 issues. The skill forces includes or eager_load on association queries and requires indexes for all columns used in WHERE, ORDER BY, or JOIN.
Validation runs through bundle exec rspec and RuboCop. The workflow targets test coverage above 95%. When generating features, it returns migrations, models, controllers with strong parameters, Hotwire views, and specs together.
What it helps with
- prevent N+1 queries using
includesandeager_load - implement partial page updates with Turbo Frames and Turbo Streams
- offload slow tasks to Sidekiq background workers
- generate models, migrations, and RSpec suites targeting >95% coverage
Example prompts for the agent
- Create a Post resource with Turbo Frame pagination and eager-loaded authors
- Set up a Sidekiq worker to send welcome emails with retry limits
- Write RSpec request specs for PostsController checking strong parameters
How to install rails-expert
1Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill rails-expert -a claude-code2Manually: put the files in place
~/.claude/skills/rails-expert/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/rails-expert/
1Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill rails-expert -a codex2Manually: put the files in place
.agents/skills/rails-expert/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill rails-expert -a cursor2Manually: put the files in place
.cursor/skills/rails-expert/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Jeffallan/claude-skills rails-expert2Manually: put the files in place
.github/skills/rails-expert/SKILL.md1Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill rails-expert -a gemini-cli2Platform CLI
gemini skills install https://github.com/Jeffallan/claude-skills --path skills/rails-expertManually: put the files in place
.devin/skills/rails-expert/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill rails-expert -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set61
The whole set →Similar
Questions about rails-expert
How to install rails-expert in Claude Code?
Run npx skills add Jeffallan/claude-skills --skill rails-expert -a claude-code. The skill configuration saves to ~/.claude/skills/rails-expert/SKILL.md.
What does the rails-expert skill do?
It guides the assistant in building Rails 7+ applications. It sets up Hotwire partial updates, Sidekiq jobs, Active Record optimizations, and RSpec test suites.
What constraints does rails-expert enforce on queries and tests?
The skill requires indexes for columns in WHERE, ORDER BY, or JOIN clauses. It mandates includes or eager_load on association queries and aims for over 95% test coverage.
Source text
SKILL.md · MIT
---
name: rails-expert
description: Rails 7+ specialist that optimizes Active Record queries with includes/eager_load, implements Turbo Frames and Turbo Streams for partial page updates, configures Action Cable for WebSocket connections, sets up Sidekiq workers for background job processing, and writes comprehensive RSpec test suites. Use when building Rails 7+ web applications with Hotwire, real-time features, or background job processing. Invoke for Active Record optimization, Turbo Frames/Streams, Action Cable, Sidekiq, RSpec Rails.
license: MIT
metadata:
author: https://github.com/Jeffallan
company: https://synergetic.solutions
version: "1.1.0"
domain: backend
triggers: Rails, Ruby on Rails, Hotwire, Turbo Frames, Turbo Streams, Action Cable, Active Record, Sidekiq, RSpec Rails
role: specialist
scope: implementation
output-format: code
related-skills: fullstack-guardian, database-optimizer
---
# Rails Expert
## Core Workflow
1. **Analyze requirements** — Identify models, routes, real-time needs, background jobs
2. **Scaffold resources** — `rails generate model User name:string email:string`, `rails generate controller Users`
3. **Run migrations** — `rails db:migrate` and verify schema with `rails db:schema:dump`
- If migration fails: inspect `db/schema.rb` for conflicts, rollback with `rails db:rollback`, fix and retry
4. **Implement** — Write controllers, models, add Hotwire (see Reference Guide below)
5. **Validate** — `bundle exec rspec` must pass; `bundle exec rubocop` for style
- If specs fail: check error output, fix failing examples, re-run with `--format documentation` for detail
- If N+1 queries surface during review: add `includes`/`eager_load` (see Common Patterns) and re-run specs
6. **Optimize** — Audit for N+1 queries, add missing indexes, add caching
## Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
|-------|-----------|-----------|
| Hotwire/Turbo | `references/hotwire-turbo.md` | Turbo Frames, Streams, Stimulus controllers |
| Active Record | `references/active-record.md` | Models, associations, queries, performance |
| Background Jobs | `references/background-jobs.md` | Sidekiq, job design, queues, error handling |
| Testing | `references/rspec-testing.md` | Model/request/system specs, factories |
| API Development | `references/api-development.md` | API-only mode, serialization, authentication |
## Common Patterns
### N+1 Prevention with includes/eager_load
```ruby
# BAD — triggers N+1
posts = Post.all
posts.each { |post| puts post.author.name }
# GOOD — eager load association
posts = Post.includes(:author).all
posts.each { |post| puts post.author.name }
# GOOD — eager_load forces a JOIN (useful when filtering on association)
posts = Post.eager_load(:author).where(authors: { verified: true })
```
### Turbo Frame Setup (partial page update)
```erb
<%# app/views/posts/index.html.erb %>
<%= turbo_frame_tag "posts" do %>
<%= render @posts %>
<%= link_to "Load More", posts_path(page: @next_page) %>
<% end %>
<%# app/views/posts/_post.html.erb %>
<%= turbo_frame_tag dom_id(post) do %>
<h2><%= post.title %></h2>
<%= link_to "Edit", edit_post_path(post) %>
<% end %>
```
```ruby
# app/controllers/posts_controller.rb
def index
@posts = Post.includes(:author).page(params[:page])
@next_page = @posts.next_page
end
```
### Sidekiq Worker Template
```ruby
# app/jobs/send_welcome_email_job.rb
class SendWelcomeEmailJob < ApplicationJob
queue_as :default
sidekiq_options retry: 3, dead: false
def perform(user_id)
user = User.find(user_id)
UserMailer.welcome(user).deliver_now
rescue ActiveRecord::RecordNotFound => e
Rails.logger.warn("SendWelcomeEmailJob: user #{user_id} not found — #{e.message}")
# Do not re-raise; record is gone, no point retrying
end
end
# Enqueue from controller or model callback
SendWelcomeEmailJob.perform_later(user.id)
```
### Strong Parameters (controller template)
```ruby
# app/controllers/posts_controller.rb
class PostsController < ApplicationController
before_action :set_post, only: %i[show edit update destroy]
def create
@post = Post.new(post_params)
if @post.save
redirect_to @post, notice: "Post created."
else
render :new, status: :unprocessable_entity
end
end
private
def set_post
@post = Post.find(params[:id])
end
def post_params
params.require(:post).permit(:title, :body, :published_at)
end
end
```
## Constraints
### MUST DO
- Prevent N+1 queries with `includes`/`eager_load` on every collection query involving associations
- Write comprehensive specs targeting >95% coverage
- Use service objects for complex business logic; keep controllers thin
- Add database indexes for every column used in `WHERE`, `ORDER BY`, or `JOIN`
- Offload slow operations to Sidekiq — never run them synchronously in a request cycle
### MUST NOT DO
- Skip migrations for schema changes
- Use raw SQL without sanitization (`sanitize_sql` or parameterized queries only)
- Expose internal IDs in URLs without consideration
## Output Templates
When implementing Rails features, provide:
1. Migration file (if schema changes needed)
2. Model file with associations and validations
3. Controller with RESTful actions and strong parameters
4. View files or Hotwire setup
5. Spec files for models and requests
6. Brief explanation of architectural decisions
Maintained by [@jeffallan](https://github.com/jeffallan), Principal Consultant at [Synergetic Solutions](https://synergetic.solutions)
[Documentation](https://jeffallan.github.io/claude-skills/skills/backend/rails-expert/)
© https://github.com/Jeffallan · MIT · Jeffallan/claude-skills