| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 3 | 1 | 0% |
| Commands | 0 | 5 | 0 | 0% |
| Section tags | 0 | 3 | 3 | 0% |
What each file covers
Sections
0 shared · 3 only in A · 1 only in B- − Frontend Instructions
- − Commands
- − Rules
- + Documentation Page Memory
Commands
0 shared · 5 only in A · 0 only in B- − npm --workspace frontend run dev
- − npm --workspace frontend run lint
- − npm --workspace frontend run typecheck
- − npm --workspace frontend run test
- − npm --workspace frontend run build
Section tags
0 shared · 3 only in A · 3 only in B- − test
- − do-not
- − agent-behaviour
- + code-style
- + performance
- + docs
Line diff
Aledon8/OpenLeukemia · frontend/CLAUDE.md
@@ −1 @@
1# Frontend Instructions
2
3This directory contains the React + TypeScript + Vite application.
4
5## Commands
6
7Run from the repository root unless you are already inside `frontend/`:
8
9```sh
10npm --workspace frontend run dev
11npm --workspace frontend run lint
12npm --workspace frontend run typecheck
13npm --workspace frontend run test
14npm --workspace frontend run build
15```
16
17## Rules
18
19- Keep components feature-oriented under `src/features/` unless shared app-level code is a better fit.
20- Preserve mobile-first responsive behavior, light/dark theme support, and accessible interactions.
21- Keep patient-facing copy calm, plain, and non-diagnostic.
22- Reuse existing CSS variables and layout patterns in `src/styles/global.css`.
23- Add or update Vitest tests when UI behavior changes.
24- For visual UI work, compare against the existing page or supplied design and verify desktop and mobile states.
25
Aledon8/OpenLeukemia · frontend/src/features/documentation/CLAUDE.md
@@ +1 @@
1# Documentation Page Memory
2
3Apply this inside `frontend/src/features/documentation/`.
4
5- Keep project documentation readable for patients, contributors, and reviewers.
6- Link concepts back to charter, architecture, privacy, consent, and non-diagnostic AI behavior.
7- Avoid marketing-heavy copy; prefer precise product and safety language.
8- Preserve theme controls and accessible structure.
9
@@ −1 +1 @@
1−# Frontend Instructions
1+# Documentation Page Memory
22
3−This directory contains the React + TypeScript + Vite application.
3+Apply this inside `frontend/src/features/documentation/`.
44
5−## Commands
6−
7−Run from the repository root unless you are already inside `frontend/`:
8−
9−```sh
10−npm --workspace frontend run dev
11−npm --workspace frontend run lint
12−npm --workspace frontend run typecheck
13−npm --workspace frontend run test
14−npm --workspace frontend run build
15−```
16−
17−## Rules
18−
19−- Keep components feature-oriented under `src/features/` unless shared app-level code is a better fit.
20−- Preserve mobile-first responsive behavior, light/dark theme support, and accessible interactions.
21−- Keep patient-facing copy calm, plain, and non-diagnostic.
22−- Reuse existing CSS variables and layout patterns in `src/styles/global.css`.
23−- Add or update Vitest tests when UI behavior changes.
24−- For visual UI work, compare against the existing page or supplied design and verify desktop and mobile states.
5+- Keep project documentation readable for patients, contributors, and reviewers.
6+- Link concepts back to charter, architecture, privacy, consent, and non-diagnostic AI behavior.
7+- Avoid marketing-heavy copy; prefer precise product and safety language.
8+- Preserve theme controls and accessible structure.
259
