Crie um site de agendamento para cuidado de jardim com Claude Code

Escolha o tipo de projeto

Site de agendamento de cuidado de jardim

Site de agendamento de clínica odontológica

Site de agendamento de salão de cabeleireiro

Site de agendamento de barbearia

Site de agendamento de spa

Site de agendamento de personal trainer

Site de agendamento de coaching

Site de reserva de restaurante

Site de agendamento de salão de beleza

Site de agendamento de terapia de massagem

Site de agendamento de salão de unhas

Site de agendamento de fotógrafo

Site de agendamento de banho e tosa

Site de agendamento de estúdio de yoga

Site de agendamento de estúdio de tatuagem

Site de agendamento de aulas de dança

Site de agendamento de aulas de fitness

Site de agendamento de terapia e aconselhamento

Site de agendamento de quiropraxista

Site de agendamento de fisioterapeuta

Site de agendamento de estética automotiva

Site de agendamento de oficina automotiva

Site de agendamento de serviço de limpeza

Site de agendamento de reparos residenciais

Site de agendamento de cuidado de jardim

Site de agendamento de organizador de eventos

Site de agendamento de wedding planner

Site de agendamento de maquiadora

Site de agendamento de esteticista

Site de agendamento de professor particular

Site de agendamento de autoescola

Site de agendamento de visitas de imóveis

Site de agendamento de corretor de imóveis

Pré-visualização do fluxo de agendamento

- Selecionar serviço

- Selecionar data

- Selecionar horário

- Confirmar agendamento

Detalhes do cliente coletados

- Nome completo

- E-mail

- Telefone

- Observações opcionais

Criar um projeto no Supabase

Crie um novo projeto Supabase para o backend do seu sistema de agendamento.

Abrir o Supabase

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

Criar o usuário admin

Crie um usuário admin no Supabase Authentication e depois copie o user ID.

Rodar o SQL de configuração completa

Cole seu user ID de admin e depois rode este código SQL no SQL Editor do Supabase. Ele configura tudo de uma vez: tabelas, políticas de segurança e acesso de admin.

SQL de configuração 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 business_settings ( id uuid primary key default gen_random_uuid(), business_name text not null default 'GreenEdge Lawn Care', business_email text, business_phone text, business_address text, slot_interval_minutes integer not null default 30, booking_notice_hours integer not null default 6, 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 ('Lawn Mowing Service', 'A reliable lawn mowing appointment for keeping grass neat, clean, and well-maintained.', 60, 65), ('Lawn Maintenance Visit', 'A complete lawn care visit including mowing, edging, trimming, and basic cleanup.', 120, 140), ('Hedge & Shrub Trimming', 'A focused trimming service for hedges, shrubs, and landscape edges to improve curb appeal.', 90, 110), ('Seasonal Yard Cleanup', 'A detailed cleanup service for leaves, branches, debris, and seasonal outdoor maintenance needs.', 180, 220), ('Fertilization Service', 'A lawn treatment appointment designed to support healthier grass and better seasonal growth.', 60, 95), ('Landscape Consultation', 'A consultation visit to review your yard, discuss lawn care needs, and recommend the right service plan.', 45, 60); insert into business_hours (weekday, is_open, start_time, end_time) values (0, false, null, null), (1, true, '08:00', '18:00'), (2, true, '08:00', '18:00'), (3, true, '08:00', '18:00'), (4, true, '08:00', '18:00'), (5, true, '08:00', '17: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 ('GreenEdge Lawn Care', 'hello@greenedgelawncare.com', '+1 555 890 4567', '62 Garden Service Road, New York, NY', 30, 6); 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');

User ID do admin

Informe seu user ID do Supabase Auth

Configuração SQL passo a passo (opcional)

Criar as tabelas do banco de dados

Rode essas queries SQL dentro do SQL Editor do Supabase.

Tabela de serviços

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

Tabela de agendamentos

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

Tabela de horários do negócio

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

Tabela de datas 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() );

Tabela de definições

