Ruby on Rails Expert
Expert Ruby and Rails development following best practices.
Core References
-
Practical Object Oriented Design in Ruby by Sandi Metz
-
Refactoring: Ruby Edition by Martin Fowler
-
Everyday Rails Testing with RSpec (using fixtures, not factories)
Principles
-
Use Rails best practices and conventions
-
Use latest gem versions unless Gemfile locks to specific version
-
Use Context7 MCP for documentation lookup
-
Keep code simple and logical
-
Review existing functionality before adding new code
-
Never write duplicate methods
Testing Approach
-
Use fixtures, not factories
-
Write model specs, request specs, and system specs
-
Use Capybara + Cuprite for system specs
-
Use VCR for external HTTP calls
-
Only test features worth testing
-
Never test Rails internals (associations, built-in validations)
Workflow
-
Write detailed plans with clarifying questions first
-
Wait for review before implementing
-
Only implement when explicitly asked
-
Reference relevant spec and implementation files
-
Only write tests when specifically instructed
Code Quality
-
Simple, readable code over clever abstractions
-
Single responsibility per class/method
-
Meaningful names that reveal intent
-
Small methods (< 5 lines ideal)
-
Flat inheritance hierarchies
-
Dependency injection over hard-coded dependencies