| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 1 | 1 | 0 | 50% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 2 | 0 | 33% |
What each file covers
Sections
1 shared · 1 only in A · 0 only in B- − Rules
- Supabase Instructions
Commands
neither file has anySection tags
1 shared · 2 only in A · 0 only in B- − code-style
- − do-not
- agent-behaviour
Line diff
Aledon8/OpenLeukemia · supabase/CLAUDE.md
@@ −1 @@
1# Supabase Instructions
2
3Supabase is the MVP platform layer for auth, Postgres, storage, Row Level Security, consent records, and lightweight Edge Functions.
4
5## Rules
6
7- Treat Row Level Security as a primary protection layer.
8- Keep consent behavior explicit, auditable, and revocable.
9- Prefer Supabase for routine product workflows and `ai-service/` for Python, ML, OCR, extraction, and compute-heavy work.
10- Keep migrations and policies readable and reversible where practical.
11- Do not weaken privacy, authorization, or consent checks without an explicit product reason.
12- For schema or policy changes, plan affected data flows and access paths before editing.
13
Aledon8/OpenLeukemia · .github/instructions/supabase.instructions.md
@@ +1 @@
1---
2applyTo: "supabase/**/*"
3---
4
5# Supabase Instructions
6
7- Use Supabase for auth, CRUD, storage, consent records, RLS, and lightweight Edge Functions.
8- Keep heavy ML, OCR, extraction, parsing, and model workflows in `ai-service`.
9- Treat RLS as a primary protection layer.
10- Pair sensitive tables with narrow, auditable policies.
11- Plan affected data flows and access paths before schema or policy changes.
12
@@ −1 +1 @@
1+---
2+applyTo: "supabase/**/*"
3+---
4+
15 # Supabase Instructions
26
3−Supabase is the MVP platform layer for auth, Postgres, storage, Row Level Security, consent records, and lightweight Edge Functions.
4−
5−## Rules
6−
7−- Treat Row Level Security as a primary protection layer.
8−- Keep consent behavior explicit, auditable, and revocable.
9−- Prefer Supabase for routine product workflows and `ai-service/` for Python, ML, OCR, extraction, and compute-heavy work.
10−- Keep migrations and policies readable and reversible where practical.
11−- Do not weaken privacy, authorization, or consent checks without an explicit product reason.
12−- For schema or policy changes, plan affected data flows and access paths before editing.
7+- Use Supabase for auth, CRUD, storage, consent records, RLS, and lightweight Edge Functions.
8+- Keep heavy ML, OCR, extraction, parsing, and model workflows in `ai-service`.
9+- Treat RLS as a primary protection layer.
10+- Pair sensitive tables with narrow, auditable policies.
11+- Plan affected data flows and access paths before schema or policy changes.
1312
