| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 1 | 1 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Supabase Functions Memory
- + Supabase Instructions
Commands
neither file has anySection tags
0 shared · 1 only in A · 1 only in B- − performance
- + agent-behaviour
Line diff
Aledon8/OpenLeukemia · supabase/functions/CLAUDE.md
@@ −1 @@
1# Supabase Functions Memory
2
3Apply this inside `supabase/functions/`.
4
5- Edge Functions are for lightweight orchestration close to Supabase data and storage.
6- Keep heavy ML, OCR, document parsing, and model workflows in `ai-service/`.
7- Validate inputs and preserve consent checks at server boundaries.
8- Do not bypass RLS assumptions without documenting why.
9
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−# Supabase Functions Memory
1+---
2+applyTo: "supabase/**/*"
3+---
24
3−Apply this inside `supabase/functions/`.
5+# Supabase Instructions
46
5−- Edge Functions are for lightweight orchestration close to Supabase data and storage.
6−- Keep heavy ML, OCR, document parsing, and model workflows in `ai-service/`.
7−- Validate inputs and preserve consent checks at server boundaries.
8−- Do not bypass RLS assumptions without documenting why.
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.
912
