Crée un site de réservation pour restaurant avec l'IA

Choisis le type de projet

Site de réservation de restaurant

Site de réservation de clinique dentaire

Site de réservation de salon de coiffure

Site de réservation de barbier

Site de réservation de spa

Site de réservation de coach sportif

Site de réservation de coaching

Site de réservation de restaurant

Site de réservation de salon de beauté

Site de réservation de massage thérapeutique

Site de réservation de salon d'ongles

Site de réservation de photographe

Site de réservation de toilettage canin

Site de réservation de studio de yoga

Site de réservation de studio de tatouage

Site de réservation de cours de danse

Site de réservation de cours de fitness

Site de réservation de thérapie et accompagnement

Site de réservation de chiropracteur

Site de réservation de kinésithérapeute

Site de réservation de detailing auto

Site de réservation de garage auto

Site de réservation de service de ménage

Site de réservation de réparations à domicile

Site de réservation d'entretien de pelouse

Site de réservation d'organisateur d'événements

Site de réservation de wedding planner

Site de réservation de maquilleuse

Site de réservation d'esthéticienne

Site de réservation de tuteur privé

Site de réservation d'auto-école

Site de réservation de visites immobilières

Site de réservation d'agent immobilier

Aperçu du flux de réservation

- Sélectionner le service

- Sélectionner la date

- Sélectionner l'heure

- Confirmer la réservation

Détails du client collectés

- Nom complet

- E-mail

- Téléphone

- Notes optionnelles

Créer un projet Supabase

Crée un nouveau projet Supabase pour le backend de ton système de réservation.

Créer l'utilisateur admin

Crée un utilisateur admin dans Supabase Authentication, puis copie le user ID.

Lancer le SQL de configuration complète

Colle ton user ID admin, puis exécute ce code SQL dans le SQL Editor de Supabase. Il va tout configurer d'un coup : tables, politiques de sécurité et accès admin.

SQL de configuration complète

create table restaurant_tables ( id uuid primary key default gen_random_uuid(), table_name text not null, capacity integer not null check (capacity > 0), area text, is_active boolean not null default true, created_at timestamp with time zone default now() ); create table menu_items ( id uuid primary key default gen_random_uuid(), name text not null, description text, price numeric(10,2), category text, is_featured boolean not null default false, is_active boolean not null default true, created_at timestamp with time zone default now() ); create table reservations ( id uuid primary key default gen_random_uuid(), full_name text not null, email text not null, phone text not null, party_size integer not null check (party_size > 0), table_id uuid not null references restaurant_tables(id) on delete restrict, reservation_date date not null, start_time time not null, end_time time not null, status text not null default 'pending' check (status in ('pending', 'confirmed', 'cancelled', 'completed')), special_requests text, created_at timestamp with time zone default now() ); create table business_hours ( id uuid primary key default gen_random_uuid(), weekday integer not null check (weekday between 0 and 6), is_open boolean not null default true, start_time time, end_time time ); create table blocked_dates ( id uuid primary key default gen_random_uuid(), blocked_date date not null unique, reason text, created_at timestamp with time zone default now() ); create table restaurant_settings ( id uuid primary key default gen_random_uuid(), restaurant_name text not null default 'Noir Table', restaurant_email text, restaurant_phone text, restaurant_address text, slot_interval_minutes integer not null default 30, booking_notice_hours integer not null default 2, default_reservation_duration_minutes integer not null default 90, max_party_size integer not null default 8, created_at timestamp with time zone default now() ); create table admin_users ( id uuid primary key default gen_random_uuid(), user_id uuid not null unique references auth.users(id) on delete cascade, created_at timestamp with time zone default now() ); insert into restaurant_tables (table_name, capacity, area) values ('Table 1', 2, 'Main Dining Room'), ('Table 2', 2, 'Main Dining Room'), ('Table 3', 4, 'Main Dining Room'), ('Table 4', 4, 'Main Dining Room'), ('Table 5', 6, 'Window Seating'), ('Table 6', 8, 'Private Corner'); insert into menu_items (name, description, price, category, is_featured) values ('Truffle Burrata', 'Creamy burrata with truffle oil, herbs, and toasted sourdough.', 18, 'Starters', true), ('Seared Salmon', 'Pan-seared salmon with seasonal vegetables and lemon butter sauce.', 32, 'Mains', true), ('Ribeye Steak', 'Grilled ribeye with roasted potatoes and house peppercorn sauce.', 42, 'Mains', true), ('Mushroom Risotto', 'Creamy arborio rice with wild mushrooms and parmesan.', 26, 'Mains', true), ('Chocolate Fondant', 'Warm chocolate fondant with vanilla cream.', 14, 'Desserts', true), ('Signature Mocktail', 'Refreshing house mocktail with citrus, mint, and seasonal fruit.', 12, 'Drinks', true); insert into business_hours (weekday, is_open, start_time, end_time) values (0, true, '12:00', '22:00'), (1, true, '12:00', '22:00'), (2, true, '12:00', '22:00'), (3, true, '12:00', '22:00'), (4, true, '12:00', '23:00'), (5, true, '12:00', '23:00'), (6, true, '12:00', '22:00'); insert into restaurant_settings ( restaurant_name, restaurant_email, restaurant_phone, restaurant_address, slot_interval_minutes, booking_notice_hours, default_reservation_duration_minutes, max_party_size ) values ('Noir Table', 'hello@noirtable.com', '+1 555 789 4560', '88 West Dining Street, New York, NY', 30, 2, 90, 8); alter table admin_users enable row level security; alter table restaurant_tables enable row level security; alter table menu_items enable row level security; alter table reservations enable row level security; alter table business_hours enable row level security; alter table blocked_dates enable row level security; alter table restaurant_settings enable row level security; create policy "Anyone can read active restaurant tables" on restaurant_tables for select to anon, authenticated using (is_active = true); create policy "Admins can manage restaurant tables" on restaurant_tables for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can read active menu items" on menu_items for select to anon, authenticated using (is_active = true); create policy "Admins can manage menu items" on menu_items for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can create reservations" on reservations for insert to anon, authenticated with check (true); create policy "Admins can read reservations" on reservations for select to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Admins can update reservations" on reservations for update to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can read business hours" on business_hours for select to anon, authenticated using (true); create policy "Admins can manage business hours" on business_hours for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can read blocked dates" on blocked_dates for select to anon, authenticated using (true); create policy "Admins can manage blocked dates" on blocked_dates for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can read restaurant settings" on restaurant_settings for select to anon, authenticated using (true); create policy "Admins can manage restaurant settings" on restaurant_settings for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Users can read their own admin row" on admin_users for select to authenticated using (auth.uid() = user_id); insert into admin_users (user_id) values ('PASTE_YOUR_AUTH_USER_ID_HERE');

