Claude Code के साथ एक डांस क्लास बुकिंग वेबसाइट बनाएँ

प्रोजेक्ट प्रकार चुनें

डांस क्लास बुकिंग वेबसाइट

डेंटल क्लिनिक बुकिंग वेबसाइट

हेयर सैलून बुकिंग वेबसाइट

बार्बरशॉप बुकिंग वेबसाइट

स्पा बुकिंग वेबसाइट

पर्सनल ट्रेनर बुकिंग वेबसाइट

कोचिंग बुकिंग वेबसाइट

रेस्टोरेंट रिज़र्वेशन वेबसाइट

ब्यूटी सैलून बुकिंग वेबसाइट

मसाज थेरेपी बुकिंग वेबसाइट

नेल सैलून बुकिंग वेबसाइट

फ़ोटोग्राफ़ी बुकिंग वेबसाइट

पेट ग्रूमिंग बुकिंग वेबसाइट

योग स्टूडियो बुकिंग वेबसाइट

टैटू स्टूडियो बुकिंग वेबसाइट

डांस क्लास बुकिंग वेबसाइट

फिटनेस क्लास बुकिंग वेबसाइट

थेरेपी और काउंसलिंग बुकिंग वेबसाइट

काइरोप्रैक्टर बुकिंग वेबसाइट

फ़िज़ियोथेरेपी बुकिंग वेबसाइट

कार डिटेलिंग बुकिंग वेबसाइट

ऑटो रिपेयर बुकिंग वेबसाइट

क्लीनिंग सर्विस बुकिंग वेबसाइट

घर मरम्मत बुकिंग वेबसाइट

लॉन केयर बुकिंग वेबसाइट

इवेंट प्लानर बुकिंग वेबसाइट

वेडिंग प्लानर बुकिंग वेबसाइट

मेकअप आर्टिस्ट बुकिंग वेबसाइट

एस्थेटिशियन बुकिंग वेबसाइट

प्राइवेट ट्यूटर बुकिंग वेबसाइट

ड्राइविंग स्कूल बुकिंग वेबसाइट

प्रॉपर्टी व्यूइंग बुकिंग वेबसाइट

रियल एस्टेट एजेंट बुकिंग वेबसाइट

बुकिंग फ़्लो प्रीव्यू

- सेवा चुनें

- दिनांक चुनें

- समय चुनें

- बुकिंग की पुष्टि करें

ग्राहक विवरण एकत्र किए गए

- पूरा नाम

- ईमेल

- फ़ोन

- वैकल्पिक नोट्स

एक Supabase प्रोजेक्ट बनाएँ

अपने बुकिंग सिस्टम बैकएंड के लिए एक नया Supabase प्रोजेक्ट बनाएँ।

Supabase खोलें

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

एडमिन उपयोगकर्ता बनाएँ

Supabase Authentication में एक एडमिन उपयोगकर्ता बनाएँ, फिर उपयोगकर्ता ID कॉपी करें।

पूर्ण सेटअप SQL चलाएँ

अपनी एडमिन उपयोगकर्ता ID पेस्ट करें, फिर Supabase SQL Editor में यह SQL कोड चलाएँ। यह सब कुछ एक बार में सेट अप करेगा: टेबल्स, सुरक्षा पॉलिसी और एडमिन एक्सेस।

पूर्ण सेटअप 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 'Rhythm House Dance 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 4, 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 ('Beginner Dance Class', 'A welcoming dance class designed for new students who want to learn basic movement, rhythm, and confidence.', 60, 30), ('Hip-Hop Dance Class', 'An energetic class focused on rhythm, musicality, coordination, and modern hip-hop movement.', 60, 35), ('Ballet Fundamentals', 'A structured class focused on posture, technique, balance, and foundational ballet movement.', 60, 35), ('Contemporary Dance', 'A creative dance class blending fluid movement, expression, musicality, and modern technique.', 75, 40), ('Private Dance Lesson', 'A personalized one-on-one dance session tailored to the student's goals, level, and preferred style.', 60, 85), ('Wedding Dance Lesson', 'A private dance lesson designed to help couples prepare a polished first dance with confidence.', 75, 120); insert into business_hours (weekday, is_open, start_time, end_time) values (0, false, null, null), (1, true, '10:00', '20:00'), (2, true, '10:00', '20:00'), (3, true, '10:00', '20:00'), (4, true, '10:00', '20:00'), (5, true, '10:00', '18: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 ('Rhythm House Dance Studio', 'hello@rhythmhousedance.com', '+1 555 901 3456', '928 Movement Avenue, New York, NY', 30, 4); 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');

