Inertia Rails Project Setup

Detect stack, offer recommended deps, generate CLAUDE.md configuration.

Run once per project. Re-run when the stack changes.

NEVER:

• Run setup without inertia_rails gem in Gemfile — all skills assume it exists. If missing, tell the user to install it first.
• Overwrite existing ## Inertia Rails Stack in CLAUDE.md without reading it — the user may have manual customizations. Replace only the auto-generated block.
• Add @/ resolve aliases to vite.config.ts — vite-plugin-ruby already provides them. Only add to tsconfig.json.
• Recommend rails-inertia-alba if the project uses jbuilder AND the user hasn't expressed interest in switching — suggest it, but don't push. You CAN still suggest it if the project has blueprinter (alba is a direct upgrade path).
• Generate CLAUDE.md blocks for skills the user doesn't have installed — saying "rails-inertia-alba skill does NOT apply" is correct; saying "use rails-inertia-alba" when the gem is absent is wrong.

Step 1: Detect Current Stack

Read Gemfile (NOT Gemfile.lock) and package.json and check for: