makinari-obj-apps-supabase

Persist tenant-scoped data and authenticate users via Apps Supabase.

1|Updated May 8, 2025
One-click install
npx skills add https://github.com/Uncodier/API --skill makinari-obj-apps-supabase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: makinari-obj-apps-supabase
Source: https://github.com/Uncodier/API/tree/main/src/skills/makinari-obj-apps-supabase
Command: npx skills add https://github.com/Uncodier/API --skill makinari-obj-apps-supabase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill explains how to consume the Uncodie Apps Supabase (DB + Auth) inside a generated app, enabling persistent data storage, tenant-scoped authentication, and schema-change workflows without bringing your own Supabase project. The sandbox already injects the tenant envs; never bring your own Supabase project.

Core Features & Use Cases

  • Multi-tenant data access: reuse a single Apps Supabase backend across generated apps with per-tenant schema isolation.
  • Server + client integration: provides browser-ready db client and server helpers to perform authenticated operations.
  • Migrations and schema changes: guides on applying migrations within the Apps ecosystem to evolve the tenant schema safely.

Quick Start

Create a new app and integrate the Apps Supabase helpers to store tenant data and authenticate users using the sandbox-provisioned environment.

Frequently Asked Questions about makinari-obj-apps-supabase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect my app to a multi-tenant Supabase backend for data and auth?

To connect your app to a multi-tenant Supabase backend, use the provided browser and server SDK helpers to perform authenticated operations with tenant-scoped schema isolation. The sandbox injects the required environment variables automatically.

Can I bring my own Supabase project to manage app data and authentication?

No, you cannot bring your own Supabase project. This integration requires using the sandbox-provisioned Apps Supabase backend, which automatically injects the necessary tenant environment variables for database access and authentication.

What environment variables are required for tenant-scoped Supabase database access?

Tenant-scoped Supabase database access requires NEXT_PUBLIC_APPS_SUPABASE_URL, NEXT_PUBLIC_APPS_SUPABASE_ANON_KEY, NEXT_PUBLIC_APPS_TENANT_SCHEMA, APPS_TENANT_JWT, and APPS_AUTH_PROVIDER to be configured in your application environment.

How do I apply database migrations safely across multiple tenants in Supabase?

To apply database migrations safely across multiple tenants, follow the provided migrations guidance within the Apps ecosystem to evolve the tenant schema without disrupting persistent data storage or server-side data operations.

Does this Supabase integration provide server-side helpers for authenticated data operations?

Yes, this Supabase integration provides server-side helpers located in the server SDK file to perform authenticated data operations. These helpers work alongside the browser-ready client to manage tenant-scoped database access.

What is the best way to isolate data per tenant using a shared Supabase instance?

The best way to isolate data per tenant is by utilizing the sandbox-provisioned Apps Supabase backend with per-tenant schema isolation. This approach allows you to reuse a single backend across generated apps securely.