एडमिन उपयोगकर्ता ID

अपनी Supabase auth उपयोगकर्ता ID दर्ज करें

कदम-दर-कदम SQL सेटअप (वैकल्पिक)

डेटाबेस टेबल्स बनाएँ

Supabase SQL Editor के अंदर ये SQL queries चलाएँ।

सेवाएँ टेबल

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 'Rhythm House Dance 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 4, created_at timestamp with time zone default now() );

स्टार्टर डेटा जोड़ें

ये स्टार्टर queries चलाएँ।

स्टार्टर सेवाएँ डालें

insert into services (name, description, duration_minutes, price) values ('Beginner Dance Class', 'A welcoming dance class designed for new students who want to learn basic movement, rhythm, and confidence.', 60, 30), ('Hip-Hop Dance Class', 'An energetic class focused on rhythm, musicality, coordination, and modern hip-hop movement.', 60, 35), ('Ballet Fundamentals', 'A structured class focused on posture, technique, balance, and foundational ballet movement.', 60, 35), ('Contemporary Dance', 'A creative dance class blending fluid movement, expression, musicality, and modern technique.', 75, 40), ('Private Dance Lesson', 'A personalized one-on-one dance session tailored to the student\'s goals, level, and preferred style.', 60, 85), ('Wedding Dance Lesson', 'A private dance lesson designed to help couples prepare a polished first dance with confidence.', 75, 120);

व्यवसाय घंटे डालें

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 business_settings (business_name, business_email, business_phone, business_address, slot_interval_minutes, booking_notice_hours) values ('Rhythm House Dance Studio', 'hello@rhythmhousedance.com', '+1 555 901 3456', '928 Movement Avenue, New York, NY', 30, 4);

एडमिन डैशबोर्ड को सुरक्षित करें

1. एडमिन एक्सेस टेबल बनाएँ एक टेबल बनाएँ जो परिभाषित करे कि कौन से प्रमाणित उपयोगकर्ता एडमिन डैशबोर्ड तक पहुँच और प्रबंधित करने की अनुमति रखते हैं।

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. Row Level Security सक्षम करें उन टेबल्स पर RLS सक्षम करें जिन्हें सामान्य उपयोगकर्ताओं से सुरक्षित रखा जाना चाहिए।

RLS सक्षम करें

alter table admin_users enable row level security; alter table services enable row level security; alter table appointments enable row level security; alter table business_hours enable row level security; alter table blocked_dates enable row level security; alter table business_settings enable row level security;

3. एडमिन पॉलिसी जोड़ें सार्वजनिक उपयोगकर्ताओं को केवल बुकिंग वेबसाइट के लिए ज़रूरी चीज़ें पढ़ने दें, और केवल एडमिन उपयोगकर्ताओं को सुरक्षित डेटा प्रबंधित करने दें।

एडमिन पॉलिसी

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. अपना एडमिन उपयोगकर्ता जोड़ें पहले ऐप लॉगिन स्क्रीन से अपना एडमिन खाता बनाएँ, फिर अपनी प्रमाणित उपयोगकर्ता ID को admin_users टेबल में डालें।

अपना एडमिन उपयोगकर्ता डालें

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

प्रोजेक्ट बनाने के लिए Prompt 1 का उपयोग करें

Prompt 1: पूर्ण डांस क्लास प्रोजेक्ट बनाएँ

वास्तविक बुकिंग के साथ एक प्रीमियम आधुनिक डेंटल क्लिनिक वेबसाइट बनाएँ…