create table business_settings ( id uuid primary key default gen_random_uuid(), business_name text not null default 'GreenEdge Lawn Care', business_email text, business_phone text, business_address text, slot_interval_minutes integer not null default 30, booking_notice_hours integer not null default 6, created_at timestamp with time zone default now() );

Adicionar os dados iniciais

Rode essas queries iniciais.

Inserir os serviços iniciais

insert into services (name, description, duration_minutes, price) values ('Lawn Mowing Service', 'A reliable lawn mowing appointment for keeping grass neat, clean, and well-maintained.', 60, 65), ('Lawn Maintenance Visit', 'A complete lawn care visit including mowing, edging, trimming, and basic cleanup.', 120, 140), ('Hedge & Shrub Trimming', 'A focused trimming service for hedges, shrubs, and landscape edges to improve curb appeal.', 90, 110), ('Seasonal Yard Cleanup', 'A detailed cleanup service for leaves, branches, debris, and seasonal outdoor maintenance needs.', 180, 220), ('Fertilization Service', 'A lawn treatment appointment designed to support healthier grass and better seasonal growth.', 60, 95), ('Landscape Consultation', 'A consultation visit to review your yard, discuss lawn care needs, and recommend the right service plan.', 45, 60);

Inserir os horários do negócio

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

Inserir as definições

insert into business_settings (business_name, business_email, business_phone, business_address, slot_interval_minutes, booking_notice_hours) values ('GreenEdge Lawn Care', 'hello@greenedgelawncare.com', '+1 555 890 4567', '62 Garden Service Road, New York, NY', 30, 6);

Proteger o dashboard admin

1. Crie a tabela de acesso de admin Crie uma tabela que define quais usuários autenticados podem acessar e gerenciar o dashboard admin.

Tabela 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. Habilite o Row Level Security Ative o RLS nas tabelas que devem ser protegidas dos usuários comuns.

Habilitar o 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. Adicione as políticas de admin Deixe usuários públicos lerem só o necessário para o site de agendamento e permita que apenas usuários admin gerenciem os dados protegidos.

Políticas de admin

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. Adicione seu usuário admin Crie primeiro sua conta de admin na tela de login do app, depois insira o seu user ID autenticado na tabela admin_users.

Inserir seu usuário admin

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

Use o Prompt 1 para construir o projeto

Prompt 1: Construir o projeto completo de cuidado de jardim

Crie um site de clínica odontológica premium e moderno com sistema real de agendamento…

