Write rules as operational constraints: on a large monorepo

Tip: Rules are not a style essay

Say what the agent must never do: no seed, keep published_at filters, no JS build. Point at paths and @ the two files that matter.

---
description: lexprog invariants
globs: src/**/*.rs
---
Never run cargo run --bin seed.

Gotcha: A rule that restates Rust book (on a large monorepo)

The model already knows Rust. Spend tokens on this repo's footguns. @ing the whole repo wastes the window and underweights the middle.

# What is ownership?

Source: https://docs.cursor.com/context/rules