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-github-instructions-docs-instructions

Comparison

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

What each file covers

Sections

0 shared · 1 only in A · 1 only in B
  • − Supabase Rules
  • + Documentation Instructions

Commands

neither file has any

Section tags

0 shared · 1 only in A · 3 only in B
  • − do-not
  • + code-style
  • + agent-behaviour
  • + docs

Line diff

+6 added−10 removed5 unchanged33.3% 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 · .github/instructions/docs.instructions.md
@@ +1 @@
1---
2applyTo: "docs/**/*.md,*.md"
 
 
 
3---
4 
5# Documentation Instructions
6 
7- Write in plain, precise language for patients, contributors, and reviewers.
8- Keep privacy, consent, patient control, and non-diagnostic AI limits visible.
9- Prefer durable project facts over session-specific notes.
10- Match the structure and voice of nearby documents.
 
11 
@@ −1 +1 @@
11 ---
2−description: Supabase data, storage, and RLS rules
3−globs:
4− - "supabase/**/*"
5−alwaysApply: false
2+applyTo: "docs/**/*.md,*.md"
63 ---
74  
8−# Supabase Rules
5+# Documentation Instructions
96  
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.
7+- Write in plain, precise language for patients, contributors, and reviewers.
8+- Keep privacy, consent, patient control, and non-diagnostic AI limits visible.
9+- Prefer durable project facts over session-specific notes.
10+- Match the structure and voice of nearby documents.
1511  
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