| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 0 | 0% |
| Commands | 0 | 1 | 0 | 0% |
| Section tags | 0 | 1 | 0 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 0 only in B- − Compile Check Rule
Commands
0 shared · 1 only in A · 0 only in B- − cargo check --all-targets --all-features
Section tags
0 shared · 1 only in A · 0 only in B- − build
Line diff
tyler274/rummage · .cursor/rules/compile_check.mdc
@@ −1 @@
1---
2description:
3globs:
4alwaysApply: true
5---
6# Compile Check Rule
7
8Before staging files and committing changes, ensure the codebase compiles without any errors or warnings.
9
101. After making code modifications, run the appropriate build or check command for the project (e.g., `cargo check --all-targets --all-features` for Rust projects).
112. Address any reported compiler errors or warnings.
123. Only proceed with staging and committing once the compilation is clean.
tyler274/rummage · .cursor/rules/cards.mdc
@@ +1 @@
1---
2description:
3globs: src/cards/**
4alwaysApply: false
5---
6please continue refactoring the cards module to be more in line with the docs in docs/
7updating either as needed to improve the robustness of the implementation with unit tests.
8Make sure the docs and the code stay synced. Focus on fixing all the warnings and then the
9failing tests.
10Its ok to remove unused code that has no place in the final implementation, and there should not be much dead code
@@ −1 +1 @@
11 ---
22 description:
3−globs:
4−alwaysApply: true
3+globs: src/cards/**
4+alwaysApply: false
55 ---
6−# Compile Check Rule
7−
8−Before staging files and committing changes, ensure the codebase compiles without any errors or warnings.
9−
10−1. After making code modifications, run the appropriate build or check command for the project (e.g., `cargo check --all-targets --all-features` for Rust projects).
11−2. Address any reported compiler errors or warnings.
12−3. Only proceed with staging and committing once the compilation is clean.
6+please continue refactoring the cards module to be more in line with the docs in docs/
7+updating either as needed to improve the robustness of the implementation with unit tests.
8+Make sure the docs and the code stay synced. Focus on fixing all the warnings and then the
9+failing tests.
10+Its ok to remove unused code that has no place in the final implementation, and there should not be much dead code
