Baue eine Buchungs-Website für einen Makeup-Artist mit Claude Code

Wähle den Projekttyp

Buchungs-Website für einen Makeup-Artist

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 business_settings ( id uuid primary key default gen_random_uuid(), business_name text not null default 'Velvet Glow Makeup 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 12, 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 ('Soft Glam Makeup', 'A polished soft glam makeup session designed for events, photos, dinners, and special occasions.', 75, 120), ('Full Glam Makeup', 'A full glam makeup appointment with a refined, camera-ready finish for important events and celebrations.', 90, 160), ('Bridal Makeup Trial', 'A personalized bridal makeup trial to test style direction, tones, finish, and the final wedding-day look.', 120, 220), ('Bridal Makeup Session', 'A premium bridal makeup appointment designed for a polished, elegant, and long-lasting wedding-day look.', 120, 300), ('Photoshoot Makeup', 'A professional makeup session designed for photoshoots, branding, portraits, and camera-ready results.', 90, 180), ('Makeup Consultation', 'A consultation to discuss your event, preferences, skin preparation, style direction, and booking details.', 45, 60); insert into business_hours (weekday, is_open, start_time, end_time) values (0, false, null, null), (1, true, '10:00', '18:00'), (2, true, '10:00', '18:00'), (3, true, '10:00', '18:00'), (4, true, '10:00', '19:00'), (5, true, '10:00', '19:00'), (6, true, '09:00', '15:00'); insert into business_settings (business_name, business_email, business_phone, business_address, slot_interval_minutes, booking_notice_hours) values ('Velvet Glow Makeup Studio', 'hello@velvetglowmakeup.com', '+1 555 123 4568', '512 Beauty Avenue, New York, NY', 30, 12); 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');

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

Einstellungstabelle

