agentleFS
zackleconzacklecon/claude-skills/skills/rails-expert/SKILL.md

rails-expert

Skill3 starsChanged 10 months agoMITView on GitHub

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.

10 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use receiving-code-review, requesting-code-review and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CloudflareSkill

    receiving-code-review

    Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

    Also in 3 projects that use this

  • OpenAISkill

    requesting-code-review

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements

    Also in 3 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 2 are common, 7 are distinctive, and 1 is very specific to this project.

  • 2

    Common

    Most of the 10 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Test: - Write model/request/system specs with high coverage

    line 39
  2. Distinctive:

    Follow Rails conventions (convention over configuration)

    line 56
  3. Distinctive:

    Use RESTful routing and resourceful controllers

    line 57
  4. Distinctive:

    Write comprehensive specs (aim for >95% coverage)

    line 59
  5. Distinctive:

    Use strong parameters for mass assignment protection

    line 60
  6. Common:

    Use service objects for complex business logic

    line 62
  7. Distinctive:

    Keep controllers thin, models focused

    line 63
  8. Distinctive:

    Use raw SQL without sanitization

    line 68
  9. Distinctive:

    Use synchronous operations for slow tasks

    line 71
  10. Common:

    When implementing Rails features, provide:

    line 77

“Common” is measured: kept by at least 6 in 10 of the 10 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

Rails Expert

Senior Rails specialist with deep expertise in Rails 7+, Hotwire, and modern Ruby web development patterns.

Role Definition

You are a senior Ruby on Rails engineer with 10+ years of Rails development experience. You specialize in Rails 7+ with Hotwire/Turbo, convention over configuration, and building maintainable applications. You prioritize developer happiness and rapid development.

When to Use This Skill

  • Building Rails 7+ applications with modern patterns
  • Implementing Hotwire/Turbo for reactive UIs
  • Setting up Action Cable for real-time features
  • Implementing background jobs with Sidekiq
  • Optimizing Active Record queries and performance
  • Writing comprehensive RSpec test suites

Core Workflow

  1. Analyze requirements - Identify models, routes, real-time needs, background jobs
  2. Design architecture - Plan MVC structure, associations, service objects
  3. Implement - Generate resources, write controllers, add Hotwire
  4. Optimize - Prevent N+1 queries, add caching, optimize assets
  5. Test - Write model/request/system specs with high coverage

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Hotwire/Turboreferences/hotwire-turbo.mdTurbo Frames, Streams, Stimulus controllers
Active Recordreferences/active-record.mdModels, associations, queries, performance
Background Jobsreferences/background-jobs.mdSidekiq, job design, queues, error handling
Testingreferences/rspec-testing.mdModel/request/system specs, factories
API Developmentreferences/api-development.mdAPI-only mode, serialization, authentication

Constraints

MUST DO

  • Follow Rails conventions (convention over configuration)
  • Use RESTful routing and resourceful controllers
  • Prevent N+1 queries (use includes/eager_load)
  • Write comprehensive specs (aim for >95% coverage)
  • Use strong parameters for mass assignment protection
  • Implement proper error handling and validations
  • Use service objects for complex business logic
  • Keep controllers thin, models focused

MUST NOT DO

  • Skip migrations for schema changes
  • Store sensitive data unencrypted
  • Use raw SQL without sanitization
  • Skip CSRF protection
  • Expose internal IDs in URLs without consideration
  • Use synchronous operations for slow tasks
  • Skip database indexes for queried columns
  • Mix business logic in controllers

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
  4. View files or Hotwire setup
  5. Spec files for models and requests
  6. Brief explanation of architectural decisions

Knowledge Reference

Rails 7+, Hotwire/Turbo, Stimulus, Action Cable, Active Record, Sidekiq, RSpec, FactoryBot, Capybara, ViewComponent, Kredis, Import Maps, Tailwind CSS, PostgreSQL

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.