Bangun Situs Booking Wedding Planner dengan Claude Code

Pilih tipe proyek

Situs Booking Wedding Planner

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.

Buka Supabase

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

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 business_settings ( id uuid primary key default gen_random_uuid(), business_name text not null default 'Aurelia Weddings Studio', business_email text, business_phone text, business_address text, slot_interval_minutes integer not null default 30, booking_notice_hours integer not null default 24, 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 ('Wedding Planning Consultation', 'A first consultation to discuss your wedding vision, priorities, timeline, guest count, budget, and planning needs.', 60, 120), ('Full-Service Wedding Planning', 'A complete planning service for couples who want support with concept, vendors, timeline, details, and coordination.', 120, 750), ('Wedding Design Session', 'A creative planning session focused on style direction, color palette, ceremony details, reception design, and guest experience.', 90, 300), ('Vendor Coordination Consultation', 'A focused consultation to review vendor needs, communication flow, planning priorities, and coordination details.', 60, 180), ('Day-of Wedding Coordination', 'A coordination service designed to help the wedding day run smoothly with timeline, logistics, and detail support.', 120, 500), ('Elopement Planning Session', 'A personalized planning session for intimate weddings, elopements, micro-weddings, and simple celebration timelines.', 75, 250); 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', '16:00'), (6, true, '10:00', '14:00'); insert into business_settings (business_name, business_email, business_phone, business_address, slot_interval_minutes, booking_notice_hours) values ('Aurelia Weddings Studio', 'hello@aureliaweddings.com', '+1 555 012 6789', '418 Bridal Avenue, New York, NY', 30, 24); 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

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 business_settings ( id uuid primary key default gen_random_uuid(), business_name text not null default 'Aurelia Weddings Studio', business_email text, business_phone text, business_address text, slot_interval_minutes integer not null default 30, booking_notice_hours integer not null default 24, 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 ('Wedding Planning Consultation', 'A first consultation to discuss your wedding vision, priorities, timeline, guest count, budget, and planning needs.', 60, 120), ('Full-Service Wedding Planning', 'A complete planning service for couples who want support with concept, vendors, timeline, details, and coordination.', 120, 750), ('Wedding Design Session', 'A creative planning session focused on style direction, color palette, ceremony details, reception design, and guest experience.', 90, 300), ('Vendor Coordination Consultation', 'A focused consultation to review vendor needs, communication flow, planning priorities, and coordination details.', 60, 180), ('Day-of Wedding Coordination', 'A coordination service designed to help the wedding day run smoothly with timeline, logistics, and detail support.', 120, 500), ('Elopement Planning Session', 'A personalized planning session for intimate weddings, elopements, micro-weddings, and simple celebration timelines.', 75, 250);

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 business_settings (business_name, business_email, business_phone, business_address, slot_interval_minutes, booking_notice_hours) values ('Aurelia Weddings Studio', 'hello@aureliaweddings.com', '+1 555 012 6789', '418 Bridal Avenue, New York, NY', 30, 24);

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 business_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 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. 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 Wedding Planner Lengkap

Bangun situs klinik gigi 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 wedding planner 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 wedding, events, and luxury 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 wedding planner 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 wedding planning 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 wedding_settings. - Do not use wedding_planner_settings. - Do not use planner_settings. - Do not use event_settings. - Do not use agency_settings. - Do not use studio_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 wedding planner booking website where visitors can: - view wedding planning services - select a service - 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 wedding planner, studio owner, or planning manager 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 wedding planning studio. The public website should feel: - premium - modern - elegant - romantic but professional - refined - polished - luxurious - warm - organized - trustworthy - creative - client-friendly - realistic for a premium local wedding planning business The dashboard should feel: - premium - clean - modern - product-like - organized - smooth - easy for a wedding planning studio 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 wedding-focused, elegant, premium, creative, and professional - Do not make it look like a dental clinic, beauty salon, massage studio, restaurant, gym, auto repair shop, cleaning company, coaching website, or generic SaaS landing page ================================================ VISUAL DESIGN SYSTEM ================================================ Use a premium wedding planner visual style: - clean white, warm off-white, ivory, champagne, blush, soft beige, pearl, muted rose, charcoal, and elegant neutral backgrounds - refined gold, rose gold, muted blush, champagne, soft plum, deep navy, warm taupe, and tasteful accent colors - elegant high-end contrast - polished service cards - refined borders - soft shadows - layered visuals - subtle gradients - warm romantic lighting effects - editorial depth - premium buttons - minimal wedding and event icons - high-quality wedding planning 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, elegant, premium, and trustworthy - use modern, refined, readable typography - avoid overly decorative fonts - dashboard should stay clean, readable, and product-like Layout: - improve spacing and composition - use modern section layouts - use elegant wedding-service visual storytelling - introduce tasteful asymmetry where appropriate - create image-led editorial 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 elegant and professional, not distracting ================================================ IMAGE AND VISUAL STORYTELLING REQUIREMENTS ================================================ The public website must use strong, high-quality, niche-specific wedding planning 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, elegant, trustworthy, and premium. Image style: - premium wedding planning photography - elegant wedding tablescapes - ceremony setup, reception setup, floral arrangements, candles, stationery, and planning details - planner working with mood boards, notebooks, timelines, or client materials - sophisticated venue setup - refined celebration atmosphere - professional wedding coordination scenes - romantic but tasteful and professional - good cropping - consistent visual style across the website Good image subjects: - elegant wedding table setup - wedding planner arranging details - decorated ceremony or reception space - bridal bouquet, florals, candles, and place setting details - mood board, notebook, checklist, or planning desk - professional client consultation setting - wedding stationery, invitations, rings, or detail flat lay - venue setup before guests arrive - luxury celebration decor - wedding timeline or design planning workspace Do not use: - dental imagery - medical clinic imagery - massage therapy imagery - beauty salon imagery - barbershop imagery - restaurant kitchen imagery - fitness imagery - automotive imagery - chaotic party imagery - messy event scenes - alcohol-focused imagery - overly intimate or inappropriate wedding imagery - low-resolution images - awkward stock photos - broken image links - random model portraits unrelated to wedding planning 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 wedding planning brand, improve trust, and make the section feel more premium. ================================================ BRAND DIRECTION ================================================ Use wedding planning-specific language: - Wedding Planner - Wedding Planning Studio - Wedding Planning Services - Wedding Consultation - Full-Service Wedding Planning - Wedding Design - Vendor Coordination - Day-of Wedding Coordination - Elopement Planning - Wedding Timeline - Venue - Ceremony - Reception - Details - Guest Experience - Couple - Client - Appointment - Service - Consultation - Book your consultation - Schedule your planning session - Reserve your wedding planning appointment Do not use: - dental - dentist - patient - oral health - massage therapy - therapist - beauty salon - stylist - medical - healthcare - barber - barbershop - restaurant table booking - fitness - workout - auto repair - vehicle service - cleaning service - coaching Avoid unrealistic claims. Do not promise a perfect wedding outcome. Do not promise guaranteed vendor availability. Do not use manipulative luxury language. Do not use overly romantic or intimate language. Focus on organization, creativity, clarity, planning, details, vendor coordination, timeline support, trust, 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 wedding planning studio name, email, phone, and address when available. - Use business_name as the studio name. - Use business_email as the studio email. - Use business_phone as the studio phone. - Use business_address as the studio address. - Make the booking section polished and easy to follow. - Use strong wedding planner-specific imagery throughout the public website. - The site should look like a real premium wedding planner website, not a simple template. ================================================ PUBLIC WEBSITE QUALITY EXPECTATIONS ================================================ Navbar: - refined and premium - clean wedding planning brand presence - elegant spacing - polished booking CTA Hero: - visually striking and premium - must include a strong, relevant wedding planning visual - use imagery such as an elegant wedding table setup, decorated venue, ceremony setup, planner working on details, floral arrangements, mood board, wedding stationery, or luxury wedding design scene - use image overlays, gradients, lighting, or layered composition for depth - maintain strong text readability - strong headline hierarchy - elegant 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, elegant, organized, 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: - Wedding Planning Consultation: planner desk, notebook, mood board, or client consultation - Full-Service Wedding Planning: decorated venue, ceremony setup, or reception tablescape - Wedding Design Session: florals, color palette, styling details, or decor planning - Vendor Coordination Consultation: checklist, planning documents, or professional workspace - Day-of Wedding Coordination: timeline, venue setup, or wedding detail coordination - Elopement Planning Session: intimate ceremony detail, planning desk, or simple elegant setup Keep service images consistent in crop, quality, and style. Do not use chaotic party scenes, alcohol-focused images, or unrelated hospitality images. About: - elegant, creative, professional, and intentional - visually balanced - should reinforce trust, organization, creativity, planning experience, attention to detail, vendor coordination, and polished wedding execution - include a strong wedding planning-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 wedding planning 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 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 wedding-planning 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 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. 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: - Studio Name - Studio Email - Studio Phone - Studio 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 wedding planner-specific imagery - Hero section includes a strong relevant wedding planning visual - Services section includes relevant niche-specific visual treatment or images - About section includes authentic wedding planning 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 wedding planner 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 wedding planner 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.

Opsional: Mulai dari proyek siap pakai

Situs Booking Wedding Planner

Mulai lebih cepat dengan proyek siap pakai

PROJECT

https://profitstudio.app/template/wedding-planner-booking-website

Tambahkan variabel environment Supabase

Tambahkan Supabase Project URL dan Publishable Key di file .env.local untuk pengujian lokal.

Instal Git

Pastikan Git sudah terinstal di komputer Anda sebelum mempush proyek ke GitHub.

Unduh Git

https://git-scm.com/

Hubungkan VS Code ke GitHub

Masuk ke akun GitHub Anda di dalam VS Code.

Buat Repositori GitHub

Buat repositori GitHub privat baru dan salin URL repositori.

Push Proyek ke GitHub

Buka Claude Code di VS Code, tempel Prompt Push GitHub yang Aman, dan tambahkan URL repositori GitHub Anda. Setelah Claude mempersiapkan proyek, buka Source Control di VS Code, lalu commit dan sync perubahan.

Prompt Push GitHub yang Aman

Tambahkan URL repositori GitHub Anda di bawah ini, lalu gunakan prompt yang disesuaikan di 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 repositori GitHub

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

Buat Aplikasi Web Node.js di Hostinger

Buka Hostinger, buat aplikasi web Node.js baru, dan pilih domain Anda.

Buka Hostinger

Terbitkan proyek ini dengan pengaturan yang sama seperti di video.

RECOMMENDED

https://www.hostg.xyz/SHJe0

Import Repositori dan Deploy

Import repositori GitHub Anda, tambahkan variabel lingkungan yang diperlukan, lalu klik Deploy.

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

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