Tenant Backend Parity

Phase C/11–16 of the Movemental tenant migration — bring a tenant's Supabase-backed data layer to parity with the reference repo so stitch-migrated UI can wire real data. Walks: 11 Supabase org & tenant identity audit (MCP), 12 six-layer type-safety chain port (Drizzle → Zod → Services → Routes → Hooks → UI) + validate:all, 13 services & API routes parity, 14 hooks layer parity, 15 tenant.config.ts ↔ DB feature alignment, 16 backend validation & cutover. Use when the user says "port the backend", "type safety chain", "services/hooks parity", "align the tenant config with the database", "feature flags vs db", "verify tenant org", or finishes the stitch UI and needs live data. Tenant-agnostic: org id, project id, reference repo, and leak patterns come from TENANT_MANIFEST.md. Delegates to tenant-migrate, type-safety-chain, validate, tenant-check.

JoshuaShepherd Updated 1 repo stars

File contents

JoshuaShepherd/my-skills/tree/main/claude/movemental/tenant-backend-parity commit 11c66ac2ab

Frequently asked questions

npx skillmds@latest add joshuashepherd/tenant-backend-parity