Cramer Supabase Ops
Purpose
Enable safe, fast data operations in Supabase while keeping changes aligned with Cramer backend documentation.
Workflow
- •Read docs first:
- •
docs/library/backend/DATABASE_SCHEMA.md - •
docs/library/backend/ENTITIES.md - •
docs/library/backend/SERVICES.md - •
docs/library/backend/API_REFERENCE.md
- •
- •Verify schema live using MCP
supabasebefore writing. - •Prefer direct table operations for routine edits.
- •For any destructive operation, ask for explicit confirmation before executing:
- •Deletes
- •Truncations
- •Schema changes
- •Bulk updates (affecting many rows)
- •When a write is needed, show the intended change, the target table(s), and the criteria.
- •After changes, summarize what was modified and note any follow-up updates needed in docs.
Guardrails
- •Always ask before destructive operations (delete/truncate/schema/bulk updates).
- •If the docs and the live schema disagree, pause and report the mismatch before writing.
- •When unsure, run a read-only query first to validate scope.
Project Structure Notes
- •Backend code lives in
backend/src/main/java/com/cramer/.... - •Keep data operations consistent with documented entities and services.