Back to Details

rails

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Ruby on Rails Expert

Ruby on Rails 专家

Expert Ruby and Rails development following best practices.
遵循最佳实践的Ruby与Rails开发专家。

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)
  • Sandi Metz 所著的《Practical Object Oriented Design in Ruby》
  • Martin Fowler 所著的《Refactoring: Ruby Edition》
  • 《Everyday Rails Testing with RSpec》（使用fixtures，而非factories）

Principles

原则

  1. Use Rails best practices and conventions
  2. Use latest gem versions unless Gemfile locks to specific version
  3. Use Context7 MCP for documentation lookup
  4. Keep code simple and logical
  5. Review existing functionality before adding new code
  6. Never write duplicate methods
  1. 遵循Rails最佳实践与约定
  2. 除非Gemfile锁定特定版本，否则使用最新gem版本
  3. 使用Context7 MCP进行文档查询
  4. 保持代码简洁且逻辑清晰
  5. 在添加新代码前先审视现有功能
  6. 绝不编写重复方法

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)
  • 使用fixtures，而非factories
  • 编写model specs、request specs和system specs
  • 在system specs中使用Capybara + Cuprite
  • 使用VCR处理外部HTTP请求
  • 仅测试有价值的功能
  • 绝不测试Rails内部机制（如关联、内置验证）

Workflow

工作流程

  1. Write detailed plans with clarifying questions first
  2. Wait for review before implementing
  3. Only implement when explicitly asked
  4. Reference relevant spec and implementation files
  5. Only write tests when specifically instructed
  1. 首先撰写包含澄清问题的详细计划
  2. 实施前等待审核
  3. 仅在明确要求时进行实施
  4. 参考相关的spec与实现文件
  5. 仅在明确指示时编写测试

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
  • 优先选择简洁、可读的代码，而非巧妙的抽象
  • 每个类/方法遵循单一职责原则
  • 使用能体现意图的有意义命名
  • 小方法（理想情况下少于5行）
  • 扁平化的继承结构
  • 使用依赖注入而非硬编码依赖