Why does this skill recommend avoiding foreign key constraints?

Following production patterns from companies like 37signals, it avoids database-level foreign keys to prevent deadlocks during bulk operations, simplify large-scale migrations, and allow for more flexible deletion orders.

How does it handle multi-tenancy?

It ensures every tenant-scoped table includes an 'account_id' column and provides patterns for automatic query scoping via ApplicationRecord to prevent data leakage between tenants.

What is the 'state-as-records' pattern?

Instead of using boolean columns like 'closed: true', this pattern uses a separate table (e.g., 'closures') to record exactly when and by whom a state change occurred, providing a built-in audit trail.

Does this skill support UUIDv7?

Yes, it specifically enforces UUIDv7 (timestamp-ordered) primary keys, which are base36 encoded to prevent ID enumeration attacks while preserving chronological sorting.

Vanilla Rails Data Modeling

Name: Vanilla Rails Data Modeling
Author: ZempTime

byZempTime

•

Database Management

Enforces high-performance, multi-tenant database schema patterns and migrations for Ruby on Rails applications based on 37signals conventions.

About

This skill equips Claude with the expertise to design and implement robust database architectures for Rails applications, specifically following the production-hardened conventions popularized by 37signals. It prioritizes operational flexibility, auditability, and scalability by enforcing UUID primary keys, mandatory account-based multi-tenancy scoping, and the 'state-as-records' pattern instead of simple boolean columns. By avoiding foreign key constraints in favor of application-level integrity and utilizing specific indexing strategies, this skill helps developers build data layers that are resilient to deadlocks and optimized for multi-tenant query patterns.

Key Features

State-as-records implementation for auditable workflows
Strict UUIDv7 primary key enforcement for all tables
Account-based multi-tenancy architecture patterns
1 GitHub stars
Optimized composite indexing for tenant-scoped queries
Application-level integrity patterns without foreign key constraints

Use Cases

Migrating from integer IDs to UUIDs for improved security and environment syncing
Designing a new multi-tenant SaaS application on Ruby on Rails
Refactoring legacy boolean state columns into robust, auditable state tables

About

Key Features

State-as-records implementation for auditable workflows
Strict UUIDv7 primary key enforcement for all tables
Account-based multi-tenancy architecture patterns
1 GitHub stars
Optimized composite indexing for tenant-scoped queries
Application-level integrity patterns without foreign key constraints

Use Cases

Migrating from integer IDs to UUIDs for improved security and environment syncing
Designing a new multi-tenant SaaS application on Ruby on Rails
Refactoring legacy boolean state columns into robust, auditable state tables