| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 0 | 0 | — |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 0 | 0 | — |
What each file covers
Sections
neither file has anyCommands
neither file has anySection tags
neither file has anyLine diff
tyler274/rummage · .cursor/rules/mtg.mdc
@@ −1 @@
1---
2description: Magic the Gathering Rules
3globs:
4alwaysApply: false
5---
6[MagicCompRules 20250207.txt](mdc:docs/mtg_rules/MagicCompRules 20250207.txt) Refer to this as the source of truth for all Magic the
7Gathering rules and edge cases that need to be handled robustly in the game engine.
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
@@ −1 +1 @@
11 ---
2−description: Magic the Gathering Rules
2+description: General rules to always be applied
33 globs:
4−alwaysApply: false
4+alwaysApply: true
55 ---
6−[MagicCompRules 20250207.txt](mdc:docs/mtg_rules/MagicCompRules 20250207.txt) Refer to this as the source of truth for all Magic the
7−Gathering rules and edge cases that need to be handled robustly in the game engine.
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.
17+
