| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 0 | 1 | 50% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − ML Rules
- + Frontend Rules
Commands
neither file has anySection tags
1 shared · 0 only in A · 1 only in B- + test
- 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/frontend.mdc
@@ +1 @@
1---
2description: Frontend rules for OpenLeukemia React code
3globs:
4 - "frontend/**/*.{ts,tsx,css,html,json}"
5alwaysApply: false
6---
7
8# Frontend Rules
9
10- Keep React components typed, feature-oriented, and consistent with `frontend/src/features`.
11- Preserve mobile-first responsive behavior, light/dark themes, accessible controls, and existing CSS variables.
12- Keep patient-facing copy calm, plain, and non-diagnostic.
13- Consider empty, loading, error, and edge states before implementation.
14- Update or add Vitest coverage when behavior changes.
15
@@ −1 +1 @@
11 ---
2−description: ML workspace rules
2+description: Frontend rules for OpenLeukemia React code
33 globs:
4− - "ml/**/*"
4+ - "frontend/**/*.{ts,tsx,css,html,json}"
55 alwaysApply: false
66 ---
77
8−# ML Rules
8+# Frontend Rules
99
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.
10+- Keep React components typed, feature-oriented, and consistent with `frontend/src/features`.
11+- Preserve mobile-first responsive behavior, light/dark themes, accessible controls, and existing CSS variables.
12+- Keep patient-facing copy calm, plain, and non-diagnostic.
13+- Consider empty, loading, error, and edge states before implementation.
14+- Update or add Vitest coverage when behavior changes.
1515
