Comparison

A · Cursor rules · novuhq/novu B · AGENTS.md · novuhq/novu

What each file covers, counted
Dimension	Shared	Only in A	Only in B	Overlap
Sections	0	1	9	0%
Commands	0	0	2	0%
Section tags	1	1	2	25%

What each file covers

Sections

0 shared · 1 only in A · 9 only in B

− Pull Request Rules
+ AGENTS.md
+ Cursor Cloud specific instructions
+ Build
+ AI Boundaries
+ Always
+ Ask First
+ Never
+ Developer-local agent config
+ Novu Distribution

Commands

0 shared · 0 only in A · 2 only in B

+ pnpm setup:agent
+ pnpm build

Section tags

1 shared · 1 only in A · 2 only in B

− git-pr
+ build
+ agent-behaviour
do-not

Line diff

+36 added−11 removed8 unchanged18.2% identical

novuhq/novu · .cursor/rules/pullrequest.mdc

@@ −1 @@

1---

2description: When creating a new pull request on GitHub, use this to specify the contents

3alwaysApply: false

4---

6### Pull Request Rules

8**Title format**: `type(scope): Description fixes NOV-<ticket-id>`

10- When creating a pull requests from any run, verify that there is a linear ticket associated with the pr (From branch name or other), if not, create the linear ticket before creating the PR and attach the linear ticket id in title (fixes NV-XXX)

11- Examples: `feat(dashboard): add workflow trigger button fixes NOV-123`, `fix(api-service): handle null subscriber case fixes NOV-456`

14**Scopes**: `dashboard`, `api-service`, `worker`, `shared`, `js`, `react`, `react-native`, `nextjs`, `providers`, `root`, `docs`

16**Description**: Summarize what changed and why. List breaking changes. Add screenshots for UI changes. For non-trivial logic or architecture changes, include a concise Mermaid diagram (flow, sequence, or component) so reviewers can grasp the change at a glance.

18**Enterprise packages**: When changes touch `enterprise/`, also open a matching PR in `novuhq/packages-enterprise` on a branch from `next`, and cross-link the two PR bodies (monorepo ↔ enterprise). The Validate Submodule Sync test will fail; this is expected when pointing to the `.source` submodule in the novuhq/novu repository. Do not fix it.

novuhq/novu · AGENTS.md

@@ +1 @@

1# AGENTS.md

3## Cursor Cloud specific instructions

5`pnpm setup:agent` has already been run. Do not run it again. The environment is fully configured: dependencies installed, enterprise packages linked, project built, `.env` files in place, Docker services running, and a default user/org seeded. The dashboard auto signs in the pre-seeded agent user when opened in the browser (no manual login unless auto sign-in fails).

7## Build

9Run `pnpm build` after changes to `packages/` or `enterprise/`. Direct changes to `apps/` do not require a rebuild.

11## AI Boundaries

13### Always

14- Work within: `apps/api`, `apps/dashboard`, `apps/worker`, `apps/ws`

15- Use shared packages: `packages/shared`, `packages/framework`, `packages/js`, `packages/react`

16- Follow `libs/dal` for data access, `libs/application-generic` for business logic

18### Ask First

19- Before creating new UI components not in `apps/dashboard/src/components/`

20- Before adding npm dependencies

21- Before modifying MongoDB models, ClickHouse table definitions, or anything in `enterprise/` or `packages/providers/`

23### Never

24- Inactive apps — do not touch, unless monorepo wide refactor: `apps/webhook`

25- Auto-generated — never edit: `libs/internal-sdk`

26- UI: reuse existing Radix/shadcn components only; do not copy patterns from `playground/` into production code

27- If doing a monorepo wide refactor, you can touch the read only, but only when necessary.

30## Developer-local agent config

32If a **`.agents-local/`** directory exists in your working copy, read **`.agents-local/README.md`** first for personal, git-ignored agent configuration, skills and rules. Absence of the directory is normal.

34## Novu Distribution

