Onboard a repo

Cursor rules

One .mdc rule file per stack, scoped by frontmatter globs — rendered by redline init wherever the organisation has the vendor enabled.

What gets rendered

rendered artifacts
.cursor/rules/redline-javascript.mdc   # globs: **/*.js, **/*.mjs …
.cursor/rules/redline-react.mdc        # globs: **/*.tsx …

Each file carries a globs: frontmatter list, so rules activate only on matching files. The redline- prefix keeps pruning safe — Cursor rules a team wrote themselves are never touched.

Connect it

  1. Check the vendor is on for your organisation: vendors.cursor.enabled in standards/manifest.json, which ships true. A vendor the manifest disables never renders, whatever a repository asks for.
  2. Run npx redlinegate init on the repo — it renders the .cursor/rules/ files and opens a pull request with them. A later standards change arrives as a sync pull request, or is picked up by re-running init — see Distribution & drift.
  3. Cursor picks them up automatically; the Cursor agent additionally reads AGENTS.md.