This is a great approach - catching rule violations before merge rather than relying on developers to remember them. The biggest challenge with .cursorrules adoption at scale is consistency across repos.

I maintain a collection of .cursorrules for 16+ frameworks (React, Next.js, FastAPI, Go, etc.) that could work as a baseline for these kinds of checks: https://github.com/survivorforge/cursor-rules

Curious how you handle framework-specific rules that only apply to certain parts of a monorepo?