| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 0 | 2 | 33% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Supabase Rules
- + Documentation Rules
Commands
neither file has anySection tags
1 shared · 0 only in A · 2 only in B- + code-style
- + docs
- do-not
Line diff
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
Aledon8/OpenLeukemia · .cursor/rules/docs.mdc
@@ +1 @@
1---
2description: Documentation writing rules
3globs:
4 - "docs/**/*.md"
5 - "*.md"
6alwaysApply: false
7---
8
9# Documentation Rules
10
11- Write in plain, precise language for patients, contributors, and reviewers.
12- Keep privacy, consent, patient control, and non-diagnostic AI limits visible.
13- Prefer durable project facts over session-specific notes.
14- Match the structure and voice of nearby documents.
15
@@ −1 +1 @@
11 ---
2−description: Supabase data, storage, and RLS rules
2+description: Documentation writing rules
33 globs:
4− - "supabase/**/*"
4+ - "docs/**/*.md"
5+ - "*.md"
56 alwaysApply: false
67 ---
78
8−# Supabase Rules
9+# Documentation Rules
910
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.
11+- Write in plain, precise language for patients, contributors, and reviewers.
12+- Keep privacy, consent, patient control, and non-diagnostic AI limits visible.
13+- Prefer durable project facts over session-specific notes.
14+- Match the structure and voice of nearby documents.
1515
