Better Specs (Rails/RSpec)

Use this skill to apply Better Specs guidance to Rails spec writing and reviews.

Workflow (use on every request)

1. Identify spec type and scope: model, request, feature/system, job, mailer, service, lib.
2. Load only the rule files that match the question.
3. Apply guidance in this order: structure → naming → setup → expectations → speed.
4. Provide fixes as concrete edits or short examples (do/don’t).
5. When refactoring, preserve intent and minimize setup bloat.

Spec-type guidance (default expectations)

• Model/unit specs: prefer describe '#method' or '.method', lean setup, single expectations.
• Request/feature specs: allow multiple expectations per example if setup dominates.
• Controller specs: keep minimal; prefer request/feature specs for behavior.

Common pitfalls to catch