Bangun Situs Reservasi Restoran dengan Claude Code

Pilih tipe proyek

Situs Reservasi Restoran

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

User ID Admin

Masukkan user ID auth Supabase Anda

Setup SQL Langkah demi Langkah (Opsional)

Buat Tabel Database

Jalankan query SQL ini di dalam Supabase SQL Editor.

Meja Restoran

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

Item Menu

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

Reservasi

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

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

Pengaturan Restoran

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

Tambahkan Data Awal

Jalankan query awal ini.

Masukkan Meja Restoran

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

Masukkan Item Menu

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

Masukkan Jam Bisnis

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

Masukkan Pengaturan Restoran

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

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 restaurant_tables enable row level security; alter table menu_items enable row level security; alter table reservations enable row level security; alter table business_hours enable row level security; alter table blocked_dates enable row level security; alter table restaurant_settings enable row level security;

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

4. 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 Restoran Lengkap

Bangun situs reservasi restoran modern premium dengan sistem booking meja nyata dan dashboard admin yang aman.

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

Opsional: Mulai dari proyek siap pakai

Situs Reservasi Restoran

Mulai lebih cepat dengan proyek siap pakai

PROJECT

https://profitstudio.app/template/restaurant-reservation-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