| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 3 | 1 | 0% |
| Commands | 0 | 1 | 0 | 0% |
| Section tags | 0 | 2 | 0 | 0% |
What each file covers
Sections
0 shared · 3 only in A · 1 only in B- − Agent setup
- − Common tasks
- − Reference
- + Context Engineering Checklist
Commands
0 shared · 1 only in A · 0 only in B- − pnpm install
Section tags
0 shared · 2 only in A · 0 only in B- − setup
- − agent-behaviour
Line diff
novuhq/novu · .deepsec/AGENTS.md
@@ −1 @@
1# Agent setup
2
3This is a deepsec scanning workspace. Each registered project has its
4own setup prompt at `data/<id>/SETUP.md` — open the relevant one when
5asked to set a project up.
6
7## Common tasks
8
9- **Set up a project for scanning**: read `data/<id>/SETUP.md` and
10 follow it (read `node_modules/deepsec/SKILL.md`, then fill
11 `data/<id>/INFO.md` from the target codebase).
12- **Add a new project**: run `deepsec init-project <root>` — it
13 scaffolds `data/<id>/` and prints/writes the setup prompt for the
14 new project.
15- **Write a custom matcher** (only after a real true-positive shows you
16 a pattern worth keeping): read
17 `node_modules/deepsec/dist/docs/writing-matchers.md`.
18
19## Reference
20
21The deepsec skill is at `node_modules/deepsec/SKILL.md` (after
22`pnpm install`). The full docs ship at
23`node_modules/deepsec/dist/docs/`.
24
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
@@ −1 +1 @@
1−# Agent setup
1+---
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
12+---
213
3−This is a deepsec scanning workspace. Each registered project has its
4−own setup prompt at `data/<id>/SETUP.md` — open the relevant one when
5−asked to set a project up.
14+### Context Engineering Checklist
615
7−## Common tasks
16+When writing or reviewing agent instructions, tool descriptions, or prompts:
817
9−- **Set up a project for scanning**: read `data/<id>/SETUP.md` and
10− follow it (read `node_modules/deepsec/SKILL.md`, then fill
11− `data/<id>/INFO.md` from the target codebase).
12−- **Add a new project**: run `deepsec init-project <root>` — it
13− scaffolds `data/<id>/` and prints/writes the setup prompt for the
14− new project.
15−- **Write a custom matcher** (only after a real true-positive shows you
16− a pattern worth keeping): read
17− `node_modules/deepsec/dist/docs/writing-matchers.md`.
18−
19−## Reference
20−
21−The deepsec skill is at `node_modules/deepsec/SKILL.md` (after
22−`pnpm install`). The full docs ship at
23−`node_modules/deepsec/dist/docs/`.
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
2426
