active-record-patterns

What problem does it solve?

Ruby on Rails projects often suffer from money fields stored as floats, N+1 queries, missing transaction boundaries, and weak locking strategies, leading to data corruption and performance issues.

Core Features & Use Cases

• Enforce Iron Laws such as using decimal for money, preventing N+1 queries with intentional preloading, and keeping invariants inside transactions.
• Guidance on Migrations: ensure reversibility, safe foreign keys, and concurrent indexes for large tables.
• Transaction & Locking Best Practices: recommend optimistic or pessimistic locks, after_commit side‑effects, and isolation levels.
• Real‑world Example: In a billing system, the skill will flag float‑based price columns, suggest decimal migrations, and add select_for_update where race conditions exist.

Quick Start

Ask the active-record-patterns skill to analyze your app/models directory and suggest improvements for money fields, N+1 queries, and transaction safety.