| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 2 | 1 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Frontend Rules
- + ML Inference Memory
Commands
neither file has anySection tags
0 shared · 2 only in A · 1 only in B- − test
- − do-not
- + performance
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 · ml/inference/CLAUDE.md
@@ +1 @@
1# ML Inference Memory
2
3Apply this inside `ml/inference/`.
4
5- Keep inference interfaces typed, deterministic, and easy to validate.
6- Return explainable scores or signals with limitations, not clinical conclusions.
7- Preserve compatibility with `ai-service/` consumers when inference code is promoted.
8- Validate feature order, units, and missing-value behavior explicitly.
9
@@ −1 +1 @@
1−---
2−description: Frontend rules for OpenLeukemia React code
3−globs:
4− - "frontend/**/*.{ts,tsx,css,html,json}"
5−alwaysApply: false
6−---
1+# ML Inference Memory
72
8−# Frontend Rules
3+Apply this inside `ml/inference/`.
94
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.
5+- Keep inference interfaces typed, deterministic, and easy to validate.
6+- Return explainable scores or signals with limitations, not clinical conclusions.
7+- Preserve compatibility with `ai-service/` consumers when inference code is promoted.
8+- Validate feature order, units, and missing-value behavior explicitly.
159
