| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 2 | 1 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Supabase Migrations Memory
- + Supabase Rules
Commands
neither file has anySection tags
0 shared · 2 only in A · 1 only in B- − code-style
- − performance
- + do-not
Line diff
Aledon8/OpenLeukemia · supabase/migrations/CLAUDE.md
@@ −1 @@
1# Supabase Migrations Memory
2
3Apply this inside `supabase/migrations/`.
4
5- Model identity, medical data, consent records, documents, and audit events deliberately.
6- Prefer explicit constraints, timestamps, and readable names.
7- Pair sensitive tables with RLS policies.
8- Do not weaken privacy or authorization behavior in a migration without a clear reason.
9- Verify migrations against expected schema shape and name any rollback or data-risk assumptions.
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−# Supabase Migrations Memory
1+---
2+description: Supabase data, storage, and RLS rules
3+globs:
4+ - "supabase/**/*"
5+alwaysApply: false
6+---
27
3−Apply this inside `supabase/migrations/`.
8+# Supabase Rules
49
5−- Model identity, medical data, consent records, documents, and audit events deliberately.
6−- Prefer explicit constraints, timestamps, and readable names.
7−- Pair sensitive tables with RLS policies.
8−- Do not weaken privacy or authorization behavior in a migration without a clear reason.
9−- Verify migrations against expected schema shape and name any rollback or data-risk assumptions.
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