You are a world-class full-stack product builder, creative director, and UI/UX designer. Build a premium modern lawn care 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 outdoor service and local business 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 lawn care 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 lawn care 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 lawn_settings. - Do not use lawn_care_settings. - Do not use landscaping_settings. - Do not use outdoor_settings. - Do not use service_settings. - Do not use company_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 lawn care booking website where visitors can: - view lawn care 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 lawn care business owner, manager, or service team 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 lawn care service brand. The public website should feel: - premium - modern - fresh - clean - outdoor-focused - trustworthy - reliable - professional - organized - polished - homeowner-friendly - realistic for a premium local lawn care business The dashboard should feel: - premium - clean - modern - product-like - organized - smooth - easy for a lawn care service 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 outdoor-service-focused, premium, fresh, trustworthy, and professional - Do not make it look like a dental clinic, beauty salon, massage studio, restaurant, gym, auto repair shop, cleaning company, coaching website, or generic SaaS landing page ================================================ VISUAL DESIGN SYSTEM ================================================ Use a premium lawn care visual style: - clean white, soft off-white, fresh green, pale sage, light beige, sky blue, warm gray, and natural neutral backgrounds - refined green, deep forest, lime, soft yellow, earthy brown, navy, and fresh outdoor accent colors - clean outdoor-service contrast - polished service cards - refined borders - soft shadows - layered visuals - subtle gradients - bright natural lighting effects - fresh airy depth - premium buttons - minimal lawn care and outdoor service icons - high-quality lawn care and landscaping 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, clean, fresh, premium, and trustworthy - use modern, readable typography - avoid overly decorative fonts - dashboard should stay clean, readable, and product-like Layout: - improve spacing and composition - use modern section layouts - use fresh outdoor-service visual storytelling - introduce tasteful asymmetry where appropriate - create bright image-led 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 fresh and professional, not distracting ================================================ IMAGE AND VISUAL STORYTELLING REQUIREMENTS ================================================ The public website must use strong, high-quality, niche-specific lawn care 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, fresh, trustworthy, and premium. Image style: - premium lawn care service photography - clean green lawns and outdoor spaces - professional lawn care worker shown tastefully - mowing, edging, trimming, and yard maintenance scenes - organized lawn care tools and equipment - fresh natural daylight - well-maintained yards, gardens, hedges, and curb appeal - professional outdoor service atmosphere - refined and realistic - good cropping - consistent visual style across the website Good image subjects: - freshly mowed green lawn - professional mowing a clean yard - edging along a walkway or driveway - hedge and shrub trimming scene - lawn care tools arranged neatly - seasonal yard cleanup with leaves and outdoor equipment - fertilization or lawn treatment shown safely - beautiful front yard with curb appeal - service truck or equipment in a clean outdoor setting - homeowner consultation in a yard Do not use: - dental imagery - medical clinic imagery - massage therapy imagery - beauty salon imagery - barbershop imagery - restaurant imagery - fitness imagery - automotive imagery - extreme disaster yard scenes - unsafe equipment use - hazardous chemical imagery - messy or chaotic outdoor work scenes - low-resolution images - awkward stock photos - broken image links - random model portraits unrelated to lawn care 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 lawn care brand, improve trust, and make the section feel more premium. ================================================ BRAND DIRECTION ================================================ Use lawn care-specific language: - Lawn Care - Lawn Service - Yard Maintenance - Landscaping Support - Lawn Mowing - Lawn Maintenance - Hedge Trimming - Shrub Trimming - Seasonal Yard Cleanup - Fertilization Service - Landscape Consultation - Service Team - Homeowner - Client - Customer - Appointment - Service - Fresh Lawn - Curb Appeal - Book your lawn care - Schedule your service - Reserve your lawn care appointment Do not use: - dental - dentist - patient - oral health - massage therapy - therapist - beauty salon - stylist - medical - healthcare - barber - barbershop - restaurant - reservation - table - fitness - workout - auto repair - vehicle service - cleaning service - coaching Avoid unrealistic claims. Do not promise perfect lawn results in every situation. Do not use unsafe equipment advice. Do not include pesticide, chemical, or hazardous treatment instructions. Do not use fear-based messaging. Focus on reliability, curb appeal, outdoor care, professionalism, convenience, careful work, trust, and a polished customer 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 lawn care company name, email, phone, and address when available. - Use business_name as the company name. - Use business_email as the company email. - Use business_phone as the company phone. - Use business_address as the company address. - Make the booking section polished and easy to follow. - Use strong lawn care-specific imagery throughout the public website. - The site should look like a real premium lawn care website, not a simple template. ================================================ PUBLIC WEBSITE QUALITY EXPECTATIONS ================================================ Navbar: - refined and premium - clean outdoor service brand presence - elegant spacing - polished booking CTA Hero: - visually striking and premium - must include a strong, relevant lawn care visual - use imagery such as a freshly mowed lawn, professional lawn care worker, clean yard, edging scene, green outdoor space, or beautiful front yard - use image overlays, gradients, lighting, or layered composition for depth - maintain strong text readability - strong headline hierarchy - fresh 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, fresh, 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: - Lawn Mowing Service: freshly cut grass or mowing scene - Lawn Maintenance Visit: edging, trimming, and clean yard detail - Hedge & Shrub Trimming: hedge trimming or shaped shrubs - Seasonal Yard Cleanup: leaves, cleanup tools, or tidy outdoor space - Fertilization Service: safe lawn treatment visual or healthy grass detail - Landscape Consultation: homeowner consultation in a yard or landscape planning Keep service images consistent in crop, quality, and style. Do not use unsafe equipment scenes, hazardous chemicals, extreme yard damage, or unrelated outdoor images. About: - fresh, practical, professional, and intentional - visually balanced - should reinforce trust, reliability, curb appeal, outdoor care, careful work, convenience, and professional service - include a strong lawn care-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/customer 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 lawn care 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 customer-focused and outdoor-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/customer 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: - Company Name - Company Email - Company Phone - Company 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 lawn care-specific imagery - Hero section includes a strong relevant lawn care visual - Services section includes relevant niche-specific visual treatment or images - About section includes authentic lawn care 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 lawn care 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 lawn care 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.