create table business_settings ( id uuid primary key default gen_random_uuid(), business_name text not null default 'Velvet Glow Makeup 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 12, 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 ('Soft Glam Makeup', 'A polished soft glam makeup session designed for events, photos, dinners, and special occasions.', 75, 120), ('Full Glam Makeup', 'A full glam makeup appointment with a refined, camera-ready finish for important events and celebrations.', 90, 160), ('Bridal Makeup Trial', 'A personalized bridal makeup trial to test style direction, tones, finish, and the final wedding-day look.', 120, 220), ('Bridal Makeup Session', 'A premium bridal makeup appointment designed for a polished, elegant, and long-lasting wedding-day look.', 120, 300), ('Photoshoot Makeup', 'A professional makeup session designed for photoshoots, branding, portraits, and camera-ready results.', 90, 180), ('Makeup Consultation', 'A consultation to discuss your event, preferences, skin preparation, style direction, and booking details.', 45, 60);

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

Einstellungen einfügen

insert into business_settings (business_name, business_email, business_phone, business_address, slot_interval_minutes, booking_notice_hours) values ('Velvet Glow Makeup Studio', 'hello@velvetglowmakeup.com', '+1 555 123 4568', '512 Beauty Avenue, New York, NY', 30, 12);

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 business_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 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. 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 Makeup-Artist-Projekt bauen

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

You are a world-class full-stack product builder, creative director, and UI/UX designer. Build a premium modern makeup artist 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 beauty, fashion, and lifestyle design agency and built as a real production-ready product. Do not create a generic template. Do not create a basic admin panel. Do not make small visual improvements. Create a complete, polished, premium makeup artist 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 makeup artist 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 makeup_settings. - Do not use makeup_artist_settings. - Do not use beauty_settings. - Do not use artist_settings. - Do not use studio_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 makeup artist booking website where visitors can: - view makeup 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 makeup artist, studio owner, or beauty 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 makeup artist brand. The public website should feel: - premium - modern - elegant - polished - stylish - refined - beauty-focused - creative - trustworthy - professional - client-friendly - realistic for a premium local makeup artist or beauty studio The dashboard should feel: - premium - clean - modern - product-like - organized - smooth - easy for a makeup artist or beauty 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 beauty-focused, elegant, premium, creative, and professional - Do not make it look like a dental clinic, massage studio, restaurant, gym, auto repair shop, cleaning company, coaching website, or generic SaaS landing page ================================================ VISUAL DESIGN SYSTEM ================================================ Use a premium makeup artist visual style: - clean white, warm off-white, ivory, blush, nude, champagne, soft beige, pearl, rose, and elegant neutral backgrounds - refined rose gold, muted pink, mauve, soft plum, warm brown, champagne, graphite, and tasteful beauty accents - elegant high-end contrast - polished service cards - refined borders - soft shadows - layered visuals - subtle gradients - soft studio lighting effects - editorial depth - premium buttons - minimal beauty and makeup icons - high-quality makeup artist 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 beauty-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 makeup artist 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 makeup artist photography - clean modern beauty studio environment - soft natural or studio lighting - makeup artist working tastefully with a client - refined makeup tools, brushes, palettes, products, and vanity details - bridal makeup preparation shown professionally - photoshoot makeup atmosphere - elegant consultation or beauty desk setup - polished and realistic - good cropping - consistent visual style across the website Good image subjects: - makeup artist applying makeup professionally - elegant makeup studio or vanity - makeup brushes and palettes arranged neatly - bridal makeup preparation - soft glam makeup setting - photoshoot makeup preparation - beauty consultation desk - luxury product flat lay - client getting ready in a tasteful setting - clean beauty workspace with soft lighting Do not use: - dental imagery - medical clinic imagery - massage therapy imagery - barbershop imagery - restaurant imagery - fitness imagery - automotive imagery - graphic skin procedure imagery - uncomfortable closeups - overly edited or unrealistic beauty images - insecurity-focused images - low-resolution images - awkward stock photos - broken image links - random model portraits unrelated to makeup services 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 makeup artist brand, improve trust, and make the section feel more premium. ================================================ BRAND DIRECTION ================================================ Use makeup artist-specific language: - Makeup Artist - Makeup Studio - Beauty Studio - Makeup Services - Soft Glam Makeup - Full Glam Makeup - Bridal Makeup - Bridal Makeup Trial - Photoshoot Makeup - Makeup Consultation - Client - Appointment - Session - Beauty Look - Event Makeup - Camera-Ready Makeup - Book your appointment - Schedule your makeup session - Reserve your beauty appointment Do not use: - dental - dentist - patient - oral health - massage therapy - therapist - medical - healthcare - barber - barbershop - restaurant - reservation - table - fitness - workout - auto repair - vehicle service - cleaning service - coaching Avoid unrealistic beauty claims. Do not promise guaranteed results. Do not use manipulative or insecurity-based messaging. Do not use appearance-shaming language. Do not make claims about changing someone's worth, value, or body image. Focus on confidence, creativity, care, elegance, preparation, professional service, polished details, and a premium 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 makeup 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 makeup artist-specific imagery throughout the public website. - The site should look like a real premium makeup artist website, not a simple template. ================================================ PUBLIC WEBSITE QUALITY EXPECTATIONS ================================================ Navbar: - refined and premium - clean makeup artist brand presence - elegant spacing - polished booking CTA Hero: - visually striking and premium - must include a strong, relevant makeup artist visual - use imagery such as a makeup artist working with a client, elegant vanity, makeup brushes and palettes, bridal makeup preparation, photoshoot makeup setup, or premium beauty studio atmosphere - 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, stylish, 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: - Soft Glam Makeup: soft studio lighting, makeup brushes, or elegant beauty look preparation - Full Glam Makeup: polished makeup setup, vanity, or camera-ready beauty preparation - Bridal Makeup Trial: bridal preparation details, consultation, or refined makeup station - Bridal Makeup Session: elegant bridal makeup preparation, not overly intimate - Photoshoot Makeup: professional makeup preparation for camera or studio setting - Makeup Consultation: beauty consultation desk, palette selection, or planning notes Keep service images consistent in crop, quality, and style. Do not use medical, dental, uncomfortable procedure, or insecurity-focused images. About: - elegant, creative, professional, and intentional - visually balanced - should reinforce trust, experience, artistry, preparation, cleanliness, attention to detail, and professional beauty service - include a strong makeup artist-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 makeup 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 beauty-service 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 makeup artist-specific imagery - Hero section includes a strong relevant makeup artist visual - Services section includes relevant niche-specific visual treatment or images - About section includes authentic makeup artist 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 makeup artist 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 makeup artist 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.

Optional: Mit einem fertigen Projekt starten

Buchungs-Website für einen Makeup-Artist

Starte schneller mit dem fertigen Projekt

PROJECT

https://profitstudio.app/template/makeup-artist-booking-website

Supabase-Umgebungsvariablen hinzufügen

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

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 Admin

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

Optionales Upgrade nach dem Deployment.

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

Tutorial ansehen

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

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