| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 1 | 0 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − TDD
- + REQUIRED FOR EVERY INTERACTION
Commands
neither file has anySection tags
0 shared · 1 only in A · 0 only in B- − testing-strategy
Line diff
aviemet/inventory · .cursor/rules/conventions.mdc
@@ −3 @@
3globs:
4alwaysApply: true
5---
6
7Only work on the task at hand. Limit the scope of your response to exactly what is being worked on in the moment.
8
9### TDD
10
11For every change, find the corresponding test and ensure it passes.
12Ensure that the tests accurately test the interfaces, adjusting tests as needed to accurately test the intention of the code. Do not change tests to fit the implementation just to make them pass. The tests need to accurately indicate the intention of the code, and the code needs to be made to pass the tests, not the other way around.
13
14* For ruby files, tests are in /rspec
15* For typescript files, tests are in /app/frontend/tests
aviemet/inventory · .cursor/rules/inventory.mdc
@@ +3 @@
3globs:
4alwaysApply: true
5---
6# REQUIRED FOR EVERY INTERACTION
7
81. Read .cursor/inventory.mdx at the start of each interaction
92. Before ending ANY response, if you've learned anything useful about project-specific architectural details that are NOT immediately obvious from reading the code, you MUST update .cursor/inventory.mdx with this information
103. When updating .cursor/inventory.mdx:
11 - Only add new information not already documented
12 - Place information in the appropriate section
13 - If no appropriate section exists, create one
14 - ONLY document project-specific architectural decisions, custom patterns, and non-obvious implementation details
15
@@ −3 +3 @@
33 globs:
44 alwaysApply: true
55 ---
6+# REQUIRED FOR EVERY INTERACTION
67
7−Only work on the task at hand. Limit the scope of your response to exactly what is being worked on in the moment.
8+1. Read .cursor/inventory.mdx at the start of each interaction
9+2. Before ending ANY response, if you've learned anything useful about project-specific architectural details that are NOT immediately obvious from reading the code, you MUST update .cursor/inventory.mdx with this information
10+3. When updating .cursor/inventory.mdx:
11+ - Only add new information not already documented
12+ - Place information in the appropriate section
13+ - If no appropriate section exists, create one
14+ - ONLY document project-specific architectural decisions, custom patterns, and non-obvious implementation details
815
9−### TDD
10−
11−For every change, find the corresponding test and ensure it passes.
12−Ensure that the tests accurately test the interfaces, adjusting tests as needed to accurately test the intention of the code. Do not change tests to fit the implementation just to make them pass. The tests need to accurately indicate the intention of the code, and the code needs to be made to pass the tests, not the other way around.
13−
14−* For ruby files, tests are in /rspec
15−* For typescript files, tests are in /app/frontend/tests
