Ruby on Rails Project Rules

railsrubybackend

Enforces Rails conventions including MVC separation, ActiveRecord patterns, service objects, and Rails idioms for convention-driven web application development.

Целевые файлы

Файл	Формат
.cursorrules	plaintext
CLAUDE.md	markdown

Содержимое

## Ruby on Rails Project Rules ### MVC Separation - Controllers must be thin: fetch data, call services, render response — no business logic - Models handle data validation, associations, and simple domain logic only - Complex business logic belongs in service objects under `app/services/` - Views only display data — no database queries or business rules in ERB/Haml templates - Use `before_action` for authentication and authorization; avoid repeating auth checks ### Controllers - Inherit from `ApplicationController`; domain controllers from `ApplicationController` or namespaced base - Use `strong_parameters` in every controller action: `params.require(:user).permit(:name, :email)` - Limit controller actions to the 7 RESTful actions: `index`, `show`, `new`, `create`, `edit`, `update`, `destroy` - Non-RESTful behavior must be extracted to a new controller, not added as extra actions - Use `respond_to` for controllers that serve multiple formats (HTML, JSON) - Always redirect after successful POST/PATCH/DELETE (PRG pattern) ### Models & ActiveRecord - Put validations at the top of the model, before associations and callbacks - Use `validates :field, presence: true, uniqueness: { scope: :user_id }` — not DB-only constraints - Prefer scopes over class methods for reusable query logic: `scope :active, -> { where(active: true) }` - Avoid callbacks for side effects that cross model boundaries — use service objects instead - Use `find_each` or `find_in_batches` for iterating over large datasets — never `.all.each` - Define database indexes for all foreign keys and fields used in WHERE clauses ### Associations - Declare associations with `dependent: :destroy` or `dependent: :nullify` explicitly - Use `inverse_of` on associations to prevent extra queries and memory issues - Eager-load associations with `includes()` to prevent N+1 queries - Use `counter_cache: true` for frequently counted associations ### Service Objects - Service object naming: `[Domain][Action]Service` (e.g., `UserRegistrationService`) - Service objects must have a single public method: `call` - Use `Result` objects or raise specific exceptions from services — never return `true`/`false` ambiguously - Place service objects in `app/services/` with module namespacing for domains ### Concerns - Use `ActiveSupport::Concern` for shared model or controller behavior - Concerns must be truly reusable — do not extract one-time logic into a concern - Name concerns descriptively after the behavior: `Publishable`, `Searchable`, `Auditable` ### Migrations - Never edit applied migrations — create new ones - Every migration must be reversible; implement `def down` or use reversible `change` - Add indexes in the same migration as the column creation - Run `db:migrate` before tests in CI ### Routing - Use `resources` and `resource` helpers instead of manual route definitions - Nest routes maximum one level deep to avoid deeply nested URL helpers - Use `namespace` for admin sections; use `scope` for URL prefixes without module nesting - Use named routes (`users_path`, `edit_user_path(@user)`) — never hardcode paths ### Security - Enable CSRF protection (`protect_from_forgery`) in `ApplicationController` - Use `before_action :authenticate_user!` (Devise) or equivalent for protected routes - Sanitize user input displayed as HTML with `sanitize()` — never use `html_safe` on untrusted input - Use `attr_encrypted` or Rails credentials for sensitive attributes — never store secrets in the DB in plain text ### Testing - Use RSpec with FactoryBot for unit and integration tests - Test every model validation and every service object in isolation - Use `let` lazily; use `let!` when setup must happen before the example - Use `described_class` inside shared examples ### Anti-patterns - Do not use `update_all` without a scope — it bypasses validations and callbacks intentionally - Do not use raw SQL without parameterized queries — always use `.where("column = ?", value)` - Do not load all records with `.all` into memory - Do not add logic to `ApplicationRecord` that belongs in a specific model

CLI

npx mindaxis apply rails-rules --target cursor --scope project

Используется в паках

Rails Fullstack

Convention-over-configuration Rails stack

Открыть пак →

← Правила