| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 0 | 2 | 33% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − ML Rules
- + Documentation Rules
Commands
neither file has anySection tags
1 shared · 0 only in A · 2 only in B- + code-style
- + docs
- do-not
Line diff
Aledon8/OpenLeukemia · .cursor/rules/ml.mdc
@@ −1 @@
1---
2description: ML workspace rules
3globs:
4 - "ml/**/*"
5alwaysApply: false
6---
7
8# ML Rules
9
10- Keep structured ML workflows separate from LLM explanation workflows.
11- Use measurable criteria: split, metric, threshold, calibration, and known failure modes.
12- Do not commit patient-identifying or sensitive medical data.
13- Model outputs support signals and trends, not diagnosis or treatment guidance.
14- Document label assumptions, cohort limitations, and evaluation caveats near relevant code or reports.
15
Aledon8/OpenLeukemia · .cursor/rules/docs.mdc
@@ +1 @@
1---
2description: Documentation writing rules
3globs:
4 - "docs/**/*.md"
5 - "*.md"
6alwaysApply: false
7---
8
9# Documentation Rules
10
11- Write in plain, precise language for patients, contributors, and reviewers.
12- Keep privacy, consent, patient control, and non-diagnostic AI limits visible.
13- Prefer durable project facts over session-specific notes.
14- Match the structure and voice of nearby documents.
15
@@ −1 +1 @@
11 ---
2−description: ML workspace rules
2+description: Documentation writing rules
33 globs:
4− - "ml/**/*"
4+ - "docs/**/*.md"
5+ - "*.md"
56 alwaysApply: false
67 ---
78
8−# ML Rules
9+# Documentation Rules
910
10−- Keep structured ML workflows separate from LLM explanation workflows.
11−- Use measurable criteria: split, metric, threshold, calibration, and known failure modes.
12−- Do not commit patient-identifying or sensitive medical data.
13−- Model outputs support signals and trends, not diagnosis or treatment guidance.
14−- Document label assumptions, cohort limitations, and evaluation caveats near relevant code or reports.
11+- Write in plain, precise language for patients, contributors, and reviewers.
12+- Keep privacy, consent, patient control, and non-diagnostic AI limits visible.
13+- Prefer durable project facts over session-specific notes.
14+- Match the structure and voice of nearby documents.
1515
