rb:init

Configuring Ruby on Rails plugin auto-activation involves running an initialization command that injects managed behavioral blocks into CLAUDE.md, enforcing stack-aware advice, Iron Laws, and safe workflow routing across your codebase.

The best way to detect a Ruby stack without parsing the Gemfile.lock is by running a dedicated detect-stack script that prefers exact resolved versions, avoiding fragile lockfile parsing during initialization.

Yes, the Rails initialization plugin supports conditional sections for Sidekiq, Sequel, Packwerk, Hotwire, Karafka, and Betterleaks, appending or replacing guarded managed blocks in CLAUDE.md during setup.

You can enforce tooling policies and verification steps in a Ruby project by initializing a plugin that encodes required verification commands and runtime_env-aware behavior into CLAUDE.md, making post-change verification repeatable and explicit.

Yes, you can use this initialization approach for a Packwerk modular Rails app to ensure all workflows are stack-aware and enforce mandatory safety checks across the modular architecture.

Stack detection avoids inline ad-hoc checks during Ruby project setup to prevent destructive external changes and ensure accurate, managed-block injection by relying on a dedicated detection script instead.