| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 0 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 1 | 0 | 0% |
What each file covers
Sections
0 shared · 0 only in A · 1 only in B- + REQUIRED FOR EVERY INTERACTION
Commands
neither file has anySection tags
0 shared · 1 only in A · 0 only in B- − code-style
Line diff
aviemet/inventory · .cursor/rules/rspec.mdc
@@ −1 @@
1---
2description:
3globs: *_spec.rb
4alwaysApply: false
5---
6Avoid using `let` when setting up tests. Prefer setting up state and context in each test rather than introducing indirection by using `let`.
7
8In request specs, when testing inertia related responses and props, use the inertia rspec helpers.
9
aviemet/inventory · .cursor/rules/inventory.mdc
@@ +1 @@
1---
2description:
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
@@ −1 +1 @@
11 ---
22 description:
3−globs: *_spec.rb
4−alwaysApply: false
3+globs:
4+alwaysApply: true
55 ---
6−Avoid using `let` when setting up tests. Prefer setting up state and context in each test rather than introducing indirection by using `let`.
6+# REQUIRED FOR EVERY INTERACTION
77
8−In request specs, when testing inertia related responses and props, use the inertia rspec helpers.
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
915
