Bangun Situs Booking Salon Rambut dengan AI

Pilih tipe proyek

Situs Booking Salon Rambut

Situs Booking Klinik Gigi

Situs Booking Salon Rambut

Situs Booking Barbershop

Situs Booking Spa

Situs Booking Personal Trainer

Situs Booking Coaching

Situs Reservasi Restoran

Situs Booking Salon Kecantikan

Situs Booking Terapi Pijat

Situs Booking Salon Kuku

Situs Booking Fotografi

Situs Booking Pet Grooming

Situs Booking Studio Yoga

Situs Booking Studio Tato

Situs Booking Kelas Tari

Situs Booking Kelas Fitness

Situs Booking Terapi & Konseling

Situs Booking Chiropractor

Situs Booking Fisioterapi

Situs Booking Car Detailing

Situs Booking Bengkel Mobil

Situs Booking Layanan Pembersihan

Situs Booking Perbaikan Rumah

Situs Booking Perawatan Taman

Situs Booking Event Planner

Situs Booking Wedding Planner

Situs Booking Makeup Artist

Situs Booking Estetisien

Situs Booking Guru Privat

Situs Booking Sekolah Mengemudi

Situs Booking Tinjauan Properti

Situs Booking Agen Properti

Pratinjau alur booking

- Pilih layanan

- Pilih tanggal

- Pilih waktu

- Konfirmasi booking

Detail pelanggan terkumpul

- Nama lengkap

- Email

- Telepon

- Catatan opsional

Buat Proyek Supabase

Buat proyek Supabase baru untuk backend sistem booking Anda.

Buat Pengguna Admin

Buat pengguna admin di Supabase Authentication, lalu salin user ID.

Jalankan SQL Setup Lengkap

Tempel user ID admin Anda, lalu jalankan kode SQL ini di Supabase SQL Editor. Ini akan menyiapkan semuanya sekaligus: tabel, policy keamanan, dan akses admin.

SQL Setup Lengkap

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 salon_settings ( id uuid primary key default gen_random_uuid(), salon_name text not null default 'Luxe Hair Studio', salon_email text, salon_phone text, salon_address text, slot_interval_minutes integer not null default 30, booking_notice_hours integer not null default 2, 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 ('Women''s Haircut', 'Personalized haircut with consultation and styling finish.', 60, 65), ('Men''s Haircut', 'Clean haircut with professional styling.', 45, 45), ('Hair Coloring', 'Full color service with consultation and finish.', 120, 140), ('Blow Dry Styling', 'Wash, blow dry, and polished styling.', 45, 50), ('Hair Treatment', 'Deep conditioning treatment for softer and healthier-looking hair.', 60, 75); insert into business_hours (weekday, is_open, start_time, end_time) values (0, false, null, null), (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', '19:00'), (6, true, '10:00', '16:00'); insert into salon_settings (salon_name, salon_email, salon_phone, salon_address, slot_interval_minutes, booking_notice_hours) values ('Luxe Hair Studio', 'hello@luxehair.com', '+1 555 234 7890', '245 Madison Avenue, New York, NY', 30, 2); 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 salon_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 salon settings" on salon_settings for select to anon, authenticated using (true); create policy "Admins can manage salon settings" on salon_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

Masukkan user ID auth Supabase Anda

Setup SQL Langkah demi Langkah (Opsional)

Buat Tabel Database

Jalankan query SQL ini di dalam Supabase SQL Editor.

Tabel layanan

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() );

Tabel janji temu

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() );

Tabel jam bisnis

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 );

Tabel tanggal yang diblokir

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() );

Tabel Pengaturan

create table salon_settings ( id uuid primary key default gen_random_uuid(), salon_name text not null default 'Luxe Hair Studio', salon_email text, salon_phone text, salon_address text, slot_interval_minutes integer not null default 30, booking_notice_hours integer not null default 2, created_at timestamp with time zone default now() );

Tambahkan Data Awal

Jalankan query awal ini.

Masukkan Layanan Awal

insert into services (name, description, duration_minutes, price) values ('Women''s Haircut', 'Personalized haircut with consultation and styling finish.', 60, 65), ('Men''s Haircut', 'Clean haircut with professional styling.', 45, 45), ('Hair Coloring', 'Full color service with consultation and finish.', 120, 140), ('Blow Dry Styling', 'Wash, blow dry, and polished styling.', 45, 50), ('Hair Treatment', 'Deep conditioning treatment for softer and healthier-looking hair.', 60, 75);

Masukkan Jam Bisnis

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');

Masukkan Pengaturan