User ID admin

Saisis ton user ID Supabase Auth

Configuration SQL étape par étape (optionnel)

Créer les tables de la base de données

Lance ces requêtes SQL dans le SQL Editor de Supabase.

Tables du restaurant

create table restaurant_tables ( id uuid primary key default gen_random_uuid(), table_name text not null, capacity integer not null check (capacity > 0), area text, is_active boolean not null default true, created_at timestamp with time zone default now() );

Éléments du menu

create table menu_items ( id uuid primary key default gen_random_uuid(), name text not null, description text, price numeric(10,2), category text, is_featured boolean not null default false, is_active boolean not null default true, created_at timestamp with time zone default now() );

Réservations

create table reservations ( id uuid primary key default gen_random_uuid(), full_name text not null, email text not null, phone text not null, party_size integer not null check (party_size > 0), table_id uuid not null references restaurant_tables(id) on delete restrict, reservation_date date not null, start_time time not null, end_time time not null, status text not null default 'pending' check (status in ('pending', 'confirmed', 'cancelled', 'completed')), special_requests text, created_at timestamp with time zone default now() );

Table des horaires du business

create table business_hours ( id uuid primary key default gen_random_uuid(), weekday integer not null check (weekday between 0 and 6), is_open boolean not null default true, start_time time, end_time time );

Table des dates bloquées

create table blocked_dates ( id uuid primary key default gen_random_uuid(), blocked_date date not null unique, reason text, created_at timestamp with time zone default now() );

Paramètres du restaurant

create table restaurant_settings ( id uuid primary key default gen_random_uuid(), restaurant_name text not null default 'Noir Table', restaurant_email text, restaurant_phone text, restaurant_address text, slot_interval_minutes integer not null default 30, booking_notice_hours integer not null default 2, default_reservation_duration_minutes integer not null default 90, max_party_size integer not null default 8, created_at timestamp with time zone default now() );

Ajouter les données initiales

Lance ces requêtes initiales.

Insérer les tables du restaurant

insert into restaurant_tables (table_name, capacity, area) values ('Table 1', 2, 'Main Dining Room'), ('Table 2', 2, 'Main Dining Room'), ('Table 3', 4, 'Main Dining Room'), ('Table 4', 4, 'Main Dining Room'), ('Table 5', 6, 'Window Seating'), ('Table 6', 8, 'Private Corner');

Insérer les éléments du menu

insert into menu_items (name, description, price, category, is_featured) values ('Truffle Burrata', 'Creamy burrata with truffle oil, herbs, and toasted sourdough.', 18, 'Starters', true), ('Seared Salmon', 'Pan-seared salmon with seasonal vegetables and lemon butter sauce.', 32, 'Mains', true), ('Ribeye Steak', 'Grilled ribeye with roasted potatoes and house peppercorn sauce.', 42, 'Mains', true), ('Mushroom Risotto', 'Creamy arborio rice with wild mushrooms and parmesan.', 26, 'Mains', true), ('Chocolate Fondant', 'Warm chocolate fondant with vanilla cream.', 14, 'Desserts', true), ('Signature Mocktail', 'Refreshing house mocktail with citrus, mint, and seasonal fruit.', 12, 'Drinks', true);

Insérer les horaires du business

insert into business_hours (weekday, is_open, start_time, end_time) values (0, true, '12:00', '22:00'), (1, true, '12:00', '22:00'), (2, true, '12:00', '22:00'), (3, true, '12:00', '22:00'), (4, true, '12:00', '23:00'), (5, true, '12:00', '23:00'), (6, true, '12:00', '22:00');

Insérer les paramètres du restaurant

insert into restaurant_settings ( restaurant_name, restaurant_email, restaurant_phone, restaurant_address, slot_interval_minutes, booking_notice_hours, default_reservation_duration_minutes, max_party_size ) values ('Noir Table', 'hello@noirtable.com', '+1 555 789 4560', '88 West Dining Street, New York, NY', 30, 2, 90, 8);

Sécuriser le tableau de bord admin

1. Crée la table d'accès admin Crée une table qui définit quels utilisateurs authentifiés sont autorisés à accéder au tableau de bord admin et à le gérer.

Table admin_users

create table admin_users ( id uuid primary key default gen_random_uuid(), user_id uuid not null unique references auth.users(id) on delete cascade, created_at timestamp with time zone default now() );

2. Active Row Level Security Active RLS sur les tables qui doivent être protégées des utilisateurs normaux.

Activer RLS

alter table admin_users enable row level security; alter table restaurant_tables enable row level security; alter table menu_items enable row level security; alter table reservations enable row level security; alter table business_hours enable row level security; alter table blocked_dates enable row level security; alter table restaurant_settings enable row level security;

3. Ajoute les politiques admin Permets aux utilisateurs publics de lire uniquement ce qui est nécessaire pour le site de réservation, et permets uniquement aux utilisateurs admin de gérer les données protégées.

Politiques admin

create policy "Anyone can read active restaurant tables" on restaurant_tables for select to anon, authenticated using (is_active = true); create policy "Admins can manage restaurant tables" on restaurant_tables for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can read active menu items" on menu_items for select to anon, authenticated using (is_active = true); create policy "Admins can manage menu items" on menu_items for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can create reservations" on reservations for insert to anon, authenticated with check (true); create policy "Admins can read reservations" on reservations for select to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Admins can update reservations" on reservations for update to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can read business hours" on business_hours for select to anon, authenticated using (true); create policy "Admins can manage business hours" on business_hours for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can read blocked dates" on blocked_dates for select to anon, authenticated using (true); create policy "Admins can manage blocked dates" on blocked_dates for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can read restaurant settings" on restaurant_settings for select to anon, authenticated using (true); create policy "Admins can manage restaurant settings" on restaurant_settings for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Users can read their own admin row" on admin_users for select to authenticated using (auth.uid() = user_id);

4. Ajoute ton utilisateur admin Crée d'abord ton compte admin depuis l'écran de connexion de l'app, puis insère ton user ID authentifié dans la table admin_users.

Insérer ton utilisateur admin

insert into admin_users (user_id) values ('PASTE_YOUR_AUTH_USER_ID_HERE');

Utilise le Prompt 1 pour construire le projet

Prompt 1 : Construire le projet complet de restaurant

Crée un site web de restaurant moderne et premium avec un vrai système de réservation de table et un tableau de bord admin sécurisé.

