Name: Ror Styleguide
Author: mzygar

Rails Style Guide

Workflow

Identify the Rails area(s) in scope (for example: routing, controllers, models, migrations, views, i18n, assets, mailers, Active Support, time/duration, bundler, testing, processes).
Load the matching section file(s) from references/ before responding.
If the request spans multiple areas, read each relevant file and reconcile overlaps; prefer the most specific section.
Call out version-specific guidance explicitly (for example, Rails 6.1+ or Rails 7.0+).
If the guide does not cover a rule, say so and suggest checking the official guide section instead of inventing guidance.
Keep responses anchored to the guide’s intent; do not introduce new conventions unless asked.

Prefer concise, actionable guidance with direct mapping to the section rules.
When reviewing code, list concrete findings, each with:
- the violated rule,
- the reason (why it matters),

Identify the Rails area(s) in scope (for example: routing, controllers, models, migrations, views, i18n, assets, mailers, Active Support, time/duration, bundler, testing, processes).
Load the matching section file(s) from references/ before responding.
If the request spans multiple areas, read each relevant file and reconcile overlaps; prefer the most specific section.
Call out version-specific guidance explicitly (for example, Rails 6.1+ or Rails 7.0+).
If the guide does not cover a rule, say so and suggest checking the official guide section instead of inventing guidance.
Keep responses anchored to the guide’s intent; do not introduce new conventions unless asked.

Prefer concise, actionable guidance with direct mapping to the section rules.
When reviewing code, list concrete findings, each with:
- the violated rule,
- the reason (why it matters),