How to Use It Well
Start with a short .ruler/AGENTS.md that encodes your real workflow (tests, style, safety). Then turn on nested mode only where components truly differ.
Adoption Checklist
- Start with one real task and keep the scope narrow
- Capture a baseline: time-to-first-success and output quality
- Version your config/skills so teammates stay in sync
Guardrails
Generated files should stay generated. Avoid manual edits downstream; treat .ruler/ as the only editable surface.
FAQ
Q: Is it production-ready? A: The README labels it as a beta research preview; adopt it in one repo first and keep rollbacks simple.
Q: How does it avoid drift?
A: Rules live in .ruler/ and Ruler regenerates downstream config files, so you maintain one source of truth.
Q: Can it handle monorepos?
A: Yes. The repo documents nested rule loading for multiple .ruler/ directories with scoped configs.