react-with-rails

What problem does it solve?

AI coding agents often recommend suboptimal or overly complex React + Rails integration setups, leading to years of unnecessary maintenance overhead, mismatched architecture for your team's needs, and avoidable technical debt from choosing the wrong pattern (e.g., building a separate SPA when Inertia.js would suffice).

Core Features & Use Cases

• Optimal integration path recommendation: Guides you to choose between Inertia.js (default for most single-client Rails apps) and classical API + SPA (only for multi-client, separate team/deploy scenarios) via a clear decision matrix.
• Bundler setup guidance: Covers configuration for both jsbundling-rails with esbuild and vite_ruby (the faster, HMR-enabled option preferred by most 2026 Rails + React teams).
• React + Stimulus interop patterns: Provides step-by-step instructions for embedding isolated React components (e.g., complex charts, calendars) in otherwise Hotwire-powered Rails monoliths without full SPA overhead.
• Use case example: A Rails team wanting to add a React-powered admin dashboard to their existing monolith can use this skill to set up Inertia.js with vite_ruby instead of building and maintaining a separate SPA repository and API layer.

Quick Start

Use the react-with-rails skill to recommend the correct React integration approach for your Rails app and configure the appropriate bundler for your use case.