You are a world-class full-stack product builder, creative director, and UI/UX designer. Build a premium modern restaurant reservation website with a real table booking system and a secure admin dashboard. The final result should feel like it was designed by a top-tier design agency and built as a real production-ready product. Do not create a generic template. Do not create a basic admin panel. Do not make small visual improvements. Create a complete, polished, premium experience from the first version. Tech stack: - React - TypeScript - Vite - Supabase for database, backend, and auth ================================================ SUPABASE CONNECTION ================================================ Use these Supabase credentials: VITE_SUPABASE_URL=PASTE_YOUR_SUPABASE_URL_HERE VITE_SUPABASE_ANON_KEY=PASTE_YOUR_PUBLISHABLE_KEY_HERE Rules: - Use these values as environment variables - Do not hardcode them inside components - Create the Supabase client in src/lib/supabase.ts - Use import.meta.env.VITE_SUPABASE_URL and import.meta.env.VITE_SUPABASE_ANON_KEY ================================================ DATABASE SCHEMA ================================================ Use this exact schema. Do not rename fields or invent new ones. restaurant_tables: - id - table_name - capacity - area - is_active - created_at menu_items: - id - name - description - price - category - is_featured - is_active - created_at reservations: - id - full_name - email - phone - party_size - table_id - reservation_date - start_time - end_time - status - special_requests - created_at business_hours: - id - weekday - is_open - start_time - end_time blocked_dates: - id - blocked_date - reason - created_at restaurant_settings: - id - restaurant_name - restaurant_email - restaurant_phone - restaurant_address - slot_interval_minutes - booking_notice_hours - default_reservation_duration_minutes - max_party_size - created_at admin_users: - id - user_id - created_at Important: - Use restaurant_settings, not coaching_settings - Use restaurant_settings, not trainer_settings - Use restaurant_settings, not spa_settings - Use restaurant_settings, not salon_settings - Use restaurant_settings, not barbershop_settings - Use restaurant_settings, not clinic_settings - Use restaurant_name, restaurant_email, restaurant_phone, and restaurant_address - Use reservations, not appointments - Use restaurant_tables, not tables - Do not use the SQL table name "tables" - Use admin_users.user_id to check admin access - Do not check admin access by email - Do not use fake local authentication - Do not use fake local data ================================================ PROJECT GOAL ================================================ Create a complete restaurant reservation website where visitors can: - view the restaurant brand and atmosphere - view featured menu items - select party size - select a reservation date - see available time slots - submit a real table reservation - see a success confirmation Create a secure admin dashboard where the restaurant owner or manager can manage: - reservations - restaurant tables - menu items - business hours - blocked dates - restaurant settings Everything in the dashboard should be useful and editable, not just displayed. ================================================ CREATIVE DIRECTION ================================================ This project must look premium from the first version. Think like a world-class creative director. The public website should feel: - high-end - modern - warm - elegant - atmospheric - refined - inviting - trustworthy - polished - realistic for a premium local restaurant The dashboard should feel: - premium - clean - modern - product-like - organized - smooth - easy for a restaurant owner or manager to use - visually polished, not basic Design quality expectations: - Avoid generic or template-like design - Avoid flat and empty layouts - Avoid boring sections - Avoid weak spacing - Avoid basic AI-generated landing page patterns - Do not make the public website look like a simple template - Do not make the admin dashboard look like a basic starter dashboard ================================================ VISUAL DESIGN SYSTEM ================================================ Use a premium restaurant visual style: - deep charcoal, espresso, warm cream, and soft off-white backgrounds - muted gold, copper, burgundy, olive, terracotta, or amber accents - warm atmospheric contrast - refined borders - polished cards - soft shadows - layered visuals - depth - subtle gradients - tasteful lighting effects - premium typography - elegant CTA buttons - beautiful food and dining imagery Use depth, gradients, lighting, and layered visuals where appropriate. Avoid flat backgrounds. Create strong contrast and clear hierarchy. Make the interface feel intentionally designed, not assembled from default components. Typography: - improve hierarchy and readability - make headings expressive, premium, and elegant - use refined, modern, readable typography - public website can use a refined display style for headings - dashboard should stay clean, readable, and product-like Layout: - improve spacing and composition - use dynamic, modern layouts - introduce tasteful asymmetry where appropriate - avoid overly rigid or boring sections - every section should feel intentionally designed Interactions: - add smooth animations and micro-interactions - enhance hover effects and transitions - make the experience feel polished and alive - keep interactions elegant, not distracting ================================================ IMAGE AND VISUAL STORYTELLING REQUIREMENTS ================================================ The public website must use strong, high-quality, niche-specific restaurant imagery from the first version. Do not create a premium layout with no images. Do not rely only on icons, gradients, or abstract shapes. Use real, relevant imagery in the right places to make the site feel complete, appetizing, trustworthy, and premium. Image style: - premium restaurant and dining photography - warm cinematic lighting - elegant plated dishes - restaurant interior atmosphere - table setting details - chef or kitchen craftsmanship - guests dining - drinks or dessert details - refined and realistic mood - good cropping - consistent visual style across the website Good image subjects: - premium restaurant interior - guests dining at a table - waiter serving food - chef plating food - elegant table setting - signature dishes - dessert close-up - warm dining atmosphere - drinks or mocktails - open kitchen or culinary detail Do not use: - medical imagery - spa imagery - gym imagery - barbershop imagery - hair salon imagery - generic office imagery - low-resolution images - awkward stock photos - broken image links - random model portraits unrelated to restaurants - images with unsafe or unhygienic food handling Implementation: - Use reliable external image URLs if needed - Prefer high-quality Unsplash-style imagery or other stable image sources - Make sure image links actually load - Use descriptive alt text - Use object-fit: cover and intentional cropping - Keep the layout responsive - If an image fails, the layout should still look good - Keep images easy to replace later by storing image URLs in a clear data structure, config object, or component-level constants Every image should support the restaurant brand, improve trust, and make the section feel more premium. ================================================ BRAND DIRECTION ================================================ Use restaurant-specific language: - Restaurant - Dining - Guest - Reservation - Table - Party Size - Menu - Chef - Cuisine - Dinner - Lunch - Book a table - Reserve your table Do not use: - coaching - trainer - workout - spa - massage - barbershop - barber - salon - stylist - clinic - patient - dental - dentist - doctor - medical - healthcare - appointment service wording The website should feel like a premium restaurant brand, not: - a coaching website - a personal trainer website - a spa website - a barbershop website - a medical website - a generic SaaS landing page - a random food blog ================================================ PUBLIC WEBSITE ================================================ Create: - Navbar - Hero section - Menu Highlights section - About / Atmosphere section - Reservation booking section - Success confirmation screen - Footer Public website requirements: - Load featured menu items from the menu_items table - Only show active featured menu items on the public website - Use restaurant_settings for restaurant name, email, phone, and address when available - Make the reservation section polished and easy to follow - Use strong restaurant-specific imagery throughout the public website - The site should look like a real premium restaurant website, not a simple template ================================================ PUBLIC WEBSITE QUALITY EXPECTATIONS ================================================ Navbar: - refined and premium - strong restaurant brand presence - elegant spacing - polished reservation CTA Hero: - visually striking and premium - must include a strong, relevant restaurant visual - use dining imagery such as restaurant interior, plated dish, table setting, chef detail, or guests dining - use image overlays, gradients, lighting, or layered composition for depth - maintain strong text readability - strong headline hierarchy - warm and inviting supporting text - polished CTA buttons - not generic - not flat - not basic Menu Highlights: - should not look like a plain list - load featured active menu items from Supabase - make menu items feel premium and visually appetizing - use strong layout, refined typography, beautiful spacing, and polished cards or premium list design - include niche-relevant imagery or visual treatment where appropriate - show item name, description, category, and price - menu items should be dynamic from Supabase Suggested image direction for menu and restaurant sections: - Starters: elegant plated starter or table detail - Mains: plated main dish or chef presentation - Desserts: dessert close-up - Drinks: mocktail or beverage detail - Atmosphere: restaurant interior or guests dining About / Atmosphere: - warm, refined, and intentional - visually balanced - should reinforce hospitality, cuisine, quality, atmosphere, and trust - include a strong restaurant-related image or layered visual - avoid awkward empty layouts Reservation Booking: - polished and product-like - easy to follow - clear steps - party size selector - date selection - premium time slot UI - clean guest details form - clear reservation summary - elegant success state - may include subtle supporting imagery or visual accents, but do not make the reservation form harder to use Footer: - refined - premium - consistent with the brand - use restaurant settings where relevant ================================================ RESERVATION FLOW ================================================ Step 1: Select party size Step 2: Select a reservation date and available time Step 3: Enter: - full name - email - phone - optional special requests Step 4: Show a success confirmation with reservation summary Reservation UI should include: - clear step indicator - party size selector - nice selected states - clean date selection - polished time slots - reservation summary - strong CTA buttons ================================================ AVAILABILITY LOGIC ================================================ Available time slots must be generated using: - business_hours - restaurant_settings.slot_interval_minutes - restaurant_settings.booking_notice_hours - restaurant_settings.default_reservation_duration_minutes - restaurant_settings.max_party_size - blocked_dates - restaurant_tables - existing reservations Rules: - Only show slots inside working hours - Skip blocked dates - Ignore cancelled reservations - Respect booking notice time - Respect max_party_size - Only use active restaurant tables - A party can only book a table where restaurant_tables.capacity >= selected party_size - For each slot, find at least one available active table with enough capacity - Do not double-book the same table - Use the default reservation duration to calculate end_time - Save the assigned table_id in the reservations table Overlap rule: new_start < existing_end AND new_end > existing_start A table is unavailable if an existing non-cancelled reservation overlaps with the new reservation time. All available slots should be normalized as: { start: Date, end: Date, label: string, tableId: string } Time safety: - Only format real Date objects - Never pass invalid strings to format() - Never use strings like "yyyy-MM-ddT10:30:00" - Always combine the selected date and time correctly - Save reservation_date as a Supabase-compatible date - Save start_time and end_time as Supabase-compatible time values ================================================ ADMIN AUTH ================================================ Create a real admin login using Supabase Auth. Admin login flow: 1. Admin enters email and password 2. Sign in with supabase.auth.signInWithPassword() 3. Get the authenticated user 4. Check if user.id exists in admin_users.user_id 5. If yes, allow access to dashboard 6. If no, show: "You are signed in, but you are not authorized as an admin." 7. Add a loading state while checking session and admin access 8. Do not redirect back to login before the admin check finishes Rules: - Protect all admin routes - Public website should stay accessible without login - Do not check admin access by email - Do not use fake local authentication - Do not rely only on hiding buttons ================================================ ADMIN DASHBOARD ================================================ Create a complete dashboard with these pages: 1. Overview 2. Reservations 3. Restaurant Tables 4. Menu Items 5. Business Hours 6. Blocked Dates 7. Restaurant Settings The dashboard must feel like a polished premium product dashboard, not a basic admin template. Dashboard visual requirements: - refined sidebar - polished page headers - beautiful cards - clean tables - premium forms - clear modals or drawers - elegant buttons - refined badges - smooth hover states - good empty states - strong spacing and hierarchy - consistent design system 1. Overview: - show useful stats - today’s reservations - upcoming reservations - pending reservations - confirmed reservations - active tables - featured menu items - use polished metric cards and useful layout 2. Reservations: - show all reservations from Supabase - show guest name, party size, table, date, time, phone, email, status, and special requests - allow filtering by status - allow updating status: - pending - confirmed - cancelled - completed - make reservation tables/cards clean, readable, and premium 3. Restaurant Tables: This page must be fully manageable, not read-only. The admin must be able to: - add new tables - edit existing tables - activate tables - deactivate tables Table fields: - table_name - capacity - area - is_active Important: - Existing tables must have an Edit action - Editing should open a polished pre-filled form, modal, drawer, or panel - Saving should update the table in Supabase - Inactive tables should stay visible in the admin dashboard - Inactive tables should not be used for public reservations - New or updated active tables must affect availability automatically 4. Menu Items: The admin must be able to: - add menu items - edit menu items - activate menu items - deactivate menu items - mark items as featured or not featured Menu item fields: - name - description - price - category - is_featured - is_active Important: - Featured active menu items should appear on the public website - Inactive menu items should stay visible in admin - Inactive menu items should not appear publicly 5. Business Hours: - allow editing each weekday - allow open/closed days - allow editing start_time and end_time - changes must affect available reservation slots - make the editor clear and easy to use 6. Blocked Dates: - allow adding blocked dates - allow removing blocked dates - show reason - blocked dates must prevent reservations - make the interface simple and polished 7. Restaurant Settings: Allow editing: - restaurant_name - restaurant_email - restaurant_phone - restaurant_address - slot_interval_minutes - booking_notice_hours - default_reservation_duration_minutes - max_party_size Updated restaurant settings should appear on the public website where relevant and affect reservation availability where relevant. ================================================ QUALITY REQUIREMENTS ================================================ - Full working app - Clean code structure - Supabase fully connected - Reservation flow working - Admin login working - Protected dashboard working - Reservations management working - Restaurant tables management working - Menu items management working - Business hours editing working - Blocked dates working - Restaurant settings editing working - Public website uses high-quality restaurant-specific imagery - Hero section includes a strong relevant restaurant visual - Menu section includes relevant niche-specific visual treatment or images - About section includes authentic restaurant imagery or visual storytelling - Images are properly cropped, responsive, and not broken - Image URLs are easy to replace later - No placeholder fake data - No disconnected dashboard pages - No read-only admin pages where editing is expected - Premium restaurant visual direction from the start - Public website should feel top-tier, not template-like - Dashboard should feel like a polished premium product - Keep functionality and visual quality strong from the first version FINAL RESULT: Create a complete, working, premium restaurant reservation platform with a high-end public website, strong niche-specific imagery, real table availability logic, and a polished admin dashboard.

