Worked GOOD/BAD examples for Ruby style and OOP conventions — naming, idioms, safe navigation, freeze, SRP, dependency injection, Tell-Don't-Ask, Law of Demeter, duck typing, composition over inheritance. CONSULT when you need an idiomatic Ruby example or are unsure how a style/OOP rule looks in code. Reference loaded on demand — the always-apply rules themselves live in the `ruby-style` and `ruby-oop` rules.
Installs into .claude/skills of the current project.
Are you the author of Ruby Conventions Reference?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/mik2win-ruby-conventions-reference)
---
name: ruby-conventions-reference
description: >-
Worked GOOD/BAD examples for Ruby style and OOP conventions — naming, idioms, safe
navigation, freeze, SRP, dependency injection, Tell-Don't-Ask, Law of Demeter, duck
typing, composition over inheritance.
CONSULT when you need an idiomatic Ruby example or are unsure how a style/OOP rule looks
in code. Reference loaded on demand — the always-apply rules themselves live in the
`ruby-style` and `ruby-oop` rules.
allowed-tools:
- Read
- Grep
- Glob
---
# Ruby conventions — worked examples
Companion to the `ruby-style` and `ruby-oop` rules. Read the reference file (in this skill's
folder) for the topic you need:
- **Style** — naming, quoting, safe navigation, `Time.current`, freeze, idiomatic Ruby →
`references/style.md`
- **OOP** — SRP, dependency injection, Tell-Don't-Ask, Law of Demeter, duck typing,
Open/Closed, composition over inheritance → `references/oop.md`
