Build a Full Web App + Backend (Google AI Studio + Supabase)

Set Up the Supabase Project

Open Supabase

https://supabase.com/?utm_source=partner&utm_medium=social&utm_campaign=supasquad&dub_id=faVfKdcLWvKCbYNp

Create an Organization and Choose the Free Plan Create the Project and Select the Closest Region Save the Database Password Copy the Project URL and Publishable Key

Project Settings Data API

Project URL

Project Settings API Keys

Publishable Key

Prompt 1 — Supabase Connection

Supabase Connection

Create a simple Supabase connection file for this project. 1) Create a new file called: src/supabaseClient.js 2) Inside it, write a clean Supabase setup with two variables that I can replace later: const SUPABASE_URL = "{{SUPABASE_URL}}"; const SUPABASE_PUBLIC_KEY = "{{SUPABASE_KEY}}"; 3) Import createClient from "@supabase/supabase-js" and export one Supabase client: export const supabase = createClient(SUPABASE_URL, SUPABASE_PUBLIC_KEY); Make the file very simple and show clearly where I should paste my URL and my public key.

Supabase Project URL

Paste your Supabase project URL here

Supabase Publishable Key

Paste your Supabase publishable key here

Prompt 2 — Email Auth Logic

Email Auth Logic

Connect the Sign In and Sign Up pages in this project to Supabase Auth. Use the Supabase client from: src/supabaseClient.js 1) For Sign Up: - Use supabase.auth.signUp({ email, password }) 2) For Sign In: - Use supabase.auth.signInWithPassword({ email, password }) 3) After successful login or signup: - Redirect the user to the Home page ("/") 4) Add simple error handling: - If Supabase returns an error, show a small error message under the form Do not change the UI design — only add the logic to make these forms work. Show me only the updated Sign In and Sign Up files.

Prompt 3 — Email Confirmation Fix

Email Confirmation Fix

Fix Supabase auth logic so it handles unverified users correctly.

Fix Supabase auth logic: * After signUp(), if data.session is null, don’t redirect to the dashboard. * Just show: "Check your email and confirm your account before logging in." * Only redirect when a real session exists after login. * Protect private pages with supabase.auth.getSession() — if no session, redirect to /login.

Prompt 4 — Signup UX Improvement

Signup UX Improvement

Improve the UX of my Supabase email/password signup flow. Current behavior: - When the user completes Sign Up, the app goes back to the Sign In page, but there is no success message and the email field is empty. I want the following behavior: 1) After a successful Supabase signUp({ email, password }): - Do NOT auto-login. - Redirect the user to the Sign In page. - Keep / pre-fill the email they just used for signup in the Sign In form. 2) On the Sign In page: - If the user comes from a successful signup: - Show a clear success message above the form, for example: "Your account has been created. Please check your email and verify your address before logging in." - The email input should already contain the email used during signup. 3) You can pass the email from Sign Up to Sign In using: - router state, OR - a query parameter, OR - any simple, clean method that works well with this project. 4) Keep the existing design and layout exactly the same. Just add: - the logic for passing the email - the success message on the Sign In screen - and basic error handling if signup fails. Show me only the updated Sign Up and Sign In components.

Deployment (Required for Google OAuth)

Deploy the Web App

Watch Deployment Video

Watch Deployment Video

https://youtu.be/HGs-4QjyjHQ?si=b2qf5p0-stltUKw4

Add the Site URL and Redirect URL in Supabase Create a Google Cloud Project Configure the OAuth Consent Screen Create a Web OAuth Client and Add the Required URLs Add the Client ID and Client Secret to Supabase, Then Enable Google Sign-In

Prompt 5 — Google Sign-In

Google Sign-In

Make the “Continue with Google” button work using Supabase OAuth. Use the supabaseClient.js file. Add the Google login function and connect it to the button. Keep all UI exactly the same.

Prompt 6 — Generate Tables + CRUD

Generate Tables + CRUD

Generate the database tables, CRUD logic, and per-user security policies required by this app.

I want you to connect this web app to Supabase. 1) Analyze the existing project and detect all the data that should be saved in the database (for example: notes, tasks, posts, projects, or any items the app uses). 2) Based on the UI and the current features, generate the ideal SQL code to create the main table(s) in Supabase — including fields, types, timestamps, and user_id relations. Make sure rows belong only to the authenticated user using RLS + policies with auth.uid(). 3) After generating the SQL, write the Supabase code needed for: - loading the user's data - creating new items - updating items - deleting items 4) Use the existing components in the codebase without changing the design. Just replace the placeholder/local data logic with real Supabase queries. Keep everything simple, clean, and easy to copy-paste.

