| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 3 | 1 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Frontend Features Memory
- + ML Rules
Commands
neither file has anySection tags
0 shared · 3 only in A · 1 only in B- − test
- − code-style
- − performance
- + do-not
Line diff
Aledon8/OpenLeukemia · frontend/src/features/CLAUDE.md
@@ −1 @@
1# Frontend Features Memory
2
3Apply this inside `frontend/src/features/`.
4
5- Keep each feature self-contained with its component, local types, and feature-specific helpers.
6- Prefer explicit props and domain names over generic UI abstractions.
7- Patient-facing UI should explain data and choices without implying diagnosis or medical advice.
8- When feature behavior changes, add or update the nearest Vitest coverage.
9- For new feature work, map empty, loading, error, and edge states before implementation.
10
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
@@ −1 +1 @@
1−# Frontend Features Memory
1+---
2+description: ML workspace rules
3+globs:
4+ - "ml/**/*"
5+alwaysApply: false
6+---
27
3−Apply this inside `frontend/src/features/`.
8+# ML Rules
49
5−- Keep each feature self-contained with its component, local types, and feature-specific helpers.
6−- Prefer explicit props and domain names over generic UI abstractions.
7−- Patient-facing UI should explain data and choices without implying diagnosis or medical advice.
8−- When feature behavior changes, add or update the nearest Vitest coverage.
9−- For new feature work, map empty, loading, error, and edge states before implementation.
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.
1015
