| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 0 | 1 | 0% |
| Commands | 0 | 0 | 1 | 0% |
| Section tags | 0 | 0 | 1 | 0% |
What each file covers
Sections
0 shared · 0 only in A · 1 only in B- + Compile Check Rule
Commands
0 shared · 0 only in A · 1 only in B- + cargo check --all-targets --all-features
Section tags
0 shared · 0 only in A · 1 only in B- + build
Line diff
tyler274/rummage · .cursor/rules/general.mdc
@@ −1 @@
1---
2description: General rules to always be applied
3globs:
4alwaysApply: true
5---
61. Using Bevy 0.16.x APIs that aren't deprecated, we are implementing a robust unit and integrated end to end tested Magic the Gathering Commander format game engine.
72. Text2dBundle, SpriteBundle, NodeBundle, Camera2dBundle, SpatialBundle etc are deprecated for Text2d, Sprite, Node, and Camera2d respectively.
83. Use bevy_persistent for all persistent data operations.
94. Use bevy_replicon for networking.
105. Always check for and fix any compiler warnings and errors when changing code.
116. Always keep documentation in sync with the implementation.
127. Stage all the changed files determined using "git status" with a descriptive commit
13message using repeated "-m" flags for proper multiline commits in a single command
14invocation.
158. Use chainable builder pattern APIs to construct structs in a reusable way. Especially
16in test code. These builders/constructors should be const where possible.
17
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.
@@ −1 +1 @@
11 ---
2−description: General rules to always be applied
2+description:
33 globs:
44 alwaysApply: true
55 ---
6−1. Using Bevy 0.16.x APIs that aren't deprecated, we are implementing a robust unit and integrated end to end tested Magic the Gathering Commander format game engine.
7−2. Text2dBundle, SpriteBundle, NodeBundle, Camera2dBundle, SpatialBundle etc are deprecated for Text2d, Sprite, Node, and Camera2d respectively.
8−3. Use bevy_persistent for all persistent data operations.
9−4. Use bevy_replicon for networking.
10−5. Always check for and fix any compiler warnings and errors when changing code.
11−6. Always keep documentation in sync with the implementation.
12−7. Stage all the changed files determined using "git status" with a descriptive commit
13−message using repeated "-m" flags for proper multiline commits in a single command
14−invocation.
15−8. Use chainable builder pattern APIs to construct structs in a reusable way. Especially
16−in test code. These builders/constructors should be const where possible.
6+# Compile Check Rule
177
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.
