ruler-rules-init

Bootstrapping Ruler rules across multiple repositories involves applying template-driven scaffolding to standardize `.ruler/*` file generation. This process uses preset-based project detection and wires ruler:apply into package.json for safe, idempotent setup across monorepos.

The best way to standardize AGENTS.md and CLAUDE.md generation is through automated Ruler integration with preset-based project detection. This safely generates agent files and applies applyTo scoping patterns like `**` or `web/**` to minimize configuration drift.

Yes, preset-driven scaffolding supports a pnpm monorepo. The bootstrap tool handles both monorepo (Turbo / pnpm) and standalone repositories, applying auto-detection with presets like monorepo or node-lib to wire configurations safely.

Idempotent setup prevents configuration drift in Ruler by ensuring repeated applications of the bootstrap tool produce the same result without overwriting manual changes. It safely applies templates and updates `.gitignore` while standardizing `.ruler/*` files across runs.

You need to add generated-file ignores in `.gitignore` for Ruler to prevent committing auto-generated files like AGENTS.md or CLAUDE.md into version control. The bootstrap tool automatically wires these `.gitignore` updates to keep your repository clean and standardized.

You should use applyTo scoping patterns like `web/**` or `**` in Ruler when you need to target specific directories or the entire repository for AI rules. Designing these patterns during the bootstrap process ensures rules apply only to the intended project scopes safely.