mcpField
R
real-world-rails

real-world-rails

github.com/steveclarkeDevelopment545211 installsUpdated 2d ago
Repository

About real-world-rails

A research skill for examining how patterns are implemented across source code from 200+ production Rails applications. It is intended for Rails developers who need code-based analysis or comparisons grounded in real implementations.

Key features

  1. 01Search production Rails applications
  2. 02Read models, migrations, and schemas
  3. 03Analyze associations, validations, and queries
  4. 04Synthesize findings into analysis
  5. 05Run adversarial pattern comparisons when relevant

Use cases

  1. 01Research Rails implementation patterns
  2. 02Compare approaches across codebases
  3. 03Evaluate patterns against a project's architecture

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/steveclarke/real-world-rails --skill real-world-rails

After installing, type/real-world-railsin Claude Code to confirm it loaded.

Bundled filesmetadata.json

Details

From the project README

Rails Pattern Research

What This Is

The Real World Rails repository is a collection of 200+ production Rails application source code. The apps/ directory contains the full source of each app — models, migrations, schema, controllers, views, concerns, gems. The engines/ directory contains Rails engines.

Locating the Repository

Look for a directory called real-world-rails with an apps/ subdirectory. Check the current working directory first, then ~/src/real-world-rails. If not found, ask the user where it lives.

What To Do

The user gives you a topic. Spin up parallel agents to search the apps for how real codebases implement that pattern. Read actual code — models, schemas, migrations, associations, validations, query patterns — not just file names. Synthesize what you find into a clear analysis.

If the user's wording suggests they want help choosing a pattern for their current project (words like "compare for us", "which fits best", "adversarial", "debate", "evaluate for our project"), also spin up adversarial agents that each argue for a different pattern in the context of the current project's architecture and goals.

Comments

Markdown supported