RuleStack

Configs

Stacks

Compare

Diff

RuleStack

Configs

Stacks

Compare

Diff

Read API

RuleStack

Configs

Stacks

Compare

Diff

Read API

Diff/aledon8-openleukemia-cursor-rules-supabase ↔ aledon8-openleukemia-ml-inference-claude

Comparison

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

What each file covers

Sections

0 shared · 1 only in A · 1 only in B
  • − Supabase Rules
  • + ML Inference Memory

Commands

neither file has any

Section tags

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

Line diff

+6 added−12 removed3 unchanged20.0% identical
Aledon8/OpenLeukemia · .cursor/rules/supabase.mdc
@@ −1 @@
1---
2description: Supabase data, storage, and RLS rules
3globs:
4 - "supabase/**/*"
5alwaysApply: false
6---
7 
8# Supabase Rules
9 
10- Use Supabase for auth, CRUD, storage, consent records, RLS, and lightweight Edge Functions.
11- Keep heavy ML, OCR, extraction, parsing, and model workflows in `ai-service`.
12- Treat RLS as a primary protection layer.
13- Pair sensitive tables with narrow, auditable policies.
14- Plan affected data flows and access paths before schema or policy changes.
15 
Aledon8/OpenLeukemia · ml/inference/CLAUDE.md
@@ +1 @@
1# ML Inference Memory
 
 
 
 
 
2 
3Apply this inside `ml/inference/`.
4 
5- Keep inference interfaces typed, deterministic, and easy to validate.
6- Return explainable scores or signals with limitations, not clinical conclusions.
7- Preserve compatibility with `ai-service/` consumers when inference code is promoted.
8- Validate feature order, units, and missing-value behavior explicitly.
 
9 
@@ −1 +1 @@
1−---
2−description: Supabase data, storage, and RLS rules
3−globs:
4− - "supabase/**/*"
5−alwaysApply: false
6−---
1+# ML Inference Memory
72  
8−# Supabase Rules
3+Apply this inside `ml/inference/`.
94  
10−- Use Supabase for auth, CRUD, storage, consent records, RLS, and lightweight Edge Functions.
11−- Keep heavy ML, OCR, extraction, parsing, and model workflows in `ai-service`.
12−- Treat RLS as a primary protection layer.
13−- Pair sensitive tables with narrow, auditable policies.
14−- Plan affected data flows and access paths before schema or policy changes.
5+- Keep inference interfaces typed, deterministic, and easy to validate.
6+- Return explainable scores or signals with limitations, not clinical conclusions.
7+- Preserve compatibility with `ai-service/` consumers when inference code is promoted.
8+- Validate feature order, units, and missing-value behavior explicitly.
159  
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