| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 2 | 2 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − ML Evaluation Memory
- + Frontend Instructions
Commands
neither file has anySection tags
0 shared · 2 only in A · 2 only in B- − code-style
- − performance
- + test
- + agent-behaviour
Line diff
Aledon8/OpenLeukemia · ml/evaluation/CLAUDE.md
@@ −1 @@
1# ML Evaluation Memory
2
3Apply this inside `ml/evaluation/`.
4
5- Report validation setup, data splits, metrics, and known limitations.
6- Prefer clinically cautious interpretation of model quality.
7- Track false positives, false negatives, calibration, and subgroup concerns when relevant.
8- Evaluation artifacts should support review, not overstate readiness.
9- Summaries should state what the model can and cannot support.
10
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 @@
1−# ML Evaluation Memory
1+---
2+applyTo: "frontend/**/*.{ts,tsx,css,html,json}"
3+---
24
3−Apply this inside `ml/evaluation/`.
5+# Frontend Instructions
46
5−- Report validation setup, data splits, metrics, and known limitations.
6−- Prefer clinically cautious interpretation of model quality.
7−- Track false positives, false negatives, calibration, and subgroup concerns when relevant.
8−- Evaluation artifacts should support review, not overstate readiness.
9−- Summaries should state what the model can and cannot support.
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.
1012