Create and Verify the Database

Copy the Generated SQL Open the Supabase SQL Editor Paste and Run the SQL Confirm the Tables Were Created Review the Row Level Security Policies Create a Test Record in the App Confirm the Record Appears in Supabase

Set Up Supabase Storage

Open Supabase Storage Create a Bucket Named app-files Keep the Bucket Private Open the Supabase SQL Editor Run the Storage Policies Script Confirm the Storage Policies Were Created

Storage Policies

create policy "Users can view own files" on storage.objects for select to authenticated using ( bucket_id = 'app-files' and name like (auth.uid()::text || '/%') ); create policy "Users can upload to own folder" on storage.objects for insert to authenticated with check ( bucket_id = 'app-files' and name like (auth.uid()::text || '/%') ); create policy "Users can update own files" on storage.objects for update to authenticated using ( bucket_id = 'app-files' and name like (auth.uid()::text || '/%') ); create policy "Users can delete own files" on storage.objects for delete to authenticated using ( bucket_id = 'app-files' and name like (auth.uid()::text || '/%') );

Prompt 7 — Connect File Uploads

Connect File Uploads

Connect all file upload features to the private app-files bucket using secure per-user folders.

I already created a Supabase Storage bucket named "app-files" (private) and added all required security policies so each user can only access files under their own folder. Now analyze my project and identify every place where users upload or select files (attachments, images, avatars, covers, etc.). Connect all existing upload features to Supabase Storage using this bucket: "app-files". Important folder rule: every uploaded file path must start with the user id: ${auth.uid()}/... Use a clean structure like: ${auth.uid()}/${featureName}/${itemId}/${uuid}.${extension} After uploading a file: - Save the returned file path in the correct database table according to my current data model. - Display files using signed URLs since the bucket is private. - Add delete logic: remove the file from Storage and remove its reference from the database. - Do NOT redesign the UI. Only connect the existing upload buttons/components to Supabase Storage.

Test File Uploads

Publish the Latest App Changes Open the Live Web App Sign In With a Test Account Upload a Test File Confirm the File Appears in the App Open the app-files Bucket in Supabase Confirm the File Is Stored Inside the User’s Folder

Prompt 8 — Dynamic Total Notes

Dynamic Total Notes

Make the “Total Notes” dashboard card display the signed-in user’s real note count from Supabase.

You are working on my existing Supabase-powered AI Notes project. Goal: Make the "Total Notes" card on the dashboard show the real number of notes for the currently authenticated user. Requirements: 1. Fetch the current authenticated user using: supabase.auth.getUser() 2. Count the number of notes in the "notes" table where user_id = current user id. 3. Replace the static number in the dashboard with the real count from the database. 4. Do NOT redesign the UI. Only connect the existing "Total Notes" component to real Supabase data. 5. Keep the existing clean SaaS layout untouched. 6. Make sure it updates automatically when a note is created or deleted. Only modify necessary files. Do not change styling.

Prompt 9 — Free Plan Limit

Free Plan Limit

Limit free users to three notes and show an upgrade message when the limit is reached.

Now add simple SaaS plan logic to my existing Supabase AI Notes app. Goal: Free users can create a maximum of 3 notes. Requirements: 1. Before creating a new note: - Count how many notes the current user already has. 2. If notes count >= 3: - Block note creation. - Show a clean modal or alert: "Free plan limit reached. Upgrade to Pro to create unlimited notes." 3. Do NOT redesign the UI. Keep the existing design system. 4. Keep logic simple. No Stripe integration yet. Just front-end + Supabase validation. 5. Make sure users cannot bypass this limit by calling the create function manually. Keep everything clean and production-ready.

Create Notes Until the Free Limit Is Reached Attempt to Create Another Note Confirm Note Creation Is Blocked Verify the Upgrade Message Appears

Copy the same Google AI Studio starter project used in the Supabase tutorial.

AI Notes — Full SaaS Template

Google AI Studio starter project used in the tutorial

https://aistudio.google.com/app/prompts?state=%7B%22ids%22:%5B%221KfBjV87zDbGoGj27YRjB2kHrLcDM2-4r%22%5D,%22action%22:%22open%22,%22userId%22:%22105522043497516450070%22,%22resourceKeys%22:%7B%7D%7D&usp=sharing

Instructions

Open the project link above. Sign in to your Google account if needed. Click “Remix” inside Google AI Studio. Replace the included Supabase Project URL and Publishable Key with your own values. Run the provided database and Storage SQL scripts in the Supabase SQL Editor.

IMPORTANT NOTE

Replace the included Supabase Project URL and Publishable Key before testing authentication, database, or file uploads.