Crea un'app web completa + backend (Google AI Studio + Supabase)
Guida passo dopo passo per collegare la tua app Google AI Studio a Supabase e costruire un backend pronto per la produzione.
Roadmap e risorse
Autenticazione utente (Sign Up e Login)
Configura il progetto Supabase
Apri Supabase
https://supabase.com/?utm_source=partner&utm_medium=social&utm_campaign=supasquad&dub_id=faVfKdcLWvKCbYNp
Crea un'organizzazione e scegli il piano gratuito Crea il progetto e seleziona la regione più vicina Salva la password del database Copia il Project URL e la Publishable Key
Project Settings Data API
Project URL
Project Settings API Keys
Publishable Key
Prompt 1 — Connessione a Supabase
Connessione a Supabase
Crea un semplice file di connessione a Supabase per questo progetto.
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.
URL del progetto Supabase
Incolla qui la tua URL di progetto Supabase
Publishable Key di Supabase
Incolla qui la tua publishable key di Supabase
Prompt 2 — Logica di autenticazione via e-mail
Logica di autenticazione via e-mail
Collega le pagine di accesso e registrazione di questo progetto a Supabase Auth.
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 — Correzione della conferma e-mail
Correzione della conferma e-mail
Correggi la logica di autenticazione di Supabase perché gestisca correttamente gli utenti non verificati.
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 — Miglioramento della UX di registrazione
Miglioramento della UX di registrazione
Migliora la UX del flusso di registrazione con e-mail e password di Supabase.
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.
Deploy (richiesto per Google OAuth)
Distribuisci l'app web
Guarda il video di deploy
Guarda il video di deploy
https://youtu.be/HGs-4QjyjHQ?si=b2qf5p0-stltUKw4
Aggiungi il Site URL e il Redirect URL in Supabase Crea un progetto Google Cloud Configura la schermata di consenso OAuth Crea un client OAuth web e aggiungi gli URL richiesti Aggiungi Client ID e Client Secret a Supabase, poi abilita l'accesso con Google
Prompt 5 — Google Sign-In
Google Sign-In
Fai funzionare il pulsante “Continue with Google” tramite Supabase OAuth.
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.
Salvare i dati dell'utente (database)
Prompt 6 — Generare tabelle + CRUD
Generare tabelle + CRUD
Genera le tabelle del database, la logica CRUD e le policy di sicurezza per utente richieste da questa 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.
Crea e verifica il database
Copia l'SQL generato Apri l'editor SQL di Supabase Incolla ed esegui l'SQL Conferma che le tabelle siano state create Rivedi le policy di Row Level Security Crea un record di prova nell'app Conferma che il record compaia in Supabase
Upload di file (Supabase Storage)
Configura Supabase Storage
Apri Supabase Storage Crea un bucket chiamato app-files Mantieni il bucket privato Apri l'editor SQL di Supabase Esegui lo script delle policy di storage Conferma che le policy di storage siano state create
Policy di Storage
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 — Collegare gli upload dei file
Collegare gli upload dei file
Collega tutte le funzioni di caricamento file al bucket privato app-files usando cartelle sicure per utente.
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.
Testa il caricamento dei file
Pubblica le ultime modifiche dell'app Apri l'app web online Accedi con un account di prova Carica un file di prova Conferma che il file compaia nell'app Apri il bucket app-files in Supabase Conferma che il file sia salvato nella cartella dell'utente
Collegare alla UI (sistema dinamico)
Prompt 8 — Totale note dinamico
Totale note dinamico
Fai in modo che la card “Total Notes” della dashboard mostri il numero reale di note dell'utente connesso da 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 — Limite del piano gratuito
Limite del piano gratuito
Limita gli utenti gratuiti a tre note e mostra un messaggio di upgrade al raggiungimento del limite.
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.
Crea note fino a raggiungere il limite gratuito Prova a creare un'altra nota Conferma che la creazione di note sia bloccata Verifica che compaia il messaggio di upgrade
File del progetto (usati nel video)
Copia lo stesso progetto iniziale di Google AI Studio usato nel tutorial su Supabase.
AI Notes — Modello SaaS completo
Progetto iniziale di Google AI Studio usato nel 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
Istruzioni
Apri il link al progetto qui sopra. Accedi al tuo account Google se necessario. Clicca su “Remix” all'interno di Google AI Studio. Sostituisci il Project URL e la Publishable Key di Supabase inclusi con i tuoi valori. Esegui gli script SQL di database e storage forniti nell'editor SQL di Supabase.
NOTA IMPORTANTE
Sostituisci il Project URL e la Publishable Key di Supabase inclusi prima di testare autenticazione, database o caricamento file.