| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 3 | 0 | 0% |
| Section tags | 2 | 1 | 0 | 67% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − AI Service Rules
- + Frontend Rules
Commands
0 shared · 3 only in A · 0 only in B- − python -m mypy app
- − python -m ruff check .
- − python -m pytest
Section tags
2 shared · 1 only in A · 0 only in B- − lint-format
- test
- do-not
Line diff
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
Aledon8/OpenLeukemia · .cursor/rules/frontend.mdc
@@ +1 @@
1---
2description: Frontend rules for OpenLeukemia React code
3globs:
4 - "frontend/**/*.{ts,tsx,css,html,json}"
5alwaysApply: false
6---
7
8# Frontend Rules
9
10- Keep React components typed, feature-oriented, and consistent with `frontend/src/features`.
11- Preserve mobile-first responsive behavior, light/dark themes, accessible controls, and existing CSS variables.
12- Keep patient-facing copy calm, plain, and non-diagnostic.
13- Consider empty, loading, error, and edge states before implementation.
14- Update or add Vitest coverage when behavior changes.
15
@@ −1 +1 @@
11 ---
2−description: Python FastAPI AI-service rules
2+description: Frontend rules for OpenLeukemia React code
33 globs:
4− - "ai-service/**/*.py"
4+ - "frontend/**/*.{ts,tsx,css,html,json}"
55 alwaysApply: false
66 ---
77
8−# AI Service Rules
8+# Frontend Rules
99
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.
10+- Keep React components typed, feature-oriented, and consistent with `frontend/src/features`.
11+- Preserve mobile-first responsive behavior, light/dark themes, accessible controls, and existing CSS variables.
12+- Keep patient-facing copy calm, plain, and non-diagnostic.
13+- Consider empty, loading, error, and edge states before implementation.
14+- Update or add Vitest coverage when behavior changes.
1615
