| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 2 | 3 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Frontend Instructions
- + Documentation Rules
Commands
neither file has anySection tags
0 shared · 2 only in A · 3 only in B- − test
- − agent-behaviour
- + code-style
- + do-not
- + docs
Line diff
Aledon8/OpenLeukemia · .github/instructions/frontend.instructions.md
@@ −1 @@
1---
2applyTo: "frontend/**/*.{ts,tsx,css,html,json}"
3---
4
5# Frontend Instructions
6
7- Keep React components typed, feature-oriented, and consistent with `frontend/src/features`.
8- Preserve mobile-first responsive behavior, light/dark themes, accessible controls, and existing CSS variables.
9- Keep patient-facing copy calm, plain, and non-diagnostic.
10- For UI changes, consider empty, loading, error, and edge states.
11- Update or add Vitest coverage when behavior changes.
12
Aledon8/OpenLeukemia · .cursor/rules/docs.mdc
@@ +1 @@
1---
2description: Documentation writing rules
3globs:
4 - "docs/**/*.md"
5 - "*.md"
6alwaysApply: false
7---
8
9# Documentation Rules
10
11- Write in plain, precise language for patients, contributors, and reviewers.
12- Keep privacy, consent, patient control, and non-diagnostic AI limits visible.
13- Prefer durable project facts over session-specific notes.
14- Match the structure and voice of nearby documents.
15
@@ −1 +1 @@
11 ---
2−applyTo: "frontend/**/*.{ts,tsx,css,html,json}"
2+description: Documentation writing rules
3+globs:
4+ - "docs/**/*.md"
5+ - "*.md"
6+alwaysApply: false
37 ---
48
5−# Frontend Instructions
9+# Documentation Rules
610
7−- Keep React components typed, feature-oriented, and consistent with `frontend/src/features`.
8−- Preserve mobile-first responsive behavior, light/dark themes, accessible controls, and existing CSS variables.
9−- Keep patient-facing copy calm, plain, and non-diagnostic.
10−- For UI changes, consider empty, loading, error, and edge states.
11−- Update or add Vitest coverage when behavior changes.
11+- Write in plain, precise language for patients, contributors, and reviewers.
12+- Keep privacy, consent, patient control, and non-diagnostic AI limits visible.
13+- Prefer durable project facts over session-specific notes.
14+- Match the structure and voice of nearby documents.
1215
