| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 1 | 2 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − ML Rules
- + Frontend Instructions
Commands
neither file has anySection tags
0 shared · 1 only in A · 2 only in B- − do-not
- + test
- + agent-behaviour
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 · .github/instructions/frontend.instructions.md
@@ +1 @@
1---
2applyTo: "frontend/**/*.{ts,tsx,css,html,json}"
3---
4
5# Frontend Instructions
6
7- Keep React components typed, feature-oriented, and consistent with `frontend/src/features`.
8- Preserve mobile-first responsive behavior, light/dark themes, accessible controls, and existing CSS variables.
9- Keep patient-facing copy calm, plain, and non-diagnostic.
10- For UI changes, consider empty, loading, error, and edge states.
11- Update or add Vitest coverage when behavior changes.
12
@@ −1 +1 @@
11 ---
2−description: ML workspace rules
3−globs:
4− - "ml/**/*"
5−alwaysApply: false
2+applyTo: "frontend/**/*.{ts,tsx,css,html,json}"
63 ---
74
8−# ML Rules
5+# Frontend Instructions
96
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.
7+- Keep React components typed, feature-oriented, and consistent with `frontend/src/features`.
8+- Preserve mobile-first responsive behavior, light/dark themes, accessible controls, and existing CSS variables.
9+- Keep patient-facing copy calm, plain, and non-diagnostic.
10+- For UI changes, consider empty, loading, error, and edge states.
11+- Update or add Vitest coverage when behavior changes.
1512
