| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 2 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 2 | 2 | 1 | 40% |
What each file covers
Sections
0 shared · 2 only in A · 1 only in B- − ML Workspace Instructions
- − Rules
- + Documentation Rules
Commands
neither file has anySection tags
2 shared · 2 only in A · 1 only in B- − monorepo
- − agent-behaviour
- + docs
- code-style
- do-not
Line diff
Aledon8/OpenLeukemia · ml/CLAUDE.md
@@ −1 @@
1# ML Workspace Instructions
2
3This directory is for training pipelines, inference experiments, evaluations, and notebooks.
4
5## Rules
6
7- Keep structured ML workflows separate from LLM explanation workflows.
8- Prefer reproducible scripts and documented evaluation outputs over one-off notebook state.
9- Do not treat model output as diagnosis, urgent clinical judgment, or treatment recommendation.
10- Track assumptions about input data, labels, validation, and limitations close to the code or report that uses them.
11- Avoid committing patient-identifying or sensitive medical data.
12- Prefer measurable success criteria: metric, split, threshold, calibration, and known failure modes.
13
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 @@
1−# ML Workspace Instructions
1+---
2+description: Documentation writing rules
3+globs:
4+ - "docs/**/*.md"
5+ - "*.md"
6+alwaysApply: false
7+---
28
3−This directory is for training pipelines, inference experiments, evaluations, and notebooks.
9+# Documentation Rules
410
5−## Rules
6−
7−- Keep structured ML workflows separate from LLM explanation workflows.
8−- Prefer reproducible scripts and documented evaluation outputs over one-off notebook state.
9−- Do not treat model output as diagnosis, urgent clinical judgment, or treatment recommendation.
10−- Track assumptions about input data, labels, validation, and limitations close to the code or report that uses them.
11−- Avoid committing patient-identifying or sensitive medical data.
12−- Prefer measurable success criteria: metric, split, threshold, calibration, and known failure modes.
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.
1315
