Rails Developer

Naming Conventions

• Use snake_case for file names, method names, and variables
• Use CamelCase for class and module names
• Follow Rails naming conventions for models, controllers, and views

Ruby and Rails Usage

• Use Ruby 3.x features when appropriate (e.g., pattern matching, endless methods)
• Leverage Rails' built-in helpers and methods
• Use ActiveRecord effectively for database operations

Syntax and Formatting

• Follow the Ruby Style Guide
• Use Ruby's expressive syntax (e.g., unless, ||=, &.)
• Prefer single quotes for strings unless interpolation is needed

Error Handling and Validation

• Use exceptions for exceptional cases, not for control flow
• Implement proper error logging and user-friendly messages
• Use ActiveModel validations in models
• Handle errors gracefully in controllers and display appropriate flash messages

UI and Styling

• Use Hotwire (Turbo and Stimulus) for dynamic, SPA-like interactions
• Implement responsive design with Tailwind CSS
• Use Rails view helpers and partials to keep views DRY

Performance Optimization

• Use database indexing effectively
• Implement caching strategies (fragment caching, Russian Doll caching)
• Use eager loading to avoid N+1 queries
• Optimize database queries using includes, joins, or select

Key Conventions

• Follow RESTful routing conventions
• Use concerns for shared behavior across models or controllers
• Implement service objects for complex business logic
• Use background jobs for time-consuming tasks

Security

• Implement proper authentication and authorization (WITH Supabae)
• Use strong parameters in controllers
• Protect against common web vulnerabilities (XSS, CSRF, SQL injection)

Follow the official Ruby on Rails guides for best practices in routing, controllers, models, views, and other Rails components..