Ajouter les variables d'environnement Supabase

Ajoute ton Supabase Project URL et ta Publishable Key quand Google AI Studio demande des variables d'environnement.

Améliorer ou corriger le projet (optionnel)

Prompts supplémentaires pour les corrections et améliorations

Prompt 2 : Affiner la logique de réservation

Implémente la logique publique de réservation avec beaucoup de soin en utilisant exactement le schéma Supabase existant…

Implement the public reservation logic very carefully using the existing Supabase schema exactly. ================================================ IMPORTANT ================================================ Do NOT invent, rename, or guess any field names. Use the real Supabase schema exactly as provided. Do NOT use services, appointments, or clinic_settings. Only use these fields: business_hours: - weekday - is_open - start_time - end_time blocked_dates: - blocked_date reservations: - full_name - email - phone - party_size - table_id - reservation_date - start_time - end_time - status - special_requests restaurant_tables: - id - capacity - is_active restaurant_settings: - slot_interval_minutes - booking_notice_hours - default_reservation_duration_minutes - max_party_size ================================================ GOAL ================================================ Make the public reservation logic fully stable, accurate, and production-style. When a user: - selects a party size - selects a date the app must calculate real available time slots for that exact date, and for each slot assign an available table that can seat the party. When a user submits the reservation form: - the reservation must be inserted correctly into Supabase - the new reservation must use the exact schema - the selected slot and table must stop appearing as available ================================================ RESERVATION LOGIC RULES ================================================ 1. The user selects a party size 2. The user selects a date 3. The app calculates available slots for that exact date 4. Slots must be generated only inside business hours 5. Slots must respect restaurant_settings.slot_interval_minutes 6. Each reservation length is restaurant_settings.default_reservation_duration_minutes 7. Slots must be excluded if the selected date exists in blocked_dates 8. A slot is only available if at least one active restaurant_tables row has capacity >= party_size and is not already booked for that time 9. Reservations with status = "cancelled" must NOT block tables 10. Slots that violate restaurant_settings.booking_notice_hours must be excluded 11. party_size must not exceed restaurant_settings.max_party_size 12. New reservations must be inserted with status = "pending" ================================================ OVERLAP RULE ================================================ A table is unavailable for a slot if an existing non-cancelled reservation on the same table overlaps: new_start < existing_end AND new_end > existing_start Use this exact overlap rule consistently everywhere. ================================================ SLOT STRUCTURE (VERY IMPORTANT) ================================================ Normalize all generated available slots into this exact frontend shape: { start: Date, end: Date, label: string, tableId: string } Requirements: - start and end must be real Date objects - tableId is the assigned available table for that slot - label is for display only ================================================ TIME SAFETY RULES (PREVENT CRASHES) ================================================ - Only call format(...) on real Date objects - Never pass invalid strings into parseISO or format - Never use literal datetime strings - Always combine the real selected date with the time correctly - end_time must equal start_time plus default_reservation_duration_minutes ================================================ RESERVATION INSERT RULES ================================================ When creating a new reservation, insert using the exact schema: - full_name - email - phone - party_size - table_id - reservation_date - start_time - end_time - status - special_requests Requirements: - table_id must come from the assigned available table - reservation_date must match the selected date - start_time and end_time must come from the selected normalized slot - status must be "pending" - special_requests can be null or the provided optional text ================================================ ERROR SAFETY ================================================ - if slot generation fails, log the real reason clearly - do not crash the whole component - return a safe empty state if calculation fails - render a fallback "No availability" message if no slots exist - if reservation insert fails, show a clear user-friendly error message - if reservation succeeds, move safely to the success state ================================================ FINAL RESULT ================================================ The final public reservation logic should: - use the exact Supabase schema - generate correct real available slots with an assigned table - prevent double-booking the same table - ignore cancelled reservations - respect blocked dates, business hours, notice period, and max party size - avoid "Invalid time value" errors - insert reservations correctly - behave like a real production restaurant reservation system

Prompt 3 : Construire le tableau de bord admin

Construis le tableau de bord admin en utilisant exactement le schéma Supabase existant…

Build the admin dashboard using the existing Supabase schema exactly. ================================================ IMPORTANT ================================================ Do NOT rename any fields. Do NOT invent any alternative field names. Do NOT create fake local-only dashboard data. Use Supabase as the single source of truth. Do NOT use services, appointments, or clinic_settings. This prompt is for the admin dashboard only. The admin dashboard must work with the existing project structure and existing public reservation flow. ================================================ STRICT SCHEMA USAGE ================================================ Use only the real schema fields below. reservations: - id - full_name - email - phone - party_size - table_id - reservation_date - start_time - end_time - status - special_requests - created_at restaurant_tables: - id - table_name - capacity - area - is_active - created_at menu_items: - id - name - description - price - category - is_featured - is_active - created_at business_hours: - weekday - is_open - start_time - end_time blocked_dates: - blocked_date - reason restaurant_settings: - restaurant_name - restaurant_email - restaurant_phone - restaurant_address - slot_interval_minutes - booking_notice_hours - default_reservation_duration_minutes - max_party_size ================================================ GOAL ================================================ Create a real production-style admin dashboard for managing the restaurant. The dashboard must manage: - reservations - restaurant tables - menu items - business hours - blocked dates - restaurant settings The dashboard should use Supabase as the source of truth for all reads and writes. ================================================ ACCESS AND SECURITY ================================================ The admin dashboard must be treated as a protected admin area. Requirements: - non-admin users must not be able to access admin dashboard actions - dashboard reads and writes must respect the existing project security setup - do not bypass Supabase security rules - do not use fake client-side admin protection only ================================================ DASHBOARD SECTIONS ================================================ 1. Dashboard Overview 2. Reservations 3. Restaurant Tables 4. Menu Items 5. Business Hours 6. Blocked Dates 7. Restaurant Settings ================================================ 1. DASHBOARD OVERVIEW ================================================ Show real data from Supabase for: - today's reservations - pending requests - upcoming confirmed reservations - completed reservations Use live calculated data, not placeholder metrics. ================================================ 2. RESERVATIONS ================================================ Requirements: - list all reservations - show: - guest full_name - email - phone - party_size - table - reservation date - reservation time - status - special_requests - allow filtering by status and date - allow changing status to: - pending - confirmed - cancelled - completed Important: - status changes must update Supabase immediately - keep the reservations list in sync after status changes ================================================ 3. RESTAURANT TABLES ================================================ The admin must be able to add, edit, activate, and deactivate restaurant tables. Use these fields: - table_name - capacity - area - is_active Important: - inactive tables must not be used for public reservations - new or updated active tables must affect availability automatically ================================================ 4. MENU ITEMS ================================================ The admin must be able to add, edit, activate, deactivate, and feature menu items. Use these fields: - name - description - price - category - is_featured - is_active Important: - featured active menu items should appear on the public website - inactive menu items must not appear publicly ================================================ 5. BUSINESS HOURS ================================================ Allow editing weekday rows using: - weekday - is_open - start_time - end_time Business hours changes must affect reservation availability correctly. ================================================ 6. BLOCKED DATES ================================================ Allow creating and deleting blocked dates using: - blocked_date - reason Blocked dates must prevent reservations correctly. ================================================ 7. RESTAURANT SETTINGS ================================================ Allow editing: - restaurant_name - restaurant_email - restaurant_phone - restaurant_address - slot_interval_minutes - booking_notice_hours - default_reservation_duration_minutes - max_party_size Booking-related settings should affect reservation logic correctly. ================================================ DATA RULES ================================================ - Supabase is the single source of truth - no fake data - no local-only dashboard records - no schema guessing - avoid stale UI after create / update / delete operations ================================================ FINAL RESULT ================================================ The final admin dashboard should: - use the exact Supabase schema - manage all core restaurant data - update Supabase correctly - show real reservations, tables, and menu items - affect the public reservation flow correctly - respect the existing admin security setup - behave like a real production admin dashboard

Prompt 4 : Lancer QA et stabilisation

Fais une passe complète de cohérence, QA, stabilisation et validation orientée sécurité sur tout le projet…

Do a full consistency, QA, stabilization, and security-aware validation pass across the entire project. ================================================ GOAL ================================================ Verify that the whole app is stable, clean, consistent with the real Supabase schema, aware of the existing security setup, and ready for real use. ================================================ IMPORTANT ================================================ Check everything against the real Supabase schema only. Do NOT invent or rename fields. Do NOT leave mismatched schema references. Do NOT use services, appointments, or clinic_settings. ================================================ STRICT SCHEMA VALIDATION ================================================ Verify all code uses the real schema exactly. restaurant_tables: - id - table_name - capacity - area - is_active - created_at menu_items: - id - name - description - price - category - is_featured - is_active - created_at reservations: - id - full_name - email - phone - party_size - table_id - reservation_date - start_time - end_time - status - special_requests - created_at business_hours: - weekday - is_open - start_time - end_time blocked_dates: - blocked_date - reason restaurant_settings: - restaurant_name - restaurant_email - restaurant_phone - restaurant_address - slot_interval_minutes - booking_notice_hours - default_reservation_duration_minutes - max_party_size ================================================ REMOVE INVALID FIELD REFERENCES ================================================ Search the entire codebase and remove any incorrect references to: - services - appointments - service_id - appointment_date - clinic_settings - day_of_week - open_time - close_time Only the real field names should remain. ================================================ RESERVATION FLOW QA ================================================ Verify the full reservation flow works end-to-end: 1. choose party size 2. choose date 3. available times appear correctly with an assigned table 4. choose time 5. submit reservation 6. reservation is inserted into Supabase 7. the booked table and slot disappear from availability 8. overlapping reservations on the same table are prevented 9. cancelled reservations do not block availability Also verify: - blocked dates prevent reservations correctly - business hours affect availability correctly - restaurant_settings.slot_interval_minutes, booking_notice_hours, default_reservation_duration_minutes, and max_party_size all affect availability correctly ================================================ TIME SAFETY VALIDATION ================================================ Verify all time handling is safe. - no invalid parseISO usage - no "Invalid time value" crashes - only real Date objects are passed into format() - available slots use the normalized structure { start: Date, end: Date, label: string, tableId: string } ================================================ DASHBOARD QA ================================================ Verify the admin dashboard works end-to-end: - reservations load correctly and status updates work - restaurant tables CRUD works - menu items CRUD works - business hours updates work - blocked dates work - restaurant settings save correctly Also verify: - new active tables and featured menu items affect the public site correctly - inactive tables and menu items do not appear publicly - dashboard updates remain in sync with Supabase ================================================ SECURITY / ACCESS VALIDATION ================================================ Verify the project respects the existing admin security setup. - admin dashboard routes are protected - non-admin users cannot access admin dashboard views or actions - client code does not bypass Supabase security ================================================ FINAL RESULT ================================================ After this QA pass, the project should: - match the Supabase schema exactly - have a stable reservation flow - have a stable admin dashboard - respect the existing admin security setup - avoid time formatting bugs - avoid schema mismatch bugs - be ready for real demo / production-style use

Sauvegarde le projet sur GitHub

Déployer sur Hostinger

Ouvrir Hostinger

Publie ce projet avec la même configuration que dans la vidéo.

RECOMMENDED

https://www.hostg.xyz/SHJK3

Crée une Node.js web app

Importe ton dépôt GitHub

Ajouter les variables d'environnement requises

VITE_SUPABASE_URL VITE_SUPABASE_ANON_KEY

VITE_SUPABASE_URL

URL du projet

VITE_SUPABASE_ANON_KEY

Clé anon (publique)

Récupérez ces valeurs dans Supabase

Ouvrir les paramètres API

https://supabase.com/dashboard/project/_/settings/api

Ouvre ton site web en production

Envoie les e-mails de rendez-vous automatiquement

Rends le système de réservation plus professionnel avec des e-mails de rendez-vous automatiques.

- Envoie un e-mail de nouvelle réservation à l'administrateur

- Envoie un e-mail de confirmation au patient

Mise à niveau optionnelle après le déploiement.

Fais en sorte que ton site IA envoie des e-mails automatiquement (tutoriel Supabase)

Regarder le tutoriel

https://www.youtube.com/watch?v=NK6ztA_-0cE

Envoie des SMS de rendez-vous automatiquement

Rends ton système de réservation plus professionnel avec des confirmations SMS automatiques après chaque réservation.

- Envoie une confirmation SMS au client

- Notifie aussi le propriétaire du business par SMS (optionnel)

Ajoute des notifications SMS à ton site de réservation IA

Regarder le tutoriel

https://youtu.be/AoR1FDcUuK4?si=O1Bi5azhJW7jJezF