| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 2 | 0 | 33% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Frontend Features Memory
- + ML Inference Memory
Commands
neither file has anySection tags
1 shared · 2 only in A · 0 only in B- − test
- − code-style
- performance
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 · 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−# Frontend Features Memory
1+# ML Inference Memory
22
3−Apply this inside `frontend/src/features/`.
3+Apply this inside `ml/inference/`.
44
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.
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.
109
