| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 0 | 1 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Context Engineering Checklist
- + Novu Conventions
Commands
neither file has anySection tags
0 shared · 0 only in A · 1 only in B- + code-style
Line 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/novu.mdc
@@ +1 @@
1---
2description:
3globs:
4alwaysApply: true
5---
6### Novu Conventions
7
8- File/directory names: lowercase with dashes (`components/auth-wizard`)
9- Named exports for all components
10- TypeScript: `interface` on the backend, `type` on the frontend — this is the project convention and overrides any general "prefer interfaces" guidance
11- Blank line before every `return` statement
12- Animations: import from `"motion/react"` — not `"framer-motion"` or `"motion-react"`
13- No nested ternaries
14
@@ −1 +1 @@
11 ---
2−description: Context quality checklist for system prompts and agent instructions
3−globs:
4− - "**/tools/**/*.ts"
5− - "**/prompts/**/*.ts"
6− - "**/*.prompt.ts"
7− - "AGENTS.md"
8− - ".cursor/rules/**"
9− - ".cursor/skills/**"
10− - ".agents/skills/**"
11−alwaysApply: false
2+description:
3+globs:
4+alwaysApply: true
125 ---
6+### Novu Conventions
137
14−### Context Engineering Checklist
15−
16−When 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
8+- File/directory names: lowercase with dashes (`components/auth-wizard`)
9+- Named exports for all components
10+- TypeScript: `interface` on the backend, `type` on the frontend — this is the project convention and overrides any general "prefer interfaces" guidance
11+- Blank line before every `return` statement
12+- Animations: import from `"motion/react"` — not `"framer-motion"` or `"motion-react"`
13+- No nested ternaries
2614
