rails-ai-context

You've seen it. Your AI:

• Writes a migration for a column that already exists — didn't check the schema
• Creates a method that duplicates one in a concern — didn't know it was there
• Uses the wrong association name — user.posts when it's user.articles
• Generates tests that don't match your patterns — factories when you use fixtures, or the reverse
• Adds a gem you already have — or calls an API from one you don't
• Misses before_action filters from parent controllers — then wonders why auth fails
• Invents a method that isn't in your codebase — then you spend 10 minutes finding out

You catch it. You fix it. You re-prompt. It breaks something else.

The real cost of AI coding isn't the tokens — it's the correction loop. Every guess is a round-trip: you catch it, you fix it, you re-prompt, and something adjacent breaks. This gem kills the guessing at its source.

gem "rails-ai-context", group: :development
rails generate rails_ai_context:install

gem install rails-ai-context
cd your-rails-app
rails-ai-context init     # interactive setup
rails-ai-context serve    # start MCP server

Now your AI doesn't guess — it asks your app directly. 38 tools and 5 resource templates that query your schema, models, routes, controllers, views, and conventions on demand. Model introspection uses Prism AST parsing — every result carries a [VERIFIED] or [INFERRED] confidence tag so AI knows what's ground truth and what needs runtime checking.

One call returns: definition + source code + every caller grouped by type + tests. Replaces 4-5 sequential file reads.

Real scenarios where AI goes sideways — and what it does instead with ground truth:

# Schema: does AI know what columns exist?
rails 'ai:tool[schema]' table=users

# Trace: find every caller of a method across the codebase
rails 'ai:tool[search_code]' pattern=your_method match_type=trace

# Model: associations, scopes, callbacks, concerns — all resolved
rails 'ai:tool[model_details]' model=User

# Controllers: action source + inherited filters + strong params in one shot
rails 'ai:tool[controllers]' controller=UsersController action=create

rails ai:serve

→ rails_search_code(pattern: "can_cook?", match_type: "trace")
→ rails_get_schema(table: "users")
→ rails_analyze_feature(feature: "billing")

# config/routes.rb
mount RailsAiContext::Engine, at: "/mcp"

rails 'ai:tool[search_code]' pattern="can_cook?" match_type=trace
rails 'ai:tool[schema]' table=users
rails 'ai:tool[analyze_feature]' feature=billing

Full Guide → — every command, every parameter, every configuration option.

# Step 1: Check what exists
rails 'ai:tool[schema]' table=users
# → 20 columns, types, indexes, encrypted hints, defaults

# Step 2: Understand the model
rails 'ai:tool[model_details]' model=User
# → associations, validations, scopes, enums, callbacks, Devise modules

# Step 3: See the full feature
rails 'ai:tool[analyze_feature]' feature=subscription
# → models + controllers + routes + services + jobs + views + tests in one shot

# Trace what happens
rails 'ai:tool[controllers]' controller=CooksController action=create
# → source code + inherited filters + strong params + render map + side effects

# Check the routes
rails 'ai:tool[routes]' controller=cooks
# → code-ready helpers (cook_path(@record)) + required params

# Validate after fixing
rails 'ai:tool[validate]' files=app/controllers/cooks_controller.rb level=rails
# → syntax + semantics + Brakeman security scan

# Check existing view patterns
rails 'ai:tool[view]' controller=dashboard
# → templates with ivars, Turbo frames, Stimulus controllers, partial locals

# See existing components + usage examples
rails 'ai:tool[component_catalog]' detail=standard
# → ViewComponent/Phlex props, slots, previews, sidecar assets

# Get Stimulus data-attributes
rails 'ai:tool[stimulus]' controller=chart
# → correct HTML with dashes (not underscores) + reverse view lookup

Every tool is read-only and returns data verified against your actual app — not guesses, not training data.

Full parameter docs →

AI clients can also read structured data through resource templates — rails-ai-context:// URIs that introspect fresh on every request. Zero stale data.

Plus 9 static resources (schema, routes, conventions, gems, controllers, config, tests, migrations, engines) that AI clients read directly.

Every generated context file ships with 6 rules that force AI verification before writing code. The protocol targets the exact cognitive failures that produce confident-wrong code: statistical priors overriding observed facts, pattern completion beating verification, stale context lies.

┌─────────────────────────────────────────────────────────┐
│  Your Rails App                                          │
│  models + schema + routes + controllers + views + jobs   │
└────────────────────────┬────────────────────────────────┘
                         │ introspects (31 introspectors)
                         ▼
┌─────────────────────────────────────────────────────────┐
│  rails-ai-context                                        │
│  Prism AST parsing. Cached. Confidence-tagged results.    │
│  VFS: rails-ai-context:// URIs introspected fresh.        │
└────────┬──────────────────┬──────────────┬──────────────┘
         │                  │              │
         ▼                  ▼              ▼
┌──────────────────┐ ┌────────────┐ ┌────────────────────┐
│  Static Files     │ │  MCP Server │ │  CLI Tools          │
│  CLAUDE.md        │ │  38 tools   │ │  Same 38 tools      │
│  .cursor/rules/   │ │  5 templates│ │  No server needed   │
│  .github/instr... │ │  stdio/HTTP │ │  rails 'ai:tool[X]' │
└──────────────────┘ └────────────┘ └────────────────────┘

Option A — In Gemfile:

gem "rails-ai-context", group: :development
rails generate rails_ai_context:install

Option B — Standalone (no Gemfile entry needed):

gem install rails-ai-context
cd your-rails-app
rails-ai-context init

Both paths ask which AI tools you use (Claude Code, Cursor, GitHub Copilot, OpenCode, Codex CLI) and whether you want MCP or CLI mode. Each tool gets its own MCP config file — auto-detected on project open.

# config/initializers/rails_ai_context.rb
if defined?(RailsAiContext)
  RailsAiContext.configure do |config|
    config.ai_tools   = %i[claude cursor] # Which AI tools to generate for
    config.tool_mode  = :mcp              # :mcp (default) or :cli
    config.preset     = :full             # :full (31 introspectors) or :standard (17)
  end
end

Every MCP tool call and resource read fires an ActiveSupport::Notifications event. Subscribe with standard Rails patterns:

ActiveSupport::Notifications.subscribe("rails_ai_context.tools.call") do |event|
  Rails.logger.info "[MCP] #{event.payload[:method]} — #{event.duration}ms"
end

Events: rails_ai_context.tools.call, rails_ai_context.resources.read, and more. All 38 tools declare output_schema in the MCP protocol, so clients know the response format before calling.

• Ruby >= 3.2    Rails >= 7.1
• Optional: brakeman for security scanning, listen for watch mode, ripgrep for fast search