| 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
- + Supabase 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/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 Features Memory
1+---
2+description: Supabase data, storage, and RLS rules
3+globs:
4+ - "supabase/**/*"
5+alwaysApply: false
6+---
27
3−Apply this inside `frontend/src/features/`.
8+# Supabase 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+- 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.
1015