You are a world-class full-stack product builder, creative director, and UI/UX designer. Build a premium modern dance class 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 performing arts 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 dance class 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 dance studio 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 dance_settings. - Do not use studio_settings. - Do not use class_settings. - Do not use academy_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 dance class booking website where visitors can: - view dance classes and private lessons - select a class or lesson - 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 dance studio owner, instructor, or studio 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 dance studio. The public website should feel: - premium - modern - energetic - artistic - elegant - expressive - polished - movement-focused - trustworthy - professional - student-friendly - realistic for a premium local dance studio The dashboard should feel: - premium - clean - modern - product-like - organized - smooth - easy for a dance 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 artistic, energetic, premium, and professional - Do not make it look like a dental clinic, beauty salon, massage studio, restaurant, gym, coaching website, or generic SaaS landing page ================================================ VISUAL DESIGN SYSTEM ================================================ Use a premium dance studio visual style: - clean white, warm off-white, soft beige, charcoal, deep navy, muted purple, blush, and warm neutral backgrounds - refined purple, coral, gold, deep navy, rose, graphite, and energetic accent colors - strong but elegant contrast - polished class cards - refined borders - soft shadows - layered visuals - subtle gradients - cinematic lighting effects - expressive depth - premium buttons - minimal movement-inspired icons - high-quality dance studio 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, expressive, premium, and trustworthy - use modern, elegant, readable typography - avoid overly decorative fonts - dashboard should stay clean, readable, and product-like Layout: - improve spacing and composition - use modern section layouts - use movement-focused visual storytelling - introduce tasteful asymmetry where appropriate - create image-led energetic 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 energetic but professional, not distracting ================================================ IMAGE AND VISUAL STORYTELLING REQUIREMENTS ================================================ The public website must use strong, high-quality, niche-specific dance studio 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, creative, trustworthy, and premium. Image style: - premium dance studio photography - clean modern dance studio environment - dancers practicing in a tasteful and professional setting - instructor leading a class - studio mirrors, wooden floors, and natural or dramatic lighting - expressive movement captured tastefully - group class atmosphere - private lesson environment - refined and realistic - good cropping - consistent visual style across the website Good image subjects: - modern dance studio interior - instructor leading a class - students practicing choreography - dance floor and mirror wall - ballet barre or contemporary studio setup - hip-hop class energy in a clean studio - private dance lesson atmosphere - wedding dance lesson setting shown tastefully - movement detail, shoes, studio floor, or warm-up scene - reception or waiting area for a dance studio Do not use: - dental imagery - medical clinic imagery - massage therapy imagery - beauty salon imagery - barbershop imagery - restaurant imagery - extreme gym imagery - bodybuilding imagery - overly revealing or inappropriate dance imagery - nightclub imagery - chaotic party imagery - low-resolution images - awkward stock photos - broken image links - random model portraits unrelated to dance classes 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 dance studio brand, improve trust, and make the section feel more premium. ================================================ BRAND DIRECTION ================================================ Use dance studio-specific language: - Dance Studio - Dance Class - Dance Lesson - Instructor - Student - Client - Appointment - Class - Session - Beginner Dance - Hip-Hop Dance - Ballet Fundamentals - Contemporary Dance - Private Dance Lesson - Wedding Dance Lesson - Movement - Rhythm - Choreography - Book your class - Schedule your lesson - Reserve your dance session Do not use: - dental - dentist - patient - oral health - massage therapy - therapist - beauty salon - stylist - medical - healthcare - barber - barbershop - restaurant - reservation - table - coaching - trainer - bodybuilding - aggressive workout language Avoid unrealistic claims. Do not promise guaranteed results. Do not use body-shaming or appearance-based messaging. Do not use overly sensual or inappropriate language. Focus on movement, rhythm, confidence, creativity, expression, learning, comfort, community, professional instruction, and a polished student 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 dance 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 dance studio-specific imagery throughout the public website. - The site should look like a real premium dance studio website, not a simple template. ================================================ PUBLIC WEBSITE QUALITY EXPECTATIONS ================================================ Navbar: - refined and premium - clean dance studio brand presence - elegant spacing - polished booking CTA Hero: - visually striking and premium - must include a strong, relevant dance studio visual - use imagery such as a modern dance studio interior, instructor leading a class, dancers practicing, studio floor, mirror wall, choreography moment, or expressive movement scene - use image overlays, gradients, lighting, or layered composition for depth - maintain strong text readability - strong headline hierarchy - energetic 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, expressive, clean, 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: - Beginner Dance Class: welcoming class setting with instructor - Hip-Hop Dance Class: energetic studio movement, not nightclub imagery - Ballet Fundamentals: ballet barre or clean studio technique scene - Contemporary Dance: expressive movement in a modern studio - Private Dance Lesson: one-on-one instruction atmosphere - Wedding Dance Lesson: tasteful couple lesson or elegant studio practice Keep service images consistent in crop, quality, and style. Do not use inappropriate, nightclub, medical, or unrelated fitness images. About: - creative, energetic, professional, and intentional - visually balanced - should reinforce trust, experience, rhythm, creativity, comfort, community, and professional instruction - include a strong dance studio-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 student/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 dance class or lesson 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 student-friendly and client-focused 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/student 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/classes - edit existing services/classes - activate services/classes - deactivate services/classes 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 dance studio-specific imagery - Hero section includes a strong relevant dance studio visual - Services section includes relevant niche-specific visual treatment or images - About section includes authentic dance studio 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 dance studio 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 dance class 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.

