| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 2 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 2 | 1 | 1 | 50% |
What each file covers
Sections
0 shared · 2 only in A · 1 only in B- − Supabase Instructions
- − Rules
- + Documentation Instructions
Commands
neither file has anySection tags
2 shared · 1 only in A · 1 only in B- − do-not
- + docs
- code-style
- 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/docs.instructions.md
@@ +1 @@
1---
2applyTo: "docs/**/*.md,*.md"
3---
4
5# Documentation Instructions
6
7- Write in plain, precise language for patients, contributors, and reviewers.
8- Keep privacy, consent, patient control, and non-diagnostic AI limits visible.
9- Prefer durable project facts over session-specific notes.
10- Match the structure and voice of nearby documents.
11
@@ −1 +1 @@
1−# Supabase Instructions
1+---
2+applyTo: "docs/**/*.md,*.md"
3+---
24
3−Supabase is the MVP platform layer for auth, Postgres, storage, Row Level Security, consent records, and lightweight Edge Functions.
5+# Documentation Instructions
46
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+- Write in plain, precise language for patients, contributors, and reviewers.
8+- Keep privacy, consent, patient control, and non-diagnostic AI limits visible.
9+- Prefer durable project facts over session-specific notes.
10+- Match the structure and voice of nearby documents.
1311
