Baue eine Buchungs-Website mit Claude Code

Wähle den Projekttyp

Wähle einen Typ für eine Buchungs-Website aus

Buchungs-Website für eine Zahnklinik

Buchungs-Website für einen Friseursalon

Buchungs-Website für Barbershop

Buchungs-Website für ein Spa

Buchungs-Website für Personal Trainer

Buchungs-Website für Coaching

Reservierungs-Website für ein Restaurant

Buchungs-Website für Beautysalon

Buchungs-Website für Massagetherapie

Buchungs-Website für ein Nagelstudio

Buchungs-Website für einen Fotografen

Buchungs-Website für Tierpflege

Buchungs-Website für ein Yoga-Studio

Buchungs-Website für ein Tattoo-Studio

Buchungs-Website für Tanzkurse

Buchungs-Website für Fitnesskurse

Buchungs-Website für Therapie und Beratung

Buchungs-Website für Chiropraktiker

Buchungs-Website für Physiotherapie

Buchungs-Website für Car Detailing

Buchungs-Website für Autowerkstatt

Buchungs-Website für Reinigungsservice

Buchungs-Website für Hausreparaturen

Buchungs-Website für Gartenpflege

Buchungs-Website für einen Eventplaner

Buchungs-Website für einen Hochzeitsplaner

Buchungs-Website für einen Makeup-Artist

Buchungs-Website für eine Kosmetikerin

Buchungs-Website für einen Privatlehrer

Buchungs-Website für eine Fahrschule

Buchungs-Website für Immobilienbesichtigungen

Buchungs-Website für einen Immobilienmakler

Vorschau des Buchungs-Flows

- Service auswählen

- Datum auswählen

- Uhrzeit auswählen

- Buchung bestätigen

Kundendaten erfasst

- Vollständiger Name

- E-Mail

- Telefon

- Optionale Notizen

Ein Supabase-Projekt erstellen

Erstelle ein neues Supabase-Projekt für das Backend deines Buchungssystems.

Öffne Supabase

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

Den Admin-Nutzer erstellen

Erstelle einen Admin-Nutzer in Supabase Authentication und kopiere dann die User-ID.

Führe das vollständige Setup-SQL aus

Füge deine Admin-User-ID ein und führe dann diesen SQL-Code im Supabase SQL Editor aus. Er richtet alles auf einmal ein: Tabellen, Sicherheits-Policies und Admin-Zugriff.

