| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 3 | 4 | 0% |
| Commands | 1 | 4 | 6 | 9% |
| Section tags | 2 | 1 | 2 | 40% |
What each file covers
Sections
0 shared · 3 only in A · 4 only in B- − Frontend Instructions
- − Commands
- − Rules
- + GitHub Copilot Instructions
- + Always Follow
- + Stack And Commands
- + Workflow
Commands
1 shared · 4 only in A · 6 only in B- − npm --workspace frontend run dev
- − npm --workspace frontend run lint
- − npm --workspace frontend run typecheck
- − npm --workspace frontend run test
- + npm run lint:frontend
- + npm run typecheck:frontend
- + npm test --workspace frontend
- + python -m ruff check .
- + python -m pytest
- + python -m mypy app
- npm --workspace frontend run build
Section tags
2 shared · 1 only in A · 2 only in B- − do-not
- + lint-format
- + code-style
- test
- agent-behaviour
Line diff
Aledon8/OpenLeukemia · frontend/CLAUDE.md
@@ −1 @@
1# Frontend Instructions
2
3This directory contains the React + TypeScript + Vite application.
4
5## Commands
6
7Run from the repository root unless you are already inside `frontend/`:
8
9```sh
10npm --workspace frontend run dev
11npm --workspace frontend run lint
12npm --workspace frontend run typecheck
13npm --workspace frontend run test
14npm --workspace frontend run build
15```
16
17## Rules
18
19- Keep components feature-oriented under `src/features/` unless shared app-level code is a better fit.
20- Preserve mobile-first responsive behavior, light/dark theme support, and accessible interactions.
21- Keep patient-facing copy calm, plain, and non-diagnostic.
22- Reuse existing CSS variables and layout patterns in `src/styles/global.css`.
23- Add or update Vitest tests when UI behavior changes.
24- For visual UI work, compare against the existing page or supplied design and verify desktop and mobile states.
25
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−# Frontend Instructions
1+# GitHub Copilot Instructions
22
3−This directory contains the React + TypeScript + Vite application.
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.
44
5−## Commands
5+## Always Follow
66
7−Run from the repository root unless you are already inside `frontend/`:
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.
815
9−```sh
10−npm --workspace frontend run dev
11−npm --workspace frontend run lint
12−npm --workspace frontend run typecheck
13−npm --workspace frontend run test
14−npm --workspace frontend run build
15−```
16+## Stack And Commands
1617
17−## Rules
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`.
1823
19−- Keep components feature-oriented under `src/features/` unless shared app-level code is a better fit.
20−- Preserve mobile-first responsive behavior, light/dark theme support, and accessible interactions.
21−- Keep patient-facing copy calm, plain, and non-diagnostic.
22−- Reuse existing CSS variables and layout patterns in `src/styles/global.css`.
23−- Add or update Vitest tests when UI behavior changes.
24−- For visual UI work, compare against the existing page or supplied design and verify desktop and mobile states.
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.
2530
