RuleStack

Configs

Stacks

Compare

Diff

RuleStack

Configs

Stacks

Compare

Diff

Read API

RuleStack

Configs

Stacks

Compare

Diff

Read API

Diff/aledon8-openleukemia-cursor-rules-ml ↔ aledon8-openleukemia-cursor-rules-consents

Comparison

A · Cursor rules · Aledon8/OpenLeukemiaB · Cursor rules · Aledon8/OpenLeukemia
What each file covers, counted
DimensionSharedOnly in AOnly in BOverlap
Sections0110%
Commands000—
Section tags100100%

What each file covers

Sections

0 shared · 1 only in A · 1 only in B
  • − ML Rules
  • + Consent Rules

Commands

neither file has any

Section tags

1 shared · 0 only in A · 0 only in B
  •   do-not

Line diff

+10 added−8 removed7 unchanged41.2% identical
Aledon8/OpenLeukemia · .cursor/rules/ml.mdc
@@ −1 @@
1---
2description: ML workspace rules
3globs:
4 - "ml/**/*"
 
 
5alwaysApply: false
6---
7 
8# ML Rules
9 
10- Keep structured ML workflows separate from LLM explanation workflows.
11- Use measurable criteria: split, metric, threshold, calibration, and known failure modes.
12- Do not commit patient-identifying or sensitive medical data.
13- Model outputs support signals and trends, not diagnosis or treatment guidance.
14- Document label assumptions, cohort limitations, and evaluation caveats near relevant code or reports.
15 
Aledon8/OpenLeukemia · .cursor/rules/consents.mdc
@@ +1 @@
1---
2description: Consent behavior rules across frontend and API
3globs:
4 - "frontend/src/features/consents/**/*"
5 - "ai-service/app/domains/consents/**/*"
6 - "ai-service/app/api/v1/consents.py"
7alwaysApply: false
8---
9 
10# Consent Rules
11 
12- Consent is never implied by registration, navigation, or another consent.
13- Keep each consent separate, explicit, auditable, and reversible.
14- Do not merge cloud storage, research participation, AI improvement, or community sharing into one choice.
15- Keep frontend consent identifiers aligned with API/domain consent types.
16- Add or update tests when consent types, labels, API responses, or service behavior change.
17 
@@ −1 +1 @@
11 ---
2−description: ML workspace rules
2+description: Consent behavior rules across frontend and API
33 globs:
4− - "ml/**/*"
4+ - "frontend/src/features/consents/**/*"
5+ - "ai-service/app/domains/consents/**/*"
6+ - "ai-service/app/api/v1/consents.py"
57 alwaysApply: false
68 ---
79  
8−# ML Rules
10+# Consent Rules
911  
10−- Keep structured ML workflows separate from LLM explanation workflows.
11−- Use measurable criteria: split, metric, threshold, calibration, and known failure modes.
12−- Do not commit patient-identifying or sensitive medical data.
13−- Model outputs support signals and trends, not diagnosis or treatment guidance.
14−- Document label assumptions, cohort limitations, and evaluation caveats near relevant code or reports.
12+- Consent is never implied by registration, navigation, or another consent.
13+- Keep each consent separate, explicit, auditable, and reversible.
14+- Do not merge cloud storage, research participation, AI improvement, or community sharing into one choice.
15+- Keep frontend consent identifiers aligned with API/domain consent types.
16+- Add or update tests when consent types, labels, API responses, or service behavior change.
1517  
RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack

RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack

RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack