| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 1 | 2 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Consent Instructions
- + Frontend Rules
Commands
neither file has anySection tags
0 shared · 1 only in A · 2 only in B- − agent-behaviour
- + test
- + do-not
Line diff
Aledon8/OpenLeukemia · .github/instructions/consents.instructions.md
@@ −1 @@
1---
2applyTo: "frontend/src/features/consents/**/*,ai-service/app/domains/consents/**/*,ai-service/app/api/v1/consents.py"
3---
4
5# Consent Instructions
6
7- Consent is never implied by registration, navigation, or another consent.
8- Keep each consent separate, explicit, auditable, and reversible.
9- Do not merge cloud storage, research participation, AI improvement, or community sharing into one choice.
10- Keep frontend consent identifiers aligned with API/domain consent types.
11- Add or update tests when consent types, labels, API responses, or service behavior change.
12
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−applyTo: "frontend/src/features/consents/**/*,ai-service/app/domains/consents/**/*,ai-service/app/api/v1/consents.py"
2+description: Frontend rules for OpenLeukemia React code
3+globs:
4+ - "frontend/**/*.{ts,tsx,css,html,json}"
5+alwaysApply: false
36 ---
47
5−# Consent Instructions
8+# Frontend Rules
69
7−- Consent is never implied by registration, navigation, or another consent.
8−- Keep each consent separate, explicit, auditable, and reversible.
9−- Do not merge cloud storage, research participation, AI improvement, or community sharing into one choice.
10−- Keep frontend consent identifiers aligned with API/domain consent types.
11−- Add or update tests when consent types, labels, API responses, or service behavior change.
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.
1215
