RuleStack

Configs

Stacks

Compare

Diff

RuleStack

Configs

Stacks

Compare

Diff

Read API

RuleStack

Configs

Stacks

Compare

Diff

Read API

Diff/aledon8-openleukemia-supabase-policies-claude ↔ aledon8-openleukemia-cursor-rules-docs

Comparison

A · CLAUDE.md · Aledon8/OpenLeukemiaB · Cursor rules · 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 Policies Memory
  • + Documentation Rules

Commands

neither file has any

Section tags

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

Line diff

+12 added−7 removed3 unchanged20.0% identical
Aledon8/OpenLeukemia · supabase/policies/CLAUDE.md
@@ −1 @@
1# Supabase Policies Memory
 
 
 
 
 
 
2 
3Apply this inside `supabase/policies/`.
4 
5- RLS is a primary protection layer, not a later add-on.
6- Policies should make patient ownership and explicit consent enforceable.
7- Keep access paths narrow and auditable.
8- Treat document storage and normalized clinical data as separate access concerns.
9- Review policy changes as security-sensitive even when the SQL diff is small.
10 
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−# Supabase Policies Memory
1+---
2+description: Documentation writing rules
3+globs:
4+ - "docs/**/*.md"
5+ - "*.md"
6+alwaysApply: false
7+---
28  
3−Apply this inside `supabase/policies/`.
9+# Documentation Rules
410  
5−- RLS is a primary protection layer, not a later add-on.
6−- Policies should make patient ownership and explicit consent enforceable.
7−- Keep access paths narrow and auditable.
8−- Treat document storage and normalized clinical data as separate access concerns.
9−- Review policy changes as security-sensitive even when the SQL diff is small.
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.
1015  
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