Opcional: Comece com um projeto pronto

Site de agendamento de cuidado de jardim

Comece mais rápido com o projeto pronto

PROJECT

https://profitstudio.app/template/lawn-care-booking-website

Adicionar variáveis de ambiente do Supabase

Adicione a URL do projeto Supabase e a Publishable Key em um arquivo .env.local para testes locais.

Instalar o Git

Certifica-te de que o Git está instalado no teu computador antes de enviar o projeto para o GitHub.

Baixar o Git

https://git-scm.com/

Conectar VS Code ao GitHub

Inicia sessão com a tua conta do GitHub dentro do VS Code.

Criar um repositório no GitHub

Cria um novo repositório privado no GitHub e copia o URL do repositório.

Enviar o projeto para o GitHub

Abre o Claude Code no VS Code, cola o Prompt seguro para publicar no GitHub e adiciona o URL do teu repositório GitHub. Depois de o Claude preparar o projeto, abre o Source Control no VS Code e faz commit e sync das alterações.

Prompt seguro para publicar no GitHub

Adiciona o URL do teu repositório GitHub abaixo e usa o prompt personalizado no Claude Code.

I already created an empty GitHub repository. GitHub repository URL: {{GITHUB_REPOSITORY_URL}} Please prepare and push this local project to that GitHub repository. Rules: - Do not change the app code, UI, design, routes, database logic, backend logic, Supabase logic, or functionality. - Only handle Git and GitHub publishing. - Check Git status, branch, remotes, .gitignore, and tracked files first. - Make sure .env and .env.local are not committed. - Make sure generated files like node_modules, dist, dist-ssr, *.tsbuildinfo, .DS_Store, and log files are ignored. - If unnecessary files are already tracked, remove them from Git tracking only. Do not delete real project files. - Use main for a new repository, unless an existing branch should be preserved. - Connect this project to the GitHub repository URL. - Create a clean commit if needed. - Push the project to GitHub. If the push fails, diagnose and fix only the Git/GitHub setup. Do not change app functionality. Before any destructive action, explain what you found and what you plan to do.

URL do repositório GitHub

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

Criar uma aplicação Node.js na Hostinger

Abre a Hostinger, cria uma nova aplicação Node.js e escolhe o teu domínio.

Abrir a Hostinger

Publique este projeto com a mesma configuração mostrada no vídeo.

RECOMMENDED

https://www.hostg.xyz/SHJe0

Importar o repositório e fazer deploy

Importa o teu repositório GitHub, adiciona as variáveis de ambiente necessárias e clica em Deploy.

VITE_SUPABASE_URL VITE_SUPABASE_ANON_KEY

VITE_SUPABASE_URL

URL do projeto

VITE_SUPABASE_ANON_KEY

Chave anon (pública)

Obtenha esses valores no Supabase

Abrir configurações de API

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

Envie e-mails de agendamento automaticamente

Deixe o sistema de agendamento mais profissional com e-mails de agendamento automáticos.

- Envia um e-mail de novo agendamento ao administrador

- Envia um e-mail de confirmação ao paciente

Upgrade opcional após o deploy.

Faça seu site com IA enviar e-mails automaticamente (tutorial Supabase)

Assistir ao tutorial

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

Envie SMS de agendamento automaticamente

Torne o seu sistema de agendamento mais profissional com confirmações SMS automáticas após cada agendamento.

- Envie uma confirmação SMS ao cliente

- Notifique também o dono do negócio por SMS (opcional)

Adicione notificações SMS ao seu site de agendamento com IA

Assistir ao tutorial

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