Vanilla Rails Naming

About

This skill implements the specific 'Vanilla Rails' naming philosophy used by 37signals in production codebases like Basecamp and HEY. It guides developers in moving away from generic Rails advice toward patterns that treat state changes as resources, strictly use adjective-based naming for concerns (-able/-ible), and eliminate custom route actions. By following these patterns, developers can build highly consistent, RESTful applications that avoid common anti-patterns like bang method misuse and verb-based concern naming.

Key Features

• Corrects state method definitions to use plain verbs instead of bang (!) suffixes
• Provides guidance on plural vs. singular naming for controllers and routes to maintain RESTful integrity
• Validates concern naming to ensure only -able or -ible adjective suffixes are used
• Standardizes asynchronous method naming using the mandatory _later suffix
• Enforces 'State as Resource' pattern by replacing custom member actions with singular resources
• 1 GitHub stars

Use Cases

• Standardizing background job enqueueing methods to clearly distinguish between async and sync execution
• Refactoring messy Rails controllers with excessive custom member routes into clean singular resources
• Renaming model concerns from nouns or verbs (e.g., Pinning) to proper adjectives (e.g., Pinnable)