| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 8 | 0% |
| Section tags | 0 | 0 | 0 | — |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Context Engineering Checklist
- + Infrastructure
Commands
0 shared · 0 only in A · 8 only in B- + docker compose -f docker/local/docker-compose.yml up -d
- + docker compose -f docker/local/docker-compose.agent.yml up -d
- + pnpm start:api:dev
- + pnpm start:worker
- + pnpm start:ws
- + docker compose
- + pnpm build
- + pnpm build:agents
Section tags
neither file has anyLine diff
novuhq/novu · .cursor/rules/context-engineering.mdc
@@ −1 @@
1---
2description: Context quality checklist for system prompts and agent instructions
3globs:
4 - "**/tools/**/*.ts"
5 - "**/prompts/**/*.ts"
6 - "**/*.prompt.ts"
7 - "AGENTS.md"
8 - ".cursor/rules/**"
9 - ".cursor/skills/**"
10 - ".agents/skills/**"
11alwaysApply: false
12---
13
14### Context Engineering Checklist
15
16When writing or reviewing agent instructions, tool descriptions, or prompts:
17
18- Is this explained elsewhere? → Consolidate to one location
19- Would a senior dev infer this? → Remove if obvious
20- Can this be an example instead? → One example beats three paragraphs of rules
21- Is this defensive repetition ("MUST", "NEVER", "CRITICAL")? → State once, remove emphasis
22- Does this duplicate a tool's own description? → Keep in tool description only
23- Are there prescriptive step lists? → Compress to a sentence
24- Is the altitude right? → Specific heuristics, not hardcoded logic or vague guidance
25- Is this stable across requests? → Move to cached/static portion
26
novuhq/novu · .cursor/rules/infrastructure.mdc
@@ +1 @@
1---
2description: Infrastructure setup, Docker services, and environment configuration
3globs:
4 - "docker/**/*"
5 - "*.env*"
6 - ".env*"
7 - "**/docker-compose*"
8alwaysApply: false
9---
10
11## Infrastructure
12
13**Start all services:** `docker compose -f docker/local/docker-compose.yml up -d`
14
15**Agent environments** use a separate compose file — restart after a reboot with:
16`docker compose -f docker/local/docker-compose.agent.yml up -d`
17
18| Service | Port | Purpose |
19|---------|------|---------|
20| MongoDB | 27017 | Primary database |
21| Redis | 6379 | Caching + Bull queues |
22| ClickHouse | 8123 (HTTP) / 9000 (native) | Analytics, activity feed, traces |
23| LocalStack | 4566 | S3 emulation (optional) |
24
25**Services needed per task:**
26- Dashboard UI only: nothing (user has it running on port 4201)
27- API endpoints: `pnpm start:api:dev`
28- Notification flows: API + `pnpm start:worker`
29- Real-time features: API + Worker + `pnpm start:ws`
30- Full stack: `docker compose` + all of the above
31
32Run `pnpm build` before starting services only if changes were made to `libs/`, `packages/`, or `enterprise/`. Cloud agent install/update uses `pnpm build:agents`, which skips full app builds but still runs `@novu/api-service:build:metadata` (apps otherwise build when their dev servers start).
@@ −1 +1 @@
11 ---
2−description: Context quality checklist for system prompts and agent instructions
2+description: Infrastructure setup, Docker services, and environment configuration
33 globs:
4− - "**/tools/**/*.ts"
5− - "**/prompts/**/*.ts"
6− - "**/*.prompt.ts"
7− - "AGENTS.md"
8− - ".cursor/rules/**"
9− - ".cursor/skills/**"
10− - ".agents/skills/**"
4+ - "docker/**/*"
5+ - "*.env*"
6+ - ".env*"
7+ - "**/docker-compose*"
118 alwaysApply: false
129 ---
1310
14−### Context Engineering Checklist
11+## Infrastructure
1512
16−When writing or reviewing agent instructions, tool descriptions, or prompts:
13+**Start all services:** `docker compose -f docker/local/docker-compose.yml up -d`
1714
18−- Is this explained elsewhere? → Consolidate to one location
19−- Would a senior dev infer this? → Remove if obvious
20−- Can this be an example instead? → One example beats three paragraphs of rules
21−- Is this defensive repetition ("MUST", "NEVER", "CRITICAL")? → State once, remove emphasis
22−- Does this duplicate a tool's own description? → Keep in tool description only
23−- Are there prescriptive step lists? → Compress to a sentence
24−- Is the altitude right? → Specific heuristics, not hardcoded logic or vague guidance
25−- Is this stable across requests? → Move to cached/static portion
15+**Agent environments** use a separate compose file — restart after a reboot with:
16+`docker compose -f docker/local/docker-compose.agent.yml up -d`
2617
18+| Service | Port | Purpose |
19+|---------|------|---------|
20+| MongoDB | 27017 | Primary database |
21+| Redis | 6379 | Caching + Bull queues |
22+| ClickHouse | 8123 (HTTP) / 9000 (native) | Analytics, activity feed, traces |
23+| LocalStack | 4566 | S3 emulation (optional) |
24+
25+**Services needed per task:**
26+- Dashboard UI only: nothing (user has it running on port 4201)
27+- API endpoints: `pnpm start:api:dev`
28+- Notification flows: API + `pnpm start:worker`
29+- Real-time features: API + Worker + `pnpm start:ws`
30+- Full stack: `docker compose` + all of the above
31+
32+Run `pnpm build` before starting services only if changes were made to `libs/`, `packages/`, or `enterprise/`. Cloud agent install/update uses `pnpm build:agents`, which skips full app builds but still runs `@novu/api-service:build:metadata` (apps otherwise build when their dev servers start).