Vollständiges Setup-SQL

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 clinic_settings ( id uuid primary key default gen_random_uuid(), clinic_name text not null default 'Bright Smile Dental Clinic', clinic_email text, clinic_phone text, clinic_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 ('Dental Checkup', 'General dental examination and consultation.', 30, 40), ('Teeth Cleaning', 'Professional cleaning session.', 45, 60), ('Teeth Whitening', 'Cosmetic whitening session.', 60, 120), ('Tooth Filling', 'Basic tooth filling procedure.', 60, 90); 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'); insert into clinic_settings (clinic_name, clinic_email, clinic_phone, clinic_address, slot_interval_minutes, booking_notice_hours) values ('Bright Smile Dental Clinic', 'hello@brightsmile.com', '+1 555 123 4567', '123 Main Street, 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 clinic_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 clinic settings" on clinic_settings for select to anon, authenticated using (true); create policy "Admins can manage clinic settings" on clinic_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');

Admin-User-ID

Gib deine Supabase-Auth-User-ID ein

Schritt-für-Schritt-SQL-Setup (optional)

Die Datenbanktabellen erstellen

Führe diese SQL-Queries im Supabase SQL Editor aus.

Services-Tabelle

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

Termintabelle

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

Tabelle der Geschäftszeiten

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

Tabelle der gesperrten Daten

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

Tabelle der Klinikeinstellungen

create table clinic_settings ( id uuid primary key default gen_random_uuid(), clinic_name text not null default 'Bright Smile Dental Clinic', clinic_email text, clinic_phone text, clinic_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() );

Die Startdaten hinzufügen

Führe diese Start-Queries aus.

Die Start-Services einfügen

insert into services (name, description, duration_minutes, price) values ('Dental Checkup', 'General dental examination and consultation.', 30, 40), ('Teeth Cleaning', 'Professional cleaning session.', 45, 60), ('Teeth Whitening', 'Cosmetic whitening session.', 60, 120), ('Tooth Filling', 'Basic tooth filling procedure.', 60, 90);

Die Geschäftszeiten einfügen

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

Die Klinikeinstellungen einfügen

insert into clinic_settings (clinic_name, clinic_email, clinic_phone, clinic_address, slot_interval_minutes, booking_notice_hours) values ('Bright Smile Dental Clinic', 'hello@brightsmile.com', '+1 555 123 4567', '123 Main Street, New York, NY', 30, 2);

Das Admin-Dashboard absichern

1. Erstelle die Admin-Zugriffstabelle Erstelle eine Tabelle, die definiert, welche authentifizierten Nutzer auf das Admin-Dashboard zugreifen und es verwalten dürfen.

admin_users-Tabelle

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. Row Level Security aktivieren Aktiviere RLS auf den Tabellen, die vor normalen Nutzern geschützt werden sollen.

RLS aktivieren

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

3. Füge die Admin-Policies hinzu Erlaube öffentlichen Nutzern nur das zu lesen, was für die Buchungs-Website nötig ist, und erlaube nur Admin-Nutzern, die geschützten Daten zu verwalten.

Admin-Policies

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 clinic settings" on clinic_settings for select to anon, authenticated using (true); create policy "Admins can manage clinic settings" on clinic_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. Füge deinen Admin-Nutzer hinzu Erstelle zuerst dein Admin-Konto über den App-Login-Bildschirm, dann füge deine authentifizierte User-ID in die admin_users-Tabelle ein.

Deinen Admin-Nutzer einfügen

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

Verwende Prompt 1, um das Projekt zu bauen

Prompt 1: Das vollständige Zahnklinik-Projekt bauen

Baue eine moderne Premium-Zahnklinik-Website mit echtem Buchungssystem…

Build a premium modern dental clinic website with a real booking system and a secure admin dashboard. Tech stack: - React - TypeScript - Vite - Supabase (database + backend + auth) ================================================ SUPABASE CONNECTION (REQUIRED) ================================================ 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 Important rules: - Use these values as environment variables - Do NOT hardcode them directly inside components - Create a Supabase client in: src/lib/supabase.ts - Use: import.meta.env.VITE_SUPABASE_URL import.meta.env.VITE_SUPABASE_ANON_KEY ================================================ DATABASE SCHEMA (STRICT CONTRACT) ================================================ Use this EXACT schema. Do NOT rename or invent fields. Table: services - id - name - description - duration_minutes - price - is_active - created_at Table: appointments - id - full_name - email - phone - service_id - appointment_date - start_time - end_time - status - notes - created_at Table: business_hours - id - weekday - is_open - start_time - end_time Table: blocked_dates - id - blocked_date - reason - created_at Table: clinic_settings - id - clinic_name - clinic_email - clinic_phone - clinic_address - slot_interval_minutes - booking_notice_hours - created_at ================================================ CRITICAL RULES (DO NOT BREAK) ================================================ Do NOT use: - day_of_week - open_time / close_time - date (for blocked_dates) - customer_name / customer_email / customer_phone Only use the exact schema above. ================================================ PROJECT GOAL ================================================ Create a real dental clinic website where users can: - select a service - select a date - select an available time - submit an appointment request And an admin can: - manage appointments - manage services - manage business hours - manage blocked dates - manage clinic settings ================================================ MAIN DESIGN GOAL ================================================ The website should feel like: - a premium dental clinic - a modern healthcare brand - trustworthy - clean - calm - refined - high-end but still medical and believable The dashboard should feel like: - a premium internal healthcare admin system - modern - structured - minimal - product-like - polished IMPORTANT: Do NOT make this look like: - a fashion website - a boutique luxury brand - an editorial magazine - a perfume or jewelry brand - a spa or lifestyle site Avoid: - overly dramatic serif-heavy design - overly artistic editorial layouts - styling that does not feel medical - generic AI landing page patterns - weak spacing and flat template-looking sections ================================================ PREMIUM VISUAL DIRECTION ================================================ Use a premium healthcare design system with: - soft off-white / warm neutral backgrounds - deep teal / muted medical green / refined blue-green accents - dark charcoal text - soft gray supporting tones - subtle premium shadows - refined borders - spacious layouts - elegant but restrained typography - polished card design - strong visual hierarchy Typography: - use a clean modern sans-serif as the main font across the project - you may use a subtle refined serif only in very limited hero or section headings if it still feels premium medical, not editorial - dashboard should use sans-serif only - prioritize readability, clarity, and trust ================================================ PUBLIC WEBSITE ================================================ Create: - Homepage - Services section - About section - Booking flow - Success confirmation screen - Footer The public site should feel like a real premium clinic website, not a generic template. ================================================ PUBLIC WEBSITE — SECTION EXPECTATIONS ================================================ 1. NAVBAR - clean premium layout - strong brand presence - simple refined navigation - premium CTA button 2. HERO - strong premium first impression - high-quality layout balance between text and image - trustworthy dental clinic feeling - elegant but clear hierarchy - modern medical brand tone - no exaggerated artistic styling 3. SERVICES SECTION This section must be visually stronger than simple text-only cards. Requirements: - each service card should include a meaningful visual element - use a clean image area, premium medical visual treatment, or service-related imagery - keep visuals consistent, elegant, and medically appropriate - do not use random messy stock photos - make service cards feel premium, informative, and visually engaging Service cards should clearly present: - service name - short description - duration - price - CTA / booking affordance 4. ABOUT SECTION - should feel intentional and trustworthy - use better image composition - avoid awkward empty layouts - reinforce clinic credibility, calmness, and quality 5. BOOKING SECTION / FLOW The booking experience is a very important part of this project and should feel premium from the start. It should feel: - organized - polished - easy to understand - trustworthy - calm - productized 6. FOOTER - clean layout - strong hierarchy - premium final impression - consistent with the rest of the brand ================================================ BOOKING FLOW (IMPORTANT) ================================================ Step 1: - Select a service Step 2: - Select date - Show available times (based on real logic) Step 3: - Enter: - full name - email - phone - optional notes Step 4: - Success screen with summary ================================================ BOOKING UX REQUIREMENTS ================================================ From the first version, make the booking UI feel polished and premium. Improve: - step indicator - date selection layout - time slot layout - selected states - CTA hierarchy - details form grouping - appointment summary block - success state The booking flow should feel like a real premium reservation product, not just a simple form inside a page. ================================================ AVAILABILITY LOGIC (VERY IMPORTANT) ================================================ Available slots must be generated using: - business_hours - services.duration_minutes - clinic_settings.slot_interval_minutes - clinic_settings.booking_notice_hours - blocked_dates - existing appointments Rules: - Only generate slots inside working hours - Skip blocked dates - Skip overlapping appointments - Ignore cancelled appointments - Respect booking notice time Overlap rule: new_start < existing_end AND new_end > existing_start Slot structure (IMPORTANT): All available slots must be normalized as: { start: Date, end: Date, label: string } ================================================ TIME SAFETY RULES (PREVENT CRASHES) ================================================ - Only format REAL Date objects - NEVER pass invalid strings to format() - NEVER use strings like "yyyy-MM-ddT10:30:00" - Always combine real selected date + time correctly ================================================ ADMIN AUTH + DASHBOARD SECURITY ================================================ Build a real admin authentication flow using Supabase Auth. Requirements: - create a dedicated admin login screen - protect all admin dashboard routes - unauthenticated users must never access admin pages - non-admin users must never access admin features - redirect unauthenticated users to the admin login page - keep the public website fully accessible without login Admin access rules: - only authenticated admin users can access the dashboard - admin users should have full control over: - appointments - services - business hours - blocked dates - clinic settings Security expectations: - use Supabase Auth for sign in - connect the dashboard to the authenticated admin session - do not rely on hiding buttons only - implement real route protection for admin pages - structure the code so admin access is clear and maintainable ================================================ ADMIN DASHBOARD ================================================ Create a full premium dashboard with: 1. Overview 2. Appointments (list + filter + status update) 3. Services (CRUD) 4. Business Hours editor 5. Blocked Dates manager 6. Clinic Settings form Dashboard design requirements: - modern healthcare admin aesthetic - clean sans-serif typography - structured layout - readable tables - refined filters and controls - polished status badges - no generic admin template feeling Important: - New services must appear in booking page automatically ================================================ OUTPUT ================================================ - Full working app - Clean structure - Supabase fully connected - Booking flow working - Admin login working - Protected dashboard working - Dashboard working - No placeholder fake data - Production-style code - Premium dental / medical visual direction from the start

Supabase-Umgebungsvariablen hinzufügen

Füge die Supabase Project URL und den Publishable Key in eine .env.local-Datei für lokale Tests ein.

Das Projekt verbessern oder korrigieren (optional)

Zusätzliche Prompts für Korrekturen und Verbesserungen

Prompt 2: Die Buchungslogik verfeinern

Implementiere die öffentliche Buchungslogik sehr sorgfältig und verwende dabei exakt das bestehende Supabase-Schema…

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: Das Admin-Dashboard bauen

Baue das Admin-Dashboard exakt mit dem bestehenden Supabase-Schema…

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: QA und Stabilisierung durchführen

Führe einen vollständigen Konsistenz-, QA-, Stabilisierungs- und sicherheitsbewussten Validierungsdurchlauf über das gesamte Projekt durch…

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

Git installieren

Stelle sicher, dass Git auf deinem Computer installiert ist, bevor du das Projekt auf GitHub pushst.

Git herunterladen

https://git-scm.com/

VS Code mit GitHub verbinden

Melde dich in VS Code mit deinem GitHub-Konto an.

Ein GitHub-Repository erstellen

Erstelle ein neues privates GitHub-Repository und kopiere die Repository-URL.

Das Projekt auf GitHub pushen

Öffne Claude Code in VS Code, füge den Sicheren GitHub-Push-Prompt ein und füge deine GitHub-Repository-URL hinzu. Nachdem Claude das Projekt vorbereitet hat, öffne Source Control in VS Code und committe und synchronisiere die Änderungen.

Sicherer GitHub-Push-Prompt

Füge deine GitHub-Repository-URL unten ein und nutze dann den angepassten Prompt in 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.

GitHub-Repository-URL

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

Eine Node.js-Web-App auf Hostinger erstellen

Öffne Hostinger, erstelle eine neue Node.js-Web-App und wähle deine Domain.

Öffne Hostinger

Veröffentliche dieses Projekt mit demselben Setup wie im Video.

RECOMMENDED

https://www.hostg.xyz/SHJe0

Repository importieren und deployen

Importiere dein GitHub-Repository, füge die erforderlichen Umgebungsvariablen hinzu und klicke auf Deployen.

VITE_SUPABASE_URL VITE_SUPABASE_ANON_KEY

VITE_SUPABASE_URL

Projekt-URL

VITE_SUPABASE_ANON_KEY

Anon-Schlüssel (öffentlich)

Diese Werte findest du in Supabase

API-Einstellungen öffnen

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

Sende Termin-E-Mails automatisch

Mache das Buchungssystem mit automatischen Termin-E-Mails professioneller.

- Sende eine E-Mail über eine neue Buchung an den Geschäftsinhaber

- Sende eine Bestätigungs-E-Mail an den Kunden

Lass deine KI-Website automatisch E-Mails senden (Supabase-Tutorial)

Tutorial ansehen

https://youtu.be/KLnBJDJM_p8

Sende Termin-SMS automatisch

Mache dein Buchungssystem professioneller mit automatischen SMS-Bestätigungen nach jeder Buchung.

- Sende eine SMS-Bestätigung an den Kunden

- Benachrichtige optional auch den Inhaber per SMS

Füge SMS-Benachrichtigungen zu deiner KI-Buchungs-Website hinzu

Tutorial ansehen

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