| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 3 | 1 | 0% |
| Commands | 0 | 5 | 0 | 0% |
| Section tags | 1 | 2 | 0 | 33% |
What each file covers
Sections
0 shared · 3 only in A · 1 only in B- − Frontend Instructions
- − Commands
- − Rules
- + Supabase Rules
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
1 shared · 2 only in A · 0 only in B- − test
- − agent-behaviour
- do-not
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 · .cursor/rules/supabase.mdc
@@ +1 @@
1---
2description: Supabase data, storage, and RLS rules
3globs:
4 - "supabase/**/*"
5alwaysApply: false
6---
7
8# Supabase Rules
9
10- Use Supabase for auth, CRUD, storage, consent records, RLS, and lightweight Edge Functions.
11- Keep heavy ML, OCR, extraction, parsing, and model workflows in `ai-service`.
12- Treat RLS as a primary protection layer.
13- Pair sensitive tables with narrow, auditable policies.
14- Plan affected data flows and access paths before schema or policy changes.
15
@@ −1 +1 @@
1−# Frontend Instructions
1+---
2+description: Supabase data, storage, and RLS rules
3+globs:
4+ - "supabase/**/*"
5+alwaysApply: false
6+---
27
3−This directory contains the React + TypeScript + Vite application.
8+# Supabase Rules
49
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.
10+- Use Supabase for auth, CRUD, storage, consent records, RLS, and lightweight Edge Functions.
11+- Keep heavy ML, OCR, extraction, parsing, and model workflows in `ai-service`.
12+- Treat RLS as a primary protection layer.
13+- Pair sensitive tables with narrow, auditable policies.
14+- Plan affected data flows and access paths before schema or policy changes.
2515
