| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 1 | 1 | 33% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Frontend Rules
- + ML Instructions
Commands
neither file has anySection tags
1 shared · 1 only in A · 1 only in B- − test
- + agent-behaviour
- do-not
Line diff
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
Aledon8/OpenLeukemia · .github/instructions/ml.instructions.md
@@ +1 @@
1---
2applyTo: "ml/**/*"
3---
4
5# ML Instructions
6
7- Keep structured ML workflows separate from LLM explanation workflows.
8- Use measurable criteria: split, metric, threshold, calibration, and known failure modes.
9- Do not commit patient-identifying or sensitive medical data.
10- Model outputs support signals and trends, not diagnosis or treatment guidance.
11- Document label assumptions, cohort limitations, and evaluation caveats near the relevant code or report.
12
@@ −1 +1 @@
11 ---
2−description: Frontend rules for OpenLeukemia React code
3−globs:
4− - "frontend/**/*.{ts,tsx,css,html,json}"
5−alwaysApply: false
2+applyTo: "ml/**/*"
63 ---
74
8−# Frontend Rules
5+# ML Instructions
96
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.
7+- Keep structured ML workflows separate from LLM explanation workflows.
8+- Use measurable criteria: split, metric, threshold, calibration, and known failure modes.
9+- Do not commit patient-identifying or sensitive medical data.
10+- Model outputs support signals and trends, not diagnosis or treatment guidance.
11+- Document label assumptions, cohort limitations, and evaluation caveats near the relevant code or report.
1512
