Why does this skill prefer state records over boolean columns?

State records capture critical metadata like 'who' performed an action and 'when' it happened automatically. They provide better referential integrity and allow you to add metadata later without altering the main table.

What is invocation-based method ordering?

It is a code organization pattern where methods are ordered vertically by flow: callers are defined before the methods they call (callees), allowing the file to be read top-to-bottom like a story.

How should I name and namespace my Rails concerns?

Concerns should be named as adjectives (like Closeable or Assignable) and namespaced under the model they belong to (e.g., app/models/card/closeable.rb).

When is it appropriate to extract code into a concern?

You should extract logic into a concern when a feature adds three or more methods, a clear adjective-based capability exists, or the model file exceeds approximately 100 lines.

Vanilla Rails Models

Name: Vanilla Rails Models
Author: ZempTime

byZempTime

•

Database Management

Enforces production-grade Rails model patterns including state-as-records, namespaced concerns, and invocation-based method ordering.

About

This skill equips Claude with the architectural patterns popularized by 37signals and Basecamp for Ruby on Rails development. It focuses on creating rich domain models that avoid the 'service object' trap by using adjective-named concerns namespaced directly under the model. Key features include the 'state-as-records' pattern, which replaces simple booleans with dedicated tables to capture audit trails (who and when), and strict code organization rules such as ordering methods by invocation and specific private method indentation for maximum readability.

Key Features

Standardized private method indentation and class method placement.
Adjective-based concern namespacing (e.g., Card::Starrable) for better decomposition.
State-as-record architecture to automatically capture metadata and audit trails.
Strict method ordering based on invocation flow for top-to-bottom readability.
Guidance on when to extract capabilities to keep models under 100 lines.
1 GitHub stars

Use Cases

Standardizing a Rails codebase to follow 'Vanilla Rails' and 37signals best practices.
Refactoring bloated Rails models into clean, concern-based architectures.
Implementing robust state management that requires tracking user actions and timestamps.

About

Key Features

Standardized private method indentation and class method placement.
Adjective-based concern namespacing (e.g., Card::Starrable) for better decomposition.
State-as-record architecture to automatically capture metadata and audit trails.
Strict method ordering based on invocation flow for top-to-bottom readability.
Guidance on when to extract capabilities to keep models under 100 lines.
1 GitHub stars

Use Cases

Standardizing a Rails codebase to follow 'Vanilla Rails' and 37signals best practices.
Refactoring bloated Rails models into clean, concern-based architectures.
Implementing robust state management that requires tracking user actions and timestamps.