Construye un sitio de reservas para coaching con IA

Elige el tipo de proyecto

Sitio de reservas de coaching

Sitio de reservas de clínica dental

Sitio de reservas de peluquería

Sitio de reservas de barbería

Sitio de reservas de spa

Sitio de reservas de entrenador personal

Sitio de reservas de coaching

Sitio de reservas de restaurante

Sitio de reservas de salón de belleza

Sitio de reservas de masajes terapéuticos

Sitio de reservas de salón de uñas

Sitio de reservas de fotógrafo

Sitio de reservas de peluquería canina

Sitio de reservas de estudio de yoga

Sitio de reservas de estudio de tatuajes

Sitio de reservas de clases de baile

Sitio de reservas de clases de fitness

Sitio de reservas de terapia y orientación

Sitio de reservas de quiropráctico

Sitio de reservas de fisioterapeuta

Sitio de reservas de detallado de coches

Sitio de reservas de taller mecánico

Sitio de reservas de servicio de limpieza

Sitio de reservas de reparaciones del hogar

Sitio de reservas de cuidado de jardín

Sitio de reservas de organizador de eventos

Sitio de reservas de wedding planner

Sitio de reservas de maquilladora

Sitio de reservas de esteticista

Sitio de reservas de tutor privado

Sitio de reservas de autoescuela

Sitio de reservas de visitas inmobiliarias

Sitio de reservas de agente inmobiliario

Vista previa del flujo de reserva

- Seleccionar servicio

- Seleccionar fecha

- Seleccionar hora

- Confirmar reserva

Detalles del cliente recopilados

- Nombre completo

- Email

- Teléfono

- Notas opcionales

Crear un proyecto en Supabase

Crea un nuevo proyecto de Supabase para el backend de tu sistema de reservas.

Crear el usuario administrador

Crea un usuario administrador en Supabase Authentication y luego copia el user ID.

Ejecutar el SQL de configuración completa

Pega tu user ID de administrador y luego ejecuta este código SQL en el SQL Editor de Supabase. Configurará todo de una vez: tablas, políticas de seguridad y acceso de administrador.

