| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 3 | 0% |
| Section tags | 0 | 1 | 3 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Supabase Functions Memory
- + AI Service Rules
Commands
0 shared · 0 only in A · 3 only in B- + python -m mypy app
- + python -m ruff check .
- + python -m pytest
Section tags
0 shared · 1 only in A · 3 only in B- − performance
- + test
- + lint-format
- + do-not
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 · .cursor/rules/ai-service.mdc
@@ +1 @@
1---
2description: Python FastAPI AI-service rules
3globs:
4 - "ai-service/**/*.py"
5alwaysApply: false
6---
7
8# AI Service Rules
9
10- Keep FastAPI route handlers thin; put reusable behavior in `app/domains`.
11- Use explicit Pydantic request and response models.
12- Preserve strict typing and keep `python -m mypy app` clean.
13- Use `response_model` for route outputs.
14- Treat extraction and model outputs as explainable signals or candidate data, not clinical decisions.
15- Run `python -m ruff check .` and relevant `python -m pytest` tests for Python changes.
16
@@ −1 +1 @@
1−# Supabase Functions Memory
1+---
2+description: Python FastAPI AI-service rules
3+globs:
4+ - "ai-service/**/*.py"
5+alwaysApply: false
6+---
27
3−Apply this inside `supabase/functions/`.
8+# AI Service Rules
49
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.
10+- Keep FastAPI route handlers thin; put reusable behavior in `app/domains`.
11+- Use explicit Pydantic request and response models.
12+- Preserve strict typing and keep `python -m mypy app` clean.
13+- Use `response_model` for route outputs.
14+- Treat extraction and model outputs as explainable signals or candidate data, not clinical decisions.
15+- Run `python -m ruff check .` and relevant `python -m pytest` tests for Python changes.
916
