Why order methods by invocation sequence?

Ordering by invocation sequence allows developers to read code chronologically, following the execution flow from caller to callee rather than searching alphabetically.

When should I use a bang (!) in method names?

Following this style, you should only use a bang when a non-bang (safe) counterpart exists, avoiding its use solely to flag destructive actions.

How does this differ from standard Rubocop rules?

Unlike standard Rubocop, this skill prefers if/else over guard clauses for visibility and requires private methods to be indented two spaces under the private keyword.

Does this skill support service objects?

This skill discourages service objects as a default pattern, instead promoting 'Vanilla Rails' where logic resides in rich domain models and thin controllers.

Vanilla Rails Style Guide

Name: Vanilla Rails Style Guide
Author: ZempTime

byZempTime

•

Developer Tools

Enforces 37signals-inspired Ruby on Rails conventions to prioritize code readability and maintainable domain-driven design.

The Vanilla Rails Style skill equips Claude with the specific coding conventions championed by 37signals and the Basecamp team, which often deviate from standard Ruby style guides like Rubocop. This skill emphasizes readability through the use of expanded if/else conditionals over guard clauses, specific private method indentation, and method ordering based on invocation sequence. By encouraging a 'Vanilla Rails' architecture—focusing on rich domain models, thin controllers, and resource-oriented routing—it ensures your codebase remains consistent with high-leverage, production-grade Rails patterns used by industry leaders.

Key Features

01Advocates for rich domain models over service object abstractions

02Promotes resource-oriented routing and CRUD-based controller architecture

03Enforces private method indentation and non-alphabetical invocation ordering

04Restrictive bang (!) method naming conventions based on counterparts

051 GitHub stars

06Prioritizes explicit if/else structures over guard clauses for better logic flow

Use Cases

01Standardizing method organization and architectural patterns across team repositories

02Refactoring legacy Rails codebases to follow modern 37signals conventions

03Onboarding developers to projects following the 'Rails Omakase' philosophy

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add zemptime/zemptime-marketplace style

For use in Claude.ai and ChatGPT

Download Skill