35Novu is distributed in 3 modes, Community Edition, Enterprise Cloud Edition, and On-Prem Enterprise Edition.

37When making changes targeted to the Enterprise distribution, we need to make sure that the changes are not breaking the Community edition, and are properly gated behind a flag, or the novu enterpise env variables. Similarly when some changes are only targeting the Cloud, self-hosted on prem should not be affected.

39

40

41

42

43

@@ −1 +1 @@

1−---

2−description: When creating a new pull request on GitHub, use this to specify the contents

3−alwaysApply: false

4−---

1+# AGENTS.md

6−### Pull Request Rules

3+## Cursor Cloud specific instructions

8−**Title format**: `type(scope): Description fixes NOV-<ticket-id>`

5+`pnpm setup:agent` has already been run. Do not run it again. The environment is fully configured: dependencies installed, enterprise packages linked, project built, `.env` files in place, Docker services running, and a default user/org seeded. The dashboard auto signs in the pre-seeded agent user when opened in the browser (no manual login unless auto sign-in fails).

10−- When creating a pull requests from any run, verify that there is a linear ticket associated with the pr (From branch name or other), if not, create the linear ticket before creating the PR and attach the linear ticket id in title (fixes NV-XXX)

11−- Examples: `feat(dashboard): add workflow trigger button fixes NOV-123`, `fix(api-service): handle null subscriber case fixes NOV-456`

7+## Build

128

9+Run `pnpm build` after changes to `packages/` or `enterprise/`. Direct changes to `apps/` do not require a rebuild.

1310

14−**Scopes**: `dashboard`, `api-service`, `worker`, `shared`, `js`, `react`, `react-native`, `nextjs`, `providers`, `root`, `docs`

11+## AI Boundaries

1512

16−**Description**: Summarize what changed and why. List breaking changes. Add screenshots for UI changes. For non-trivial logic or architecture changes, include a concise Mermaid diagram (flow, sequence, or component) so reviewers can grasp the change at a glance.

13+### Always

14+- Work within: `apps/api`, `apps/dashboard`, `apps/worker`, `apps/ws`

15+- Use shared packages: `packages/shared`, `packages/framework`, `packages/js`, `packages/react`

16+- Follow `libs/dal` for data access, `libs/application-generic` for business logic

1717

18−**Enterprise packages**: When changes touch `enterprise/`, also open a matching PR in `novuhq/packages-enterprise` on a branch from `next`, and cross-link the two PR bodies (monorepo ↔ enterprise). The Validate Submodule Sync test will fail; this is expected when pointing to the `.source` submodule in the novuhq/novu repository. Do not fix it.

18+### Ask First

19+- Before creating new UI components not in `apps/dashboard/src/components/`

20+- Before adding npm dependencies

21+- Before modifying MongoDB models, ClickHouse table definitions, or anything in `enterprise/` or `packages/providers/`

22+

23+### Never

24+- Inactive apps — do not touch, unless monorepo wide refactor: `apps/webhook`

25+- Auto-generated — never edit: `libs/internal-sdk`

26+- UI: reuse existing Radix/shadcn components only; do not copy patterns from `playground/` into production code

27+- If doing a monorepo wide refactor, you can touch the read only, but only when necessary.

28+

29+

30+## Developer-local agent config

31+

32+If a **`.agents-local/`** directory exists in your working copy, read **`.agents-local/README.md`** first for personal, git-ignored agent configuration, skills and rules. Absence of the directory is normal.

33+

34+## Novu Distribution

35+Novu is distributed in 3 modes, Community Edition, Enterprise Cloud Edition, and On-Prem Enterprise Edition.

36+

37+When making changes targeted to the Enterprise distribution, we need to make sure that the changes are not breaking the Community edition, and are properly gated behind a flag, or the novu enterpise env variables. Similarly when some changes are only targeting the Cloud, self-hosted on prem should not be affected.

38+

39+

40+

41+

42+

43+

1944