insert into salon_settings (salon_name, salon_email, salon_phone, salon_address, slot_interval_minutes, booking_notice_hours) values ('Luxe Hair Studio', 'hello@luxehair.com', '+1 555 234 7890', '245 Madison Avenue, New York, NY', 30, 2);

Amankan Dashboard Admin

1. Buat Tabel Akses Admin Buat tabel yang mendefinisikan pengguna terautentikasi mana yang diizinkan untuk mengakses dan mengelola dashboard admin.

Tabel 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. Aktifkan Row Level Security Aktifkan RLS pada tabel yang harus dilindungi dari pengguna biasa.

Aktifkan 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 salon_settings enable row level security;

3. Tambahkan Policy Admin Izinkan pengguna publik hanya membaca apa yang dibutuhkan untuk situs booking, dan izinkan hanya pengguna admin yang mengelola data yang dilindungi.

Policy 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 salon settings" on salon_settings for select to anon, authenticated using (true); create policy "Admins can manage salon settings" on salon_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. Tambahkan Pengguna Admin Anda Buat akun admin Anda terlebih dahulu dari layar login aplikasi, lalu masukkan user ID terautentikasi Anda ke dalam tabel admin_users.

Masukkan Pengguna Admin Anda

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

Gunakan Prompt 1 untuk membangun proyek

Prompt 1: Bangun Proyek Salon Rambut Lengkap

Bangun situs salon rambut modern premium dengan sistem booking nyata…

You are a world-class full-stack product builder, creative director, and UI/UX designer. Build a premium modern hair salon website with a real 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. 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 salon_settings: - id - salon_name - salon_email - salon_phone - salon_address - slot_interval_minutes - booking_notice_hours - created_at admin_users: - id - user_id - created_at Important: - Use salon_settings, not clinic_settings - Use salon_name, salon_email, salon_phone, and salon_address - 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 hair salon booking website where visitors can: - view salon services - select a service - select a date - see available time slots - enter their details - submit a real booking request - see a success confirmation Create a secure admin dashboard where the salon owner can manage: - appointments - services - business hours - blocked dates - salon 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 - visually impressive - warm - elegant - refined - stylish - trustworthy - polished - realistic for a premium local hair salon The dashboard should feel: - premium - clean - modern - product-like - organized - smooth - easy for a salon owner 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 salon visual style: - warm off-white backgrounds - champagne, beige, blush, mocha, espresso, or muted gold accents - dark charcoal / espresso text - warm gray supporting tones - refined borders - soft shadows - layered visuals - depth - subtle gradients - soft lighting effects - tasteful contrast - polished cards - strong visual hierarchy - elegant spacing - premium buttons - smooth transitions - tasteful salon imagery or visual elements Use depth, gradients, lighting, and layered visuals where appropriate. Avoid flat backgrounds. Create strong contrast and hierarchy. Make the interface feel intentionally designed, not assembled from default components. Typography: - improve hierarchy and readability - make headings expressive and premium - use elegant, 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 ================================================ BRAND DIRECTION ================================================ Use salon-specific language: - Salon - Hair Salon - Stylist - Client - Appointment - Service - Haircut - Hair Color - Styling - Treatment - Book your visit - Reserve your appointment Do not use: - clinic - patient - dental - dentist - doctor - medical - healthcare - teeth The website should feel like a premium hair salon brand, not: - a dental clinic - a medical website - a generic SaaS landing page - a fashion magazine - a perfume brand - a random beauty blog ================================================ 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 salon_settings for salon name, email, phone, and address when available - Make the booking section polished and easy to follow - The site should look like a real premium salon website, not a simple template ================================================ PUBLIC WEBSITE QUALITY EXPECTATIONS ================================================ Navbar: - refined and premium - strong brand presence - elegant spacing - polished booking CTA Hero: - visually striking and premium - strong headline hierarchy - elegant supporting text - polished CTA buttons - cinematic or layered visual composition - not generic - not flat - not basic Services: - should not look like a plain list - make services feel premium and visually engaging - use strong layout, refined typography, beautiful spacing, and polished cards or premium list design - show service name, description, duration, price, and booking affordance - services should be dynamic from Supabase About: - warm, elegant, and intentional - visually balanced - should reinforce quality, care, experience, and style - avoid awkward empty layouts Booking: - polished and product-like - easy to follow - clear steps - strong selected states - premium time slot UI - clean form design - clear appointment summary - elegant success state Footer: - refined - premium - consistent with the brand - use salon settings where relevant ================================================ BOOKING FLOW ================================================ Step 1: Select a salon service Step 2: Select a date and available time Step 3: Enter: - full name - email - phone - optional notes Step 4: Show a success confirmation with booking summary Booking UI should include: - clear step indicator - nice selected states - clean date selection - polished time slots - appointment summary - strong CTA buttons ================================================ AVAILABILITY LOGIC ================================================ Available time slots must be generated using: - business_hours - services.duration_minutes - salon_settings.slot_interval_minutes - salon_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 ================================================ 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. Appointments 3. Services 4. Business Hours 5. Blocked Dates 6. Salon 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 services - edit existing services - activate services - deactivate services 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. Salon Settings: Allow editing: - salon_name - salon_email - salon_phone - salon_address - slot_interval_minutes - booking_notice_hours Updated salon settings should appear on the public website where relevant. ================================================ QUALITY REQUIREMENTS ================================================ - Full working app - Clean code structure - Supabase fully connected - Booking flow working - Admin login working - Protected dashboard working - Services management fully working - Appointments management working - Business hours editing working - Blocked dates working - Salon settings editing working - No placeholder fake data - No disconnected dashboard pages - No read-only admin pages where editing is expected - Premium hair salon 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 hair salon booking platform with a high-end public website and a polished admin dashboard.

Tambahkan variabel environment Supabase

Tambahkan Project URL dan Publishable Key Supabase Anda saat Google AI Studio meminta variabel environment.

Tingkatkan atau perbaiki proyek (opsional)

Prompt tambahan untuk perbaikan dan peningkatan

Prompt 2: Sempurnakan Logika Booking

Implementasikan logika booking publik dengan sangat hati-hati menggunakan schema Supabase yang sudah ada persis…

Implement the public booking 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. Only use these fields: business_hours: - weekday - is_open - start_time - end_time blocked_dates: - blocked_date appointments: - appointment_date - start_time - end_time - status - service_id - full_name - email - phone - notes services: - id - duration_minutes - is_active the settings table from your schema: - slot_interval_minutes - booking_notice_hours Do NOT use any alternative field names. ================================================ GOAL ================================================ Make the public booking logic fully stable, accurate, and production-style. When a user: - selects a service - selects a date the app must calculate real available time slots for that exact date. When a user submits the booking form: - the appointment must be inserted correctly into Supabase - the new appointment must use the exact schema - the selected slot must stop appearing as available ================================================ BOOKING LOGIC RULES ================================================ 1. The user selects a service 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 the selected service duration 6. Slots must respect the slot_interval_minutes field from your settings table 7. Slots must be excluded if the selected date exists in blocked_dates 8. Slots must be excluded if they overlap with existing appointments 9. Appointments with status = "cancelled" must NOT block slots 10. Slots that violate the booking_notice_hours field from your settings table must be excluded 11. Only active services should be bookable 12. New appointments must be inserted with status = "pending" ================================================ OVERLAP RULE ================================================ A new slot conflicts if: 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 } Requirements: - start must be a real Date object - end must be a real Date object - label is for display only - use label directly in the UI - avoid rebuilding labels repeatedly during render ================================================ TIME SAFETY RULES (PREVENT CRASHES) ================================================ - Only call format(...) on real Date objects - Never pass invalid strings into parseISO or format - Never use literal strings like "yyyy-MM-ddT10:30:00" - Always combine the real selected date with the time correctly - Do not rely on unsafe manual string formatting for dates ================================================ STATE RULES ================================================ - selectedService must exist before calculating slots - selectedDate must exist before calculating slots - recalculate available slots whenever selectedService changes - recalculate available slots whenever selectedDate changes - reset availableSlots when selectedService changes - reset selectedTime when service changes - reset selectedTime when date changes - do not calculate slots if required inputs are missing ================================================ BOOKING INSERT RULES ================================================ When creating a new appointment, insert using the exact schema: - full_name - email - phone - service_id - appointment_date - start_time - end_time - status - notes Requirements: - service_id must come from the selected service - appointment_date must match the selected date - start_time and end_time must come from the selected normalized slot - status must be "pending" - notes can be null or the provided optional notes ================================================ ERROR SAFETY ================================================ Add robust error protection: - 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 booking insert fails, show a clear user-friendly error message - if booking succeeds, move safely to the success state ================================================ FINAL RESULT ================================================ The final public booking logic should: - use the exact Supabase schema - generate correct real available slots - prevent overlapping bookings - ignore cancelled bookings - respect blocked dates - respect notice period rules - avoid "Invalid time value" errors - avoid UI crashes - insert appointments correctly - remove newly booked slots from availability - behave like a real production booking system

Prompt 3: Bangun Dashboard Admin

Bangun dashboard admin menggunakan schema Supabase yang sudah ada persis…

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. This prompt is for the admin dashboard only. The admin dashboard must work with the existing project structure and existing public booking flow. ================================================ STRICT SCHEMA USAGE ================================================ Use only the real schema fields below. appointments: - id - full_name - email - phone - service_id - appointment_date - start_time - end_time - status - notes - created_at services: - id - name - description - duration_minutes - price - is_active - created_at business_hours: - weekday - is_open - start_time - end_time blocked_dates: - blocked_date - reason the settings table from your schema: - the settings name field from your schema - the settings email field from your schema - the settings phone field from your schema - the settings address field from your schema - slot_interval_minutes - booking_notice_hours Do NOT use any alternative field names. ================================================ GOAL ================================================ Create a real production-style admin dashboard for managing the business. The dashboard must manage: - appointments - services - business hours - blocked dates - 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. Appointments 3. Services 4. Business Hours 5. Blocked Dates 6. Settings ================================================ 1. DASHBOARD OVERVIEW ================================================ Show real data from Supabase for: - today's appointments - pending requests - upcoming confirmed appointments - completed appointments Use live calculated data, not placeholder metrics. ================================================ 2. APPOINTMENTS ================================================ Requirements: - list all appointments - show: - customer full_name - email - phone - service name - appointment date - appointment time - status - notes - allow filtering by: - status - date - allow changing status to: - pending - confirmed - cancelled - completed Important: - status changes must update Supabase immediately - the UI must reflect the updated status clearly - use the real service relationship to display service name - keep the appointments list in sync after status changes - do not show stale records after updates ================================================ 3. SERVICES ================================================ Requirements: - list services - create service - edit service - delete service - toggle active / inactive Use these fields: - name - description - duration_minutes - price - is_active Important: - when a new service is added in the dashboard, it must appear automatically in the public booking page if is_active = true - when is_active = false, it should not appear in the public booking flow - service updates must be reflected in the UI immediately - delete behavior must update the UI safely after success ================================================ 4. BUSINESS HOURS ================================================ Allow editing weekday rows using: - weekday - is_open - start_time - end_time Important: - business hours changes must affect booking availability correctly - do not invent different field names - saving business hours must update Supabase correctly - the UI must refresh safely after updates ================================================ 5. BLOCKED DATES ================================================ Allow: - create blocked date - delete blocked date Use: - blocked_date - reason Important: - blocked dates must affect booking availability correctly - blocked date changes must update Supabase correctly - the UI must stay in sync after create or delete ================================================ 6. SETTINGS ================================================ Allow editing: - the settings name field from your schema - the settings email field from your schema - the settings phone field from your schema - the settings address field from your schema - slot_interval_minutes - booking_notice_hours Important: - settings changes must update Supabase correctly - booking-related settings should affect booking logic correctly - the settings form should load real current values from Supabase ================================================ DATA RULES ================================================ - Supabase is the single source of truth - no fake data - no local-only dashboard records - no schema guessing - use real inserts, updates, deletes, and reads - use safe re-fetching or state synchronization after mutations - avoid stale UI after create / update / delete operations ================================================ UI / BEHAVIOR REQUIREMENTS ================================================ - dashboard must feel structured, clean, and production-style - tables must be readable - forms must be clear - status controls must be understandable - destructive actions must be handled carefully - updates must be reflected in the UI after mutation - avoid stale data after create / update / delete operations - include loading states where needed - include empty states where needed - include simple error states where needed ================================================ FINAL RESULT ================================================ The final admin dashboard should: - use the exact Supabase schema - manage all core clinic data - update Supabase correctly - reflect updates in the UI - show real appointments and services - affect the public booking flow correctly - respect the existing admin security setup - behave like a real production admin dashboard

Prompt 4: Jalankan QA & Stabilisasi

Lakukan pemeriksaan konsistensi, QA, stabilisasi, dan validasi yang sadar keamanan secara menyeluruh di seluruh proyek…

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. The result should be: - stable - production-style - schema-consistent - security-aware - free from obvious logic and formatting bugs ================================================ IMPORTANT ================================================ Check everything against the real Supabase schema only. Do NOT invent or rename fields. Do NOT leave mismatched schema references. Do NOT leave obvious placeholder bugs. Do NOT bypass the existing Supabase security setup. ================================================ STRICT SCHEMA VALIDATION ================================================ Verify all code uses the real schema exactly. 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: - weekday - is_open - start_time - end_time blocked_dates: - blocked_date - reason the settings table from your schema: - the settings name field from your schema - the settings email field from your schema - the settings phone field from your schema - the settings address field from your schema - slot_interval_minutes - booking_notice_hours ================================================ REMOVE INVALID FIELD REFERENCES ================================================ Search the entire codebase and remove any incorrect references to: - day_of_week - open_time - close_time - date (when blocked_date should be used) - customer_name - customer_email - customer_phone Only the real field names should remain. ================================================ BOOKING FLOW QA ================================================ Verify the full booking flow works end-to-end: 1. choose service 2. choose date 3. available times appear correctly 4. choose time 5. submit appointment 6. appointment is inserted into Supabase 7. booked slot disappears from availability 8. overlapping bookings are prevented 9. cancelled bookings do not block availability Also verify: - blocked dates prevent booking correctly - business hours affect availability correctly - the slot_interval_minutes field from your settings table affects slot generation correctly - the booking_notice_hours field from your settings table affects availability correctly ================================================ TIME SAFETY VALIDATION ================================================ Verify all time handling is safe. Requirements: - 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 } Also verify: - selected date and time are combined safely - no unsafe literal datetime strings are used - the booking UI does not crash when no availability exists ================================================ DASHBOARD QA ================================================ Verify the admin dashboard works end-to-end: - appointments load correctly - appointment status updates work - services CRUD works - business hours updates work - blocked dates work - settings save correctly Also verify: - new active services appear in the public booking page - inactive services do not appear in the public booking page - dashboard updates remain in sync with Supabase - create / update / delete operations refresh the UI correctly - no stale records remain after mutations ================================================ SECURITY / ACCESS VALIDATION ================================================ Verify the project respects the existing admin security setup. Requirements: - admin dashboard routes are protected - non-admin users cannot access admin dashboard views or admin actions - client code does not bypass Supabase security - writes to admin-managed data respect the existing access rules - the dashboard behaves correctly when access is denied This is a validation pass only: - do not invent a new security architecture - do not rename security-related fields - do not replace the existing security setup unless necessary to make the current setup work correctly ================================================ UI / STATE CONSISTENCY ================================================ Verify: - service selection is not duplicated - data is not rendered twice unnecessarily - there are no obvious stale state issues - availability updates correctly after booking - UI remains consistent after create / update / delete operations - public booking and admin dashboard stay aligned ================================================ LOADING / EMPTY STATES ================================================ Add simple, clean loading and empty states where needed. Examples: - loading services - loading appointments - loading settings - no availability - no appointments - no services - no blocked dates These states should be clear and production-style. ================================================ CODE QUALITY ================================================ Keep the code: - clean - production-style - readable - consistent - safe against obvious runtime issues Do not leave obvious placeholder bugs or weak fallback behavior. ================================================ FINAL RESULT ================================================ After this QA pass, the project should: - match the Supabase schema exactly - have a stable booking flow - have a stable admin dashboard - respect the existing admin security setup - avoid known time formatting bugs - avoid schema mismatch bugs - avoid duplicate selection bugs - include basic loading and empty states - be ready for real demo / production-style use

Simpan proyek ke GitHub

Deploy di Hostinger

Buka Hostinger

Terbitkan proyek ini dengan pengaturan yang sama seperti di video.

RECOMMENDED

https://www.hostg.xyz/SHJK3

Buat aplikasi web Node.js

Impor repository GitHub Anda

Tambahkan variabel environment yang diperlukan

VITE_SUPABASE_URL VITE_SUPABASE_ANON_KEY

VITE_SUPABASE_URL

URL proyek

VITE_SUPABASE_ANON_KEY

Kunci anon (publik)

Ambil nilai ini dari Supabase

Buka pengaturan API

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

Buka website live Anda

Kirim Email Janji Temu Secara Otomatis

Buat sistem booking lebih profesional dengan email janji temu otomatis.

- Kirim email booking baru kepada admin

- Kirim email konfirmasi kepada pasien

Upgrade opsional setelah deployment.

Buat Situs AI Anda Mengirim Email Secara Otomatis (Tutorial Supabase)

Tonton Tutorial

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

Kirim SMS Janji Temu Secara Otomatis

Buat sistem booking Anda lebih profesional dengan konfirmasi SMS otomatis setelah setiap booking.

- Kirim konfirmasi SMS ke pelanggan

- Beri tahu pemilik bisnis lewat SMS (opsional)

Tambahkan Notifikasi SMS ke Situs Booking AI Anda

Tonton Tutorial

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