| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 2 | 1 | 25% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Frontend Features Memory
- + Frontend Rules
Commands
neither file has anySection tags
1 shared · 2 only in A · 1 only in B- − code-style
- − performance
- + do-not
- test
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/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
@@ −1 +1 @@
1−# Frontend Features Memory
1+---
2+description: Frontend rules for OpenLeukemia React code
3+globs:
4+ - "frontend/**/*.{ts,tsx,css,html,json}"
5+alwaysApply: false
6+---
27
3−Apply this inside `frontend/src/features/`.
8+# Frontend 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 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.
1015