वैकल्पिक: तैयार प्रोजेक्ट से शुरू करें

डांस क्लास बुकिंग वेबसाइट

तैयार प्रोजेक्ट के साथ तेज़ी से शुरू करें

PROJECT

https://profitstudio.app/template/dance-class-booking-website

Supabase एनवायरनमेंट वेरिएबल्स जोड़ें

स्थानीय परीक्षण के लिए अपनी Supabase Project URL और Publishable Key को .env.local फ़ाइल में जोड़ें।

Git इंस्टॉल करें

प्रोजेक्ट को GitHub पर पुश करने से पहले सुनिश्चित करें कि आपके कंप्यूटर पर Git इंस्टॉल है।

Git डाउनलोड करें

https://git-scm.com/

VS Code को GitHub से कनेक्ट करें

VS Code के अंदर अपने GitHub अकाउंट में साइन इन करें।

एक GitHub रिपॉज़िटरी बनाएँ

एक नई प्राइवेट GitHub रिपॉज़िटरी बनाएँ और रिपॉज़िटरी URL कॉपी करें।

प्रोजेक्ट को GitHub पर पुश करें

VS Code में Claude Code खोलें, Safe GitHub Push Prompt पेस्ट करें और अपना GitHub रिपॉज़िटरी URL डालें। Claude प्रोजेक्ट तैयार करने के बाद, VS Code में Source Control खोलें, फिर कमिट करें और बदलावों को सिंक करें।

सुरक्षित GitHub Push Prompt

नीचे अपना GitHub रिपॉज़िटरी URL डालें, फिर 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 रिपॉज़िटरी URL

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

Hostinger पर Node.js वेब ऐप बनाएँ

Hostinger खोलें, एक नई Node.js वेब ऐप बनाएँ और अपना डोमेन चुनें।

Hostinger खोलें

इस प्रोजेक्ट को वीडियो में दिखाए गए उसी सेटअप के साथ पब्लिश करें।

RECOMMENDED

https://www.hostg.xyz/SHJe0

रिपॉज़िटरी इम्पोर्ट करें और डिप्लॉय करें

अपनी GitHub रिपॉज़िटरी इम्पोर्ट करें, आवश्यक एनवायरनमेंट वेरिएबल्स जोड़ें, फिर Deploy पर क्लिक करें।

VITE_SUPABASE_URL VITE_SUPABASE_ANON_KEY

VITE_SUPABASE_URL

प्रोजेक्ट URL

VITE_SUPABASE_ANON_KEY

anon (सार्वजनिक) की

ये मान Supabase से लें

API सेटिंग्स खोलें

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

स्वचालित रूप से अपॉइंटमेंट ईमेल भेजें

स्वचालित अपॉइंटमेंट ईमेल के साथ बुकिंग सिस्टम को अधिक पेशेवर बनाएँ।

- एडमिन को नई बुकिंग ईमेल भेजें

- रोगी को पुष्टिकरण ईमेल भेजें

डिप्लॉयमेंट के बाद वैकल्पिक अपग्रेड।

अपनी AI वेबसाइट को स्वचालित रूप से ईमेल भेजने दें (Supabase ट्यूटोरियल)

ट्यूटोरियल देखें

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

अपॉइंटमेंट SMS स्वचालित रूप से भेजें

हर बुकिंग के बाद स्वचालित SMS कन्फ़र्मेशन के साथ अपने बुकिंग सिस्टम को और पेशेवर बनाएँ।

- ग्राहक को SMS कन्फ़र्मेशन भेजें

- वैकल्पिक रूप से व्यवसाय के मालिक को SMS से सूचित करें

अपनी AI बुकिंग वेबसाइट में SMS नोटिफिकेशन जोड़ें

ट्यूटोरियल देखें

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