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

•

数据库管理

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

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.

主要功能

01Standardized private method indentation and class method placement.

02Adjective-based concern namespacing (e.g., Card::Starrable) for better decomposition.

03State-as-record architecture to automatically capture metadata and audit trails.

04Strict method ordering based on invocation flow for top-to-bottom readability.

05Guidance on when to extract capabilities to keep models under 100 lines.

061 GitHub stars

使用场景

01Standardizing a Rails codebase to follow 'Vanilla Rails' and 37signals best practices.

02Refactoring bloated Rails models into clean, concern-based architectures.

03Implementing robust state management that requires tracking user actions and timestamps.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add zemptime/zemptime-marketplace models

For use in Claude.ai and ChatGPT

Download Skill