From sorah-guides
Provides Ruby on Rails conventions, patterns, and best practices for ActiveRecord models, controllers, migrations, configuration, background jobs, logging, and request specs.
npx claudepluginhub sorah/config --plugin sorah-guidesThis skill uses the workspace's default tool permissions.
Coding conventions and best practices for Ruby on Rails projects. Project-specific conventions (CLAUDE.md, style guides) always take priority over this guidance.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Coding conventions and best practices for Ruby on Rails projects. Project-specific conventions (CLAUDE.md, style guides) always take priority over this guidance.
has_many, belongs_to, has_one — specify dependent behavior and foreign key constraintsRails.configuration.x.namespace.key with second-level namespacing; avoid single-level Rails.configuration.x.fooconfig/environments/*.rb using ENV.fetch; avoid direct ENV access in application codeRails.env checks: Do not use Rails.env.production? or similar in application code; express environment differences through configuration values instead# Good — config/environments/production.rb
Rails.configuration.x.oauth.client_id = ENV.fetch("OAUTH_CLIENT_ID")
Rails.configuration.x.session.idle_timeout = 30.minutes
# Good — application code
client_id = Rails.configuration.x.oauth.client_id
# Bad — direct ENV access in application code
client_id = ENV.fetch("OAUTH_CLIENT_ID")
# Bad — Rails.env check in application code
if Rails.env.production?
Prefer test-driven development: write a failing test first (Red), implement minimum code to pass (Green), then refactor while keeping tests green. Tests should cover both happy paths and error conditions.
let_it_be for read-only fixtures shared across examples.invalid TLD for fake hostnames and URLs in test data (RFC 2606 reserved, guaranteed to never resolve)travel_to depending on project conventionhas_secure_password or dedicated servicefilter_parameters configuration for sensitive request paramsbin/setup: Seed data, fixture files for development