RuleStack

Configs

Stacks

Compare

Diff

RuleStack

Configs

Stacks

Compare

Diff

Read API

RuleStack

Configs

Stacks

Compare

Diff

Read API

Diff/tyler274-rummage-cursor-rules-save ↔ tyler274-rummage-cursor-rules-compile-check

Comparison

A · Cursor rules · tyler274/rummageB · Cursor rules · tyler274/rummage
What each file covers, counted
DimensionSharedOnly in AOnly in BOverlap
Sections0010%
Commands0010%
Section tags0010%

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

+8 added−4 removed4 unchanged33.3% identical
tyler274/rummage · .cursor/rules/save.mdc
@@ −1 @@
1---
2description:
3globs: src/game_engine/save/**
4alwaysApply: false
5---
6The save/load/rewind/replay/rollback subsystem collection needs to be robustly tested.
7 
8We will use it for implementing the MTG card Shahrazad "Players play a Magic subgame, using their libraries as their decks. Each player who doesn't win the subgame loses half their life, rounded up."
 
 
 
 
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 ---
22 description:
3−globs: src/game_engine/save/**
4−alwaysApply: false
3+globs:
4+alwaysApply: true
55 ---
6−The save/load/rewind/replay/rollback subsystem collection needs to be robustly tested.
6+# Compile Check Rule
77  
8−We will use it for implementing the MTG card Shahrazad "Players play a Magic subgame, using their libraries as their decks. Each player who doesn't win the subgame loses half their life, rounded up."
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.
RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack

RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack

RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack