Crée un site de réservation pour visite immobilière avec Claude Code

Choisis le type de projet

Site de réservation de visites immobilières

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.

Ouvrir Supabase

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

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 services ( id uuid primary key default gen_random_uuid(), name text not null, description text, duration_minutes integer not null check (duration_minutes > 0), price numeric(10,2), is_active boolean not null default true, created_at timestamp with time zone default now() ); create table appointments ( id uuid primary key default gen_random_uuid(), full_name text not null, email text not null, phone text not null, service_id uuid not null references services(id) on delete restrict, appointment_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')), notes 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 business_settings ( id uuid primary key default gen_random_uuid(), business_name text not null default 'UrbanNest Property Viewings', business_email text, business_phone text, business_address text, slot_interval_minutes integer not null default 30, booking_notice_hours integer not null default 6, 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 services (name, description, duration_minutes, price) values ('Apartment Viewing', 'A scheduled property viewing for apartments, condos, or rental units with a guided walkthrough and basic details.', 45, 0), ('House Viewing', 'A guided viewing appointment for houses, townhomes, or family properties with time to explore key spaces.', 60, 0), ('Luxury Property Viewing', 'A private viewing appointment for premium properties with a more detailed walkthrough and consultation time.', 75, 0), ('Rental Property Viewing', 'A practical viewing appointment for rental homes, apartments, or available leasing opportunities.', 45, 0), ('Investment Property Viewing', 'A focused viewing appointment for buyers or investors interested in property details, potential, and next steps.', 60, 0), ('Virtual Property Tour', 'A remote property viewing session for clients who prefer an online walkthrough before visiting in person.', 45, 0); insert into business_hours (weekday, is_open, start_time, end_time) values (0, true, '10:00', '15:00'), (1, true, '09:00', '18:00'), (2, true, '09:00', '18:00'), (3, true, '09:00', '18:00'), (4, true, '09:00', '18:00'), (5, true, '09:00', '17:00'), (6, true, '10:00', '15:00'); insert into business_settings (business_name, business_email, business_phone, business_address, slot_interval_minutes, booking_notice_hours) values ('UrbanNest Property Viewings', 'hello@urbannestviewings.com', '+1 555 567 8901', '720 Realty Avenue, New York, NY', 30, 6); alter table admin_users enable row level security; alter table services enable row level security; alter table appointments enable row level security; alter table business_hours enable row level security; alter table blocked_dates enable row level security; alter table business_settings enable row level security; create policy "Anyone can read active services" on services for select to anon, authenticated using (is_active = true); create policy "Admins can manage services" on services 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 appointments" on appointments for insert to anon, authenticated with check (true); create policy "Admins can read appointments" on appointments for select to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Admins can update appointments" on appointments 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 business settings" on business_settings for select to anon, authenticated using (true); create policy "Admins can manage business settings" on business_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.

Table des services

create table services ( id uuid primary key default gen_random_uuid(), name text not null, description text, duration_minutes integer not null check (duration_minutes > 0), price numeric(10,2), is_active boolean not null default true, created_at timestamp with time zone default now() );

Table des rendez-vous

create table appointments ( id uuid primary key default gen_random_uuid(), full_name text not null, email text not null, phone text not null, service_id uuid not null references services(id) on delete restrict, appointment_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')), notes 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() );

Table des paramètres

create table business_settings ( id uuid primary key default gen_random_uuid(), business_name text not null default 'UrbanNest Property Viewings', business_email text, business_phone text, business_address text, slot_interval_minutes integer not null default 30, booking_notice_hours integer not null default 6, created_at timestamp with time zone default now() );

Ajouter les données initiales

Lance ces requêtes initiales.

Insérer les services initiaux

insert into services (name, description, duration_minutes, price) values ('Apartment Viewing', 'A scheduled property viewing for apartments, condos, or rental units with a guided walkthrough and basic details.', 45, 0), ('House Viewing', 'A guided viewing appointment for houses, townhomes, or family properties with time to explore key spaces.', 60, 0), ('Luxury Property Viewing', 'A private viewing appointment for premium properties with a more detailed walkthrough and consultation time.', 75, 0), ('Rental Property Viewing', 'A practical viewing appointment for rental homes, apartments, or available leasing opportunities.', 45, 0), ('Investment Property Viewing', 'A focused viewing appointment for buyers or investors interested in property details, potential, and next steps.', 60, 0), ('Virtual Property Tour', 'A remote property viewing session for clients who prefer an online walkthrough before visiting in person.', 45, 0);

Insérer les horaires du business

insert into business_hours (weekday, is_open, start_time, end_time) values (0, false, null, null), (1, true, '09:00', '17:00'), (2, true, '09:00', '17:00'), (3, true, '09:00', '17:00'), (4, true, '09:00', '17:00'), (5, true, '09:00', '17:00'), (6, true, '09:00', '13:00');

Insérer les paramètres

insert into business_settings (business_name, business_email, business_phone, business_address, slot_interval_minutes, booking_notice_hours) values ('UrbanNest Property Viewings', 'hello@urbannestviewings.com', '+1 555 567 8901', '720 Realty Avenue, New York, NY', 30, 6);

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 services enable row level security; alter table appointments enable row level security; alter table business_hours enable row level security; alter table blocked_dates enable row level security; alter table business_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 services" on services for select to anon, authenticated using (is_active = true); create policy "Admins can manage services" on services 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 appointments" on appointments for insert to anon, authenticated with check (true); create policy "Admins can read appointments" on appointments for select to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Admins can update appointments" on appointments 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 business settings" on business_settings for select to anon, authenticated using (true); create policy "Admins can manage business settings" on business_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 visites immobilières

Crée un site web de clinique dentaire moderne et premium avec un vrai système de réservation…

You are a world-class full-stack product builder, creative director, and UI/UX designer. Build a premium modern property viewing booking website with a real booking system and a secure admin dashboard. The final result should feel like it was designed by a top-tier real estate, property, and lifestyle 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 property viewing booking experience from the first version. Tech stack: - React - TypeScript - Vite - Supabase for database, backend, and auth ================================================ SUPABASE CONNECTION ================================================ Create a .env.local file in your project root with your 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 - Use the official Supabase client with normal browser session persistence - Do not manually clear or remove the Supabase session - Do not sign the admin out automatically unless the user clicks a sign out button ================================================ DATABASE SCHEMA ================================================ Use this exact schema. Do not rename fields or invent new ones. services: - id - name - description - duration_minutes - price - is_active - created_at appointments: - id - full_name - email - phone - service_id - appointment_date - start_time - end_time - status - notes - created_at business_hours: - id - weekday - is_open - start_time - end_time blocked_dates: - id - blocked_date - reason - created_at business_settings: - id - business_name - business_email - business_phone - business_address - slot_interval_minutes - booking_notice_hours - created_at admin_users: - id - user_id - created_at Important: - Use business_settings for property viewing business information. - Use business_name, business_email, business_phone, and business_address. - Do not use clinic_settings. - Do not use clinic_name, clinic_email, clinic_phone, or clinic_address. - Do not use property_settings. - Do not use viewing_settings. - Do not use real_estate_settings. - Do not use realtor_settings. - Do not use agency_settings. - Do not use listing_settings. - Do not use company_settings. - Do not use service_settings. - Do not use salon_settings. - Do not use spa_settings. - Do not use dental_settings. - Do not use barbershop_settings. - Do not use trainer_settings. - Do not use coaching_settings. - Do not rename any table or field. - Use admin_users.user_id to check admin access. - Do not check admin access by email. - Do not check admin_users.id for authorization. - Do not use fake local authentication. - Do not use fake local data. ================================================ PROJECT GOAL ================================================ Create a complete property viewing booking website where visitors can: - view property viewing services - select a viewing type - select a date - see available time slots - enter their details - submit a real appointment request - see a success confirmation Create a secure admin dashboard where the property manager, real estate team, viewing coordinator, or agency owner can manage: - appointments - services - business hours - blocked dates - business 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 for a premium property viewing and real estate brand. The public website should feel: - premium - modern - clean - elegant - trustworthy - refined - professional - polished - real-estate-focused - client-friendly - property-focused - realistic for a premium local property viewing or real estate service The dashboard should feel: - premium - clean - modern - product-like - organized - smooth - easy for a property viewing coordinator or real estate 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 - Keep the design real-estate-focused, premium, clean, trustworthy, and professional - Do not make it look like a dental clinic, beauty salon, massage studio, restaurant, gym, auto repair shop, cleaning company, tutoring website, or generic SaaS landing page ================================================ VISUAL DESIGN SYSTEM ================================================ Use a premium property viewing visual style: - clean white, warm off-white, soft beige, light gray, stone, charcoal, deep navy, and elegant neutral backgrounds - refined navy, emerald, gold, warm taupe, graphite, cream, soft blue, and real-estate-inspired accent colors - clean premium contrast - polished property viewing service cards - refined borders - soft shadows - layered visuals - subtle gradients - natural interior lighting effects - elegant professional depth - premium buttons - minimal property, home, key, calendar, and location icons - high-quality real estate and property imagery Use depth, gradients, lighting, and layered visuals where appropriate. Avoid flat backgrounds. Create clear contrast and strong hierarchy. Make the interface feel intentionally designed, not assembled from default components. Typography: - improve hierarchy and readability - make headings strong, clean, premium, and trustworthy - use modern, readable typography - avoid overly decorative fonts - dashboard should stay clean, readable, and product-like Layout: - improve spacing and composition - use modern section layouts - use premium property-service visual storytelling - introduce tasteful asymmetry where appropriate - create image-led professional compositions - avoid rigid 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 clean and professional, not distracting ================================================ IMAGE AND VISUAL STORYTELLING REQUIREMENTS ================================================ The public website must use strong, high-quality, niche-specific property viewing 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, trustworthy, premium, and property-focused. Image style: - premium real estate photography - bright modern property interiors - luxury apartments, homes, townhouses, or rental spaces - real estate agent showing a property professionally - property keys, listing documents, floor plans, and consultation details - clean natural lighting - elegant home staging - refined and realistic - good cropping - consistent visual style across the website Good image subjects: - modern apartment interior - elegant home living room - real estate agent showing a property - client viewing a bright interior space - property keys on a clean desk - floor plan, notebook, and listing documents - luxury property exterior - rental apartment viewing scene - virtual tour laptop setup - clean property consultation workspace Do not use: - dental imagery - medical clinic imagery - massage therapy imagery - beauty salon imagery - barbershop imagery - restaurant imagery - fitness imagery - automotive imagery - construction disaster scenes - messy or damaged properties as the main visual - unsafe property scenes - low-resolution images - awkward stock photos - broken image links - random model portraits unrelated to property viewing 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 property viewing brand, improve trust, and make the section feel more premium. ================================================ BRAND DIRECTION ================================================ Use property viewing-specific language: - Property Viewing - Real Estate Viewing - Viewing Appointment - Property Tour - Apartment Viewing - House Viewing - Luxury Property Viewing - Rental Property Viewing - Investment Property Viewing - Virtual Property Tour - Property Manager - Viewing Coordinator - Real Estate Team - Buyer - Renter - Client - Appointment - Viewing - Schedule your viewing - Book your property tour - Reserve your viewing appointment Do not use: - dental - dentist - patient - oral health - massage therapy - therapist - beauty salon - stylist - medical - healthcare - barber - barbershop - restaurant - reservation - table - fitness - workout - auto repair - vehicle service - cleaning service - spa treatment - tutoring session Avoid unrealistic real estate claims. Do not promise guaranteed purchase approval. Do not promise guaranteed rental approval. Do not make financial or legal guarantees. Do not use pressure-based selling language. Do not claim that every property will remain available. Focus on clarity, convenience, trust, professional guidance, property details, viewing coordination, and a polished client experience. ================================================ PUBLIC WEBSITE ================================================ Create: - Navbar - Hero section - Services section - About section - Booking section - Success confirmation screen - Footer Public website requirements: - Load real services from the services table. - Only show active services on the public website. - Use business_settings for property viewing business name, email, phone, and address when available. - Use business_name as the business name. - Use business_email as the business email. - Use business_phone as the business phone. - Use business_address as the business address. - Make the booking section polished and easy to follow. - Use strong property viewing-specific imagery throughout the public website. - The site should look like a real premium property viewing website, not a simple template. ================================================ PUBLIC WEBSITE QUALITY EXPECTATIONS ================================================ Navbar: - refined and premium - clean property viewing brand presence - elegant spacing - polished booking CTA Hero: - visually striking and premium - must include a strong, relevant property viewing visual - use imagery such as a modern apartment interior, elegant home, agent showing a property, property keys, floor plans, bright living room, or premium real estate scene - use image overlays, gradients, lighting, or layered composition for depth - maintain strong text readability - strong headline hierarchy - clear and trustworthy supporting text - polished CTA buttons - not generic - not flat - not basic Services: - should not look like a plain list - make services feel premium, clear, elegant, and visually engaging - use strong layout, refined typography, beautiful spacing, and polished cards or premium list design - include relevant visual treatment for services - service cards should include niche-relevant images or image areas where appropriate - show service name, description, duration, price, and booking affordance - services should be dynamic from Supabase Suggested image direction for services: - Apartment Viewing: bright apartment interior or condo living space - House Viewing: modern home exterior or warm living room - Luxury Property Viewing: premium interior, luxury kitchen, or elegant staged home - Rental Property Viewing: clean rental apartment or practical viewing scene - Investment Property Viewing: floor plan, listing documents, or property consultation desk - Virtual Property Tour: laptop showing property tour or online viewing setup Keep service images consistent in crop, quality, and style. Do not use damaged properties, construction disaster scenes, unsafe spaces, or unrelated real estate images. About: - professional, trustworthy, and intentional - visually balanced - should reinforce trust, convenience, property expertise, viewing coordination, local knowledge, clear communication, and professional real estate service - include a strong property viewing-related image or layered visual - avoid awkward empty layouts Booking: - polished and product-like - easy to follow - clear steps - strong selected states - premium time slot UI - clean client details form - clear appointment summary - elegant success state - may include subtle supporting imagery or visual accents, but do not make the booking form harder to use Footer: - refined - premium - consistent with the brand - use business_settings where relevant ================================================ BOOKING FLOW ================================================ Step 1: Select a property viewing type Step 2: Select a date and available time Step 3: Enter: - full name - email - phone - optional notes Step 4: Show a success confirmation with appointment summary Booking UI should include: - clear step indicator - nice selected states - clean date selection - polished time slots - appointment summary - strong CTA buttons Use client-focused and property-viewing language in the booking flow. Do not use patient-focused language. ================================================ AVAILABILITY LOGIC ================================================ Available time slots must be generated using: - business_hours - services.duration_minutes - business_settings.slot_interval_minutes - business_settings.booking_notice_hours - blocked_dates - existing appointments Rules: - Only show slots inside working hours - Skip blocked dates - Skip overlapping appointments - Ignore cancelled appointments - Respect booking notice time - Use the selected service duration to calculate end_time - New active services added from the dashboard must work in the booking flow Overlap rule: new_start < existing_end AND new_end > existing_start All slots should be normalized as: { start: Date, end: Date, label: 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 appointment_date as a Supabase-compatible date - Save start_time and end_time as Supabase-compatible time values Important booking insert rule: - When creating an appointment, do not use .insert(...).select() or .insert(...).select().single(). - Public users are allowed to insert appointments, but they are not allowed to read all appointments. - Use insert only, then show the success screen from the local booking data already available in the form. - Do not add a public SELECT policy for appointments. - Do not insert id manually. - Do not insert created_at manually. - service_id must be the selected service id from the services table. ================================================ 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. If login fails, show a clear error message. 4. After successful sign in, get the authenticated user. 5. Use the authenticated user's id. 6. Check if user.id exists in admin_users.user_id. 7. If the user exists in admin_users, allow access to dashboard. 8. If the user is authenticated but not found in admin_users, show: "You are signed in, but you are not authorized as an admin." 9. Add a loading state while checking session and admin access. 10. Do not redirect back to login before the admin check finishes. Important admin session rules: - On admin route load, call supabase.auth.getSession(). - If there is no session, stop loading and show the login form. - If there is a session, get the current user with supabase.auth.getUser(). - Query admin_users where user_id equals user.id. - Use maybeSingle(), not single(), when checking admin_users. - If a matching row exists, set isAdmin to true and show the dashboard. - If no matching row exists, set isAdmin to false and show the unauthorized message. - Always stop the loading state in a finally block. - The UI must never stay stuck on "Verifying access..." forever. - Use supabase.auth.onAuthStateChange to respond to sign in, sign out, token refresh, and session changes. - Do not sign the admin out automatically because of a temporary query error. - Do not clear local storage or remove the Supabase session manually. - Keep the admin logged in as long as Supabase has a valid session. - If a token refresh event happens, keep the dashboard available and re-check admin access if needed. Rules: - Protect all admin routes. - Public website should stay accessible without login. - Do not check admin access by email. - Do not check admin_users.id. - Do not use fake local authentication. - Do not rely only on hiding buttons. - Do not use business_settings for admin authentication. - Do not use services or appointments for admin authentication. - Admin access is only controlled by admin_users.user_id. Important: - The admin_users table contains user_id values from Supabase Auth. - The login email and password belong to a Supabase Auth user. - After login, always compare auth.user.id with admin_users.user_id. - Do not compare user.email with anything in admin_users. ================================================ ADMIN DASHBOARD ================================================ Create a complete dashboard with these pages: 1. Overview 2. Appointments 3. Services 4. Business Hours 5. Blocked Dates 6. Business 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 - upcoming appointments - pending appointments - completed appointments - active services - use polished metric cards and useful layout 2. Appointments: - show all appointments from Supabase - show client name, service, date, time, phone, email, status, and notes - allow filtering by status - allow updating status: - pending - confirmed - cancelled - completed - make appointment tables/cards clean, readable, and premium 3. Services: This page must be fully manageable, not read-only. The admin must be able to: - add new property viewing types - edit existing property viewing types - activate property viewing types - deactivate property viewing types Each service row should have clear actions. Service fields: - name - description - duration_minutes - price - is_active Important: - Existing services must have an Edit action. - Editing should open a polished pre-filled form, modal, drawer, or panel. - Saving should update the service in Supabase. - Inactive services should stay visible in the admin dashboard. - Inactive services should not appear on the public booking page. - Prefer deactivate instead of hard delete because appointments can reference services. - New or updated active services must appear automatically in the booking flow. 4. Business Hours: - allow editing each weekday - allow open/closed days - allow editing start_time and end_time - changes must affect available booking slots - make the editor clear and easy to use 5. Blocked Dates: - allow adding blocked dates - allow removing blocked dates - show reason - blocked dates must prevent bookings - make the interface simple and polished 6. Business Settings: Allow editing: - business_name - business_email - business_phone - business_address - slot_interval_minutes - booking_notice_hours In the UI, these fields can be labeled as: - Business Name - Business Email - Business Phone - Business Address - Slot Interval - Booking Notice Important: - Save updates back to business_settings. - Updated business settings should appear on the public website where relevant. ================================================ QUALITY REQUIREMENTS ================================================ - Full working app - Clean code structure - Supabase fully connected - Booking flow working - Appointment insert works without requiring public appointment read access - Admin login working - Admin session handling working - Admin verification never gets stuck forever - Protected dashboard working - Services management fully working - Appointments management working - Business hours editing working - Blocked dates working - Business settings editing working using business_settings - Public website uses high-quality property viewing-specific imagery - Hero section includes a strong relevant property viewing visual - Services section includes relevant niche-specific visual treatment or images - About section includes authentic property viewing 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 property viewing visual direction from the start - Public website should feel top-tier, not template-like - Dashboard should feel like a polished premium product - Admin auth must work using Supabase Auth user.id and admin_users.user_id - Keep functionality and visual quality strong from the first version FINAL RESULT: Create a complete, working, premium property viewing booking platform with a high-end public website, strong niche-specific imagery, working admin login, stable session handling, real appointment booking, and a polished admin dashboard.

Optionnel : Partez d'un projet prêt à l'emploi

Site de réservation de visites immobilières

Démarrez plus vite avec le projet prêt à l'emploi

PROJECT

https://profitstudio.app/template/property-viewing-booking-website

Ajouter les variables d'environnement Supabase

Ajoute l'URL de ton projet Supabase et ta Publishable Key dans un fichier .env.local pour les tests locaux.

Installer Git

Assure-toi que Git est installé sur ton ordinateur avant de pousser le projet vers GitHub.

Télécharger Git

https://git-scm.com/

Connecter VS Code à GitHub

Connecte-toi à ton compte GitHub dans VS Code.

Créer un dépôt GitHub

Crée un nouveau dépôt GitHub privé et copie l'URL du dépôt.

Pousser le projet vers GitHub

Ouvre Claude Code dans VS Code, colle le Prompt de publication GitHub sécurisé et ajoute l'URL de ton dépôt GitHub. Une fois que Claude a préparé le projet, ouvre Source Control dans VS Code, puis commit et synchronise les modifications.

Prompt de publication GitHub sécurisé

Ajoute l'URL de ton dépôt GitHub ci-dessous, puis utilise le prompt personnalisé dans Claude Code.

I already created an empty GitHub repository. GitHub repository URL: {{GITHUB_REPOSITORY_URL}} Please prepare and push this local project to that GitHub repository. Rules: - Do not change the app code, UI, design, routes, database logic, backend logic, Supabase logic, or functionality. - Only handle Git and GitHub publishing. - Check Git status, branch, remotes, .gitignore, and tracked files first. - Make sure .env and .env.local are not committed. - Make sure generated files like node_modules, dist, dist-ssr, *.tsbuildinfo, .DS_Store, and log files are ignored. - If unnecessary files are already tracked, remove them from Git tracking only. Do not delete real project files. - Use main for a new repository, unless an existing branch should be preserved. - Connect this project to the GitHub repository URL. - Create a clean commit if needed. - Push the project to GitHub. If the push fails, diagnose and fix only the Git/GitHub setup. Do not change app functionality. Before any destructive action, explain what you found and what you plan to do.

URL du dépôt GitHub

https://github.com/username/repository-name.git

Créer une application Node.js sur Hostinger

Ouvre Hostinger, crée une nouvelle application Node.js et choisis ton domaine.

Ouvrir Hostinger

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

RECOMMENDED

https://www.hostg.xyz/SHJe0

Importer le dépôt et déployer

Importe ton dépôt GitHub, ajoute les variables d'environnement requises, puis clique sur Déployer.

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

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