| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 1 | 0 | 50% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Frontend Rules
- + Supabase Rules
Commands
neither file has anySection tags
1 shared · 1 only in A · 0 only in B- − test
- do-not
Line diff
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
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 @@
11 ---
2−description: Frontend rules for OpenLeukemia React code
2+description: Supabase data, storage, and RLS rules
33 globs:
4− - "frontend/**/*.{ts,tsx,css,html,json}"
4+ - "supabase/**/*"
55 alwaysApply: false
66 ---
77
8−# Frontend Rules
8+# Supabase Rules
99
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.
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.
1515
