| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 4 | 0% |
| Commands | 0 | 0 | 7 | 0% |
| Section tags | 1 | 1 | 3 | 20% |
What each file covers
Sections
0 shared · 1 only in A · 4 only in B- − Frontend Rules
- + GitHub Copilot Instructions
- + Always Follow
- + Stack And Commands
- + Workflow
Commands
0 shared · 0 only in A · 7 only in B- + npm run lint:frontend
- + npm run typecheck:frontend
- + npm test --workspace frontend
- + npm --workspace frontend run build
- + python -m ruff check .
- + python -m pytest
- + python -m mypy app
Section tags
1 shared · 1 only in A · 3 only in B- − do-not
- + lint-format
- + code-style
- + agent-behaviour
- test
Line diff
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
Aledon8/OpenLeukemia · .github/copilot-instructions.md
@@ +1 @@
1# GitHub Copilot Instructions
2
3OpenLeukemia is a patient-centered leukemia data platform. It organizes medical data, tracks changes over time, extracts structured information from documents, and explains validated model outputs in plain language.
4
5## Always Follow
6
7- Preserve explicit consent, privacy-by-default behavior, and patient ownership of data.
8- Registration is not blanket consent.
9- AI output may summarize, extract, and explain; it must not diagnose, recommend treatment, or make urgent clinical judgments.
10- Treat LLM extraction as candidate data until validated or confirmed.
11- Prefer minimal, focused changes that match nearby code.
12- Do not introduce dependencies, API changes, schema changes, or consent-flow changes without clear need.
13- Add or update tests when behavior changes.
14- Run or recommend the relevant check after changes.
15
16## Stack And Commands
17
18- Frontend: React 19, TypeScript, Vite, Vitest, ESLint.
19- Platform: Supabase Auth, Postgres, Storage, RLS, Edge Functions.
20- AI service: Python 3.12, FastAPI, Pydantic, Uvicorn.
21- Frontend checks: `npm run lint:frontend`, `npm run typecheck:frontend`, `npm test --workspace frontend`, `npm --workspace frontend run build`.
22- AI-service checks from `ai-service/`: `python -m ruff check .`, `python -m pytest`, `python -m mypy app`.
23
24## Workflow
25
26- Read nearby files before editing and follow the existing pattern.
27- For multi-file or risky changes, identify touched files and verification steps before implementation.
28- Use artifacts as primary evidence: errors, logs, screenshots, issues, plans, and referenced files.
29- Verify work with tests, build, lint, typecheck, or visual comparison when practical.
30
@@ −1 +1 @@
1−---
2−description: Frontend rules for OpenLeukemia React code
3−globs:
4− - "frontend/**/*.{ts,tsx,css,html,json}"
5−alwaysApply: false
6−---
1+# GitHub Copilot Instructions
72
8−# Frontend Rules
3+OpenLeukemia is a patient-centered leukemia data platform. It organizes medical data, tracks changes over time, extracts structured information from documents, and explains validated model outputs in plain language.
94
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.
5+## Always Follow
6+
7+- Preserve explicit consent, privacy-by-default behavior, and patient ownership of data.
8+- Registration is not blanket consent.
9+- AI output may summarize, extract, and explain; it must not diagnose, recommend treatment, or make urgent clinical judgments.
10+- Treat LLM extraction as candidate data until validated or confirmed.
11+- Prefer minimal, focused changes that match nearby code.
12+- Do not introduce dependencies, API changes, schema changes, or consent-flow changes without clear need.
13+- Add or update tests when behavior changes.
14+- Run or recommend the relevant check after changes.
15+
16+## Stack And Commands
17+
18+- Frontend: React 19, TypeScript, Vite, Vitest, ESLint.
19+- Platform: Supabase Auth, Postgres, Storage, RLS, Edge Functions.
20+- AI service: Python 3.12, FastAPI, Pydantic, Uvicorn.
21+- Frontend checks: `npm run lint:frontend`, `npm run typecheck:frontend`, `npm test --workspace frontend`, `npm --workspace frontend run build`.
22+- AI-service checks from `ai-service/`: `python -m ruff check .`, `python -m pytest`, `python -m mypy app`.
23+
24+## Workflow
25+
26+- Read nearby files before editing and follow the existing pattern.
27+- For multi-file or risky changes, identify touched files and verification steps before implementation.
28+- Use artifacts as primary evidence: errors, logs, screenshots, issues, plans, and referenced files.
29+- Verify work with tests, build, lint, typecheck, or visual comparison when practical.
1530