SQL de configuración completa

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 coaching_settings ( id uuid primary key default gen_random_uuid(), coaching_name text not null default 'Clarity Coaching Studio', coaching_email text, coaching_phone text, coaching_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 ('Discovery Call', 'A short introductory session to understand goals, challenges, and next steps.', 30, 0), ('1:1 Coaching Session', 'A focused private coaching session designed to help clients gain clarity and direction.', 60, 120), ('Strategy Session', 'A practical session focused on planning, priorities, decision-making, and action steps.', 75, 180), ('Career Coaching', 'A personalized coaching session for career direction, confidence, interviews, and transitions.', 60, 140), ('Business Consultation', 'A focused consultation for entrepreneurs and professionals who need strategic guidance.', 60, 160), ('Follow-up Session', 'A shorter follow-up session to review progress, refine actions, and stay accountable.', 45, 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', '15:00'), (6, false, null, null); insert into coaching_settings (coaching_name, coaching_email, coaching_phone, coaching_address, slot_interval_minutes, booking_notice_hours) values ('Clarity Coaching Studio', 'hello@claritycoaching.com', '+1 555 678 7890', '210 Madison Avenue, 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 coaching_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 coaching settings" on coaching_settings for select to anon, authenticated using (true); create policy "Admins can manage coaching settings" on coaching_settings for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Users can read their own admin row" on admin_users for select to authenticated using (auth.uid() = user_id); insert into admin_users (user_id) values ('PASTE_YOUR_AUTH_USER_ID_HERE');

User ID del administrador

Introduce tu user ID de Supabase Auth

Configuración SQL paso a paso (opcional)

Crear las tablas de la base de datos

Ejecuta estas consultas SQL dentro del SQL Editor de Supabase.

Tabla de servicios

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

Tabla de citas

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

Tabla de horarios del negocio

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

Tabla de fechas bloqueadas

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

Tabla de ajustes

create table coaching_settings ( id uuid primary key default gen_random_uuid(), coaching_name text not null default 'Clarity Coaching Studio', coaching_email text, coaching_phone text, coaching_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() );

Añadir los datos iniciales

Ejecuta estas consultas iniciales.

Insertar los servicios iniciales

insert into services (name, description, duration_minutes, price) values ('Discovery Call', 'A short introductory session to understand goals, challenges, and next steps.', 30, 0), ('1:1 Coaching Session', 'A focused private coaching session designed to help clients gain clarity and direction.', 60, 120), ('Strategy Session', 'A practical session focused on planning, priorities, decision-making, and action steps.', 75, 180), ('Career Coaching', 'A personalized coaching session for career direction, confidence, interviews, and transitions.', 60, 140), ('Business Consultation', 'A focused consultation for entrepreneurs and professionals who need strategic guidance.', 60, 160), ('Follow-up Session', 'A shorter follow-up session to review progress, refine actions, and stay accountable.', 45, 90);

Insertar los horarios del negocio

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

Inserta los ajustes

insert into coaching_settings (coaching_name, coaching_email, coaching_phone, coaching_address, slot_interval_minutes, booking_notice_hours) values ('Clarity Coaching Studio', 'hello@claritycoaching.com', '+1 555 678 7890', '210 Madison Avenue, New York, NY', 30, 2);

Asegurar el panel de administración

1. Crear la tabla de acceso de administradores Crea una tabla que defina qué usuarios autenticados pueden acceder y gestionar el panel de administración.

Tabla 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. Habilitar Row Level Security Activa RLS en las tablas que deben protegerse de los usuarios normales.

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

3. Añadir las políticas de administrador Permite a los usuarios públicos leer solo lo necesario para el sitio de reservas, y permite solo a los usuarios administradores gestionar los datos protegidos.

Políticas de administrador

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 coaching settings" on coaching_settings for select to anon, authenticated using (true); create policy "Admins can manage coaching settings" on coaching_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. Añadir tu usuario administrador Primero crea tu cuenta de administrador desde la pantalla de login de la app, luego inserta tu user ID autenticado en la tabla admin_users.

Insertar tu usuario administrador

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

Usa el Prompt 1 para construir el proyecto

Prompt 1: Construir el proyecto completo de coaching

Construye un sitio web de coaching y consultoría moderno y premium con un sistema real de reservas y un panel de administración seguro.

You are a world-class full-stack product builder, creative director, and UI/UX designer. Build a premium modern coaching and consultation website with a real booking system and a secure admin dashboard. The final result should feel like it was designed by a top-tier design agency and built as a real production-ready product. Do not create a generic template. Do not create a basic admin panel. Do not make small visual improvements. Create a complete, polished, premium experience from the first version. Tech stack: - React - TypeScript - Vite - Supabase for database, backend, and auth ================================================ SUPABASE CONNECTION ================================================ Use these Supabase credentials: VITE_SUPABASE_URL=PASTE_YOUR_SUPABASE_URL_HERE VITE_SUPABASE_ANON_KEY=PASTE_YOUR_PUBLISHABLE_KEY_HERE Rules: - Use these values as environment variables - Do not hardcode them inside components - Create the Supabase client in src/lib/supabase.ts - Use import.meta.env.VITE_SUPABASE_URL and import.meta.env.VITE_SUPABASE_ANON_KEY ================================================ DATABASE SCHEMA ================================================ Use this exact schema. Do not rename fields or invent new ones. 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 coaching_settings: - id - coaching_name - coaching_email - coaching_phone - coaching_address - slot_interval_minutes - booking_notice_hours - created_at admin_users: - id - user_id - created_at Important: - Use coaching_settings, not trainer_settings - Use coaching_settings, not spa_settings - Use coaching_settings, not salon_settings - Use coaching_settings, not barbershop_settings - Use coaching_settings, not clinic_settings - Use coaching_name, coaching_email, coaching_phone, and coaching_address - Use admin_users.user_id to check admin access - Do not check admin access by email - Do not use fake local authentication - Do not use fake local data ================================================ PROJECT GOAL ================================================ Create a complete coaching booking website where visitors can: - view coaching and consultation services - select a service - select a date - see available time slots - enter their details - submit a real booking request - see a success confirmation Create a secure admin dashboard where the coach or consultant can manage: - appointments - services - business hours - blocked dates - coaching settings Everything in the dashboard should be useful and editable, not just displayed. ================================================ CREATIVE DIRECTION ================================================ This project must look premium from the first version. Think like a world-class creative director. The public website should feel: - high-end - modern - calm - confident - smart - trustworthy - refined - clear - polished - realistic for a premium coach, consultant, or advisor The dashboard should feel: - premium - clean - modern - product-like - organized - smooth - easy for a coach or consultant to use - visually polished, not basic Design quality expectations: - Avoid generic or template-like design - Avoid flat and empty layouts - Avoid boring sections - Avoid weak spacing - Avoid basic AI-generated landing page patterns - Do not make the public website look like a simple template - Do not make the admin dashboard look like a basic starter dashboard ================================================ VISUAL DESIGN SYSTEM ================================================ Use a premium coaching and consultation visual style: - warm off-white and soft neutral backgrounds - deep navy, charcoal, muted indigo, slate, champagne, or soft gold accents - clean white contrast sections - refined professional color palette - premium cards - soft shadows - refined borders - layered visuals - subtle gradients - calm lighting effects - strong but approachable hierarchy - elegant CTA buttons - polished consultation and coaching visual elements Use depth, gradients, lighting, and layered visuals where appropriate. Avoid flat backgrounds. Create strong contrast and clear hierarchy. Make the interface feel intentionally designed, not assembled from default components. Typography: - improve hierarchy and readability - make headings expressive, premium, and clear - use elegant, modern, readable typography - public website can use a refined display style for headings - dashboard should stay clean, readable, and product-like Layout: - improve spacing and composition - use dynamic, modern layouts - introduce tasteful asymmetry where appropriate - avoid overly rigid or boring sections - every section should feel intentionally designed Interactions: - add smooth animations and micro-interactions - enhance hover effects and transitions - make the experience feel polished and alive - keep interactions elegant, not distracting ================================================ IMAGE AND VISUAL STORYTELLING REQUIREMENTS ================================================ The public website must use strong, high-quality, niche-specific coaching and consultation 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, trustworthy, and premium. Image style: - premium coaching and consultation photography - modern office, studio, or calm professional environment - client conversation - coach taking notes - strategic planning - laptop, notebook, tablet, or workspace details - warm natural lighting - professional but approachable mood - clean composition - refined and modern - realistic and trustworthy - good cropping - consistent visual style across the website Good image subjects: - coach speaking with a client - one-on-one consultation - business coaching session - career coaching session - strategy planning with notebook or tablet - calm professional workspace - client discussion - remote coaching setup - laptop and planning materials - premium office or consultation environment Do not use: - fitness trainer imagery - spa imagery - barbershop imagery - hair salon imagery - dental or medical imagery - random model portraits unrelated to coaching - low-resolution images - awkward stock photos - broken image links - overly corporate generic handshake imagery - unrealistic luxury business clichés 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 coaching brand, improve trust, and make the section feel more premium. ================================================ BRAND DIRECTION ================================================ Use coaching and consultation language: - Coaching - Coach - Consultant - Client - Appointment - Session - Discovery Call - Strategy Session - Career Coaching - Business Consultation - Clarity - Goals - Direction - Action Plan - Book your session - Reserve your consultation Do not use: - trainer - workout - gym - fitness - spa - massage - facial - barbershop - barber - haircut - salon - stylist - clinic - patient - dental - dentist - doctor - medical - healthcare - teeth Avoid unrealistic promises. Do not claim guaranteed success, guaranteed income, guaranteed career results, or guaranteed transformation. Focus on clarity, strategy, decision-making, confidence, planning, and guided support. The website should feel like a premium coaching and consultation brand, not: - a personal trainer website - a spa website - a barbershop website - a hair salon website - a medical website - a generic SaaS landing page - a random business blog ================================================ 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 coaching_settings for coaching name, email, phone, and address when available - Make the booking section polished and easy to follow - Use strong coaching and consultation-specific imagery throughout the public website - The site should look like a real premium coaching website, not a simple template ================================================ PUBLIC WEBSITE QUALITY EXPECTATIONS ================================================ Navbar: - refined and premium - strong brand presence - elegant spacing - polished booking CTA Hero: - visually striking and premium - must include a strong, relevant coaching or consultation visual - use imagery such as coach speaking with a client, strategy planning, calm workspace, or professional consultation setting - use image overlays, gradients, lighting, or layered composition for depth - maintain strong text readability - strong headline hierarchy - clear and confident supporting text - polished CTA buttons - not generic - not flat - not basic Services: - should not look like a plain list - make services feel premium, clear, 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: - Discovery Call: friendly first consultation or video call setup - 1:1 Coaching Session: coach speaking with a client - Strategy Session: planning, notes, tablet, or workspace detail - Career Coaching: professional conversation or career planning - Business Consultation: business discussion or strategy workspace - Follow-up Session: notebook, progress review, or calm consultation visual Keep service images consistent in crop, quality, and style. Do not use random unrelated business images. About: - confident, warm, and intentional - visually balanced - should reinforce trust, clarity, experience, direction, and personal support - include a strong coaching-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 form design - 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 coaching settings where relevant ================================================ BOOKING FLOW ================================================ Step 1: Select a coaching 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 booking summary Booking UI should include: - clear step indicator - nice selected states - clean date selection - polished time slots - appointment summary - strong CTA buttons ================================================ AVAILABILITY LOGIC ================================================ Available time slots must be generated using: - business_hours - services.duration_minutes - coaching_settings.slot_interval_minutes - coaching_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 ================================================ ADMIN AUTH ================================================ Create a real admin login using Supabase Auth. Admin login flow: 1. Admin enters email and password 2. Sign in with supabase.auth.signInWithPassword() 3. Get the authenticated user 4. Check if user.id exists in admin_users.user_id 5. If yes, allow access to dashboard 6. If no, show: "You are signed in, but you are not authorized as an admin." 7. Add a loading state while checking session and admin access 8. Do not redirect back to login before the admin check finishes Rules: - Protect all admin routes - Public website should stay accessible without login - Do not check admin access by email - Do not use fake local authentication - Do not rely only on hiding buttons ================================================ ADMIN DASHBOARD ================================================ Create a complete dashboard with these pages: 1. Overview 2. Appointments 3. Services 4. Business Hours 5. Blocked Dates 6. Coaching 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. Coaching Settings: Allow editing: - coaching_name - coaching_email - coaching_phone - coaching_address - slot_interval_minutes - booking_notice_hours Updated coaching settings should appear on the public website where relevant. ================================================ QUALITY REQUIREMENTS ================================================ - Full working app - Clean code structure - Supabase fully connected - Booking flow working - Admin login working - Protected dashboard working - Services management fully working - Appointments management working - Business hours editing working - Blocked dates working - Coaching settings editing working - Public website uses high-quality coaching and consultation-specific imagery - Hero section includes a strong relevant coaching visual - Services section includes relevant niche-specific visual treatment or images - About section includes authentic coaching or consultation 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 coaching visual direction from the start - Public website should feel top-tier, not template-like - Dashboard should feel like a polished premium product - Keep functionality and visual quality strong from the first version FINAL RESULT: Create a complete, working, premium coaching booking platform with a high-end public website, strong niche-specific imagery, and a polished admin dashboard.

Añadir variables de entorno de Supabase

Añade tu Supabase Project URL y Publishable Key cuando Google AI Studio te pida variables de entorno.

Mejorar o corregir el proyecto (opcional)

Prompts extra para correcciones y mejoras

Prompt 2: Refinar la lógica de reservas

Implementa la lógica pública de reservas con mucho cuidado, usando exactamente el esquema existente de Supabase…

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: Construir el panel de administración

Construye el panel de administración usando exactamente el esquema existente de Supabase…

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 coaching_settings: - coaching_name - coaching_email - coaching_phone - coaching_address - 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. Coaching 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. COACHING SETTINGS ================================================ Allow editing: - coaching_name - coaching_email - coaching_phone - coaching_address - 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: Ejecutar QA y estabilización

Haz una pasada completa de consistencia, QA, estabilización y validación con conciencia de seguridad en todo el proyecto…

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

Guarda el proyecto en GitHub

Desplegar en Hostinger

Abrir Hostinger

Publica este proyecto con la misma configuración que se muestra en el vídeo.

RECOMMENDED

https://www.hostg.xyz/SHJK3

Crea una Node.js web app

Importa tu repositorio de GitHub

Añadir las variables de entorno requeridas

VITE_SUPABASE_URL VITE_SUPABASE_ANON_KEY

VITE_SUPABASE_URL

URL del proyecto

VITE_SUPABASE_ANON_KEY

Clave anon (pública)

Obtén estos valores en Supabase

Abrir la configuración de API

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

Abre tu sitio web en producción

Envía los emails de cita automáticamente

Haz el sistema de reservas más profesional con emails de cita automáticos.

- Envía un email de nueva reserva al administrador

- Envía un email de confirmación al paciente

Mejora opcional después del despliegue.

Haz que tu sitio web con IA envíe emails automáticamente (tutorial de Supabase)

Ver tutorial

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

Envía SMS de citas automáticamente

Haz que tu sistema de reservas sea más profesional con confirmaciones SMS automáticas después de cada reserva.

- Envía una confirmación SMS al cliente

- Notifica también al propietario del negocio por SMS (opcional)

Añade notificaciones SMS a tu sitio de reservas con IA

Ver tutorial

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