Crea un sito di prenotazione per barberia con Claude Code

Scegli il tipo di progetto

Sito di prenotazione barberia

Sito di prenotazione clinica dentistica

Sito di prenotazione parrucchiere

Sito di prenotazione barberia

Sito di prenotazione spa

Sito di prenotazione personal trainer

Sito di prenotazione coaching

Sito di prenotazione ristorante

Sito di prenotazione salone di bellezza

Sito di prenotazione massaggi terapeutici

Sito di prenotazione centro unghie

Sito di prenotazione fotografo

Sito di prenotazione toelettatura animali

Sito di prenotazione studio di yoga

Sito di prenotazione studio di tatuaggi

Sito di prenotazione lezioni di danza

Sito di prenotazione lezioni di fitness

Sito di prenotazione terapia e counseling

Sito di prenotazione chiropratico

Sito di prenotazione fisioterapista

Sito di prenotazione car detailing

Sito di prenotazione officina auto

Sito di prenotazione servizio di pulizia

Sito di prenotazione riparazioni domestiche

Sito di prenotazione cura del giardino

Sito di prenotazione event planner

Sito di prenotazione wedding planner

Sito di prenotazione makeup artist

Sito di prenotazione estetista

Sito di prenotazione tutor privato

Sito di prenotazione scuola guida

Sito di prenotazione visite immobiliari

Sito di prenotazione agente immobiliare

Anteprima del flusso di prenotazione

- Seleziona servizio

- Seleziona data

- Seleziona orario

- Conferma prenotazione

Dettagli del cliente raccolti

- Nome completo

- E-mail

- Telefono

- Note opzionali

Creare un progetto Supabase

Crea un nuovo progetto Supabase per il backend del tuo sistema di prenotazione.

Apri Supabase

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

Creare l'utente admin

Crea un utente admin in Supabase Authentication, poi copia lo user ID.

Eseguire il SQL di configurazione completa

Incolla il tuo user ID admin, poi esegui questo codice SQL nel SQL Editor di Supabase. Configurerà tutto in una volta sola: tabelle, policy di sicurezza e accesso admin.

SQL di configurazione 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 barbershop_settings ( id uuid primary key default gen_random_uuid(), barbershop_name text not null default 'Luxe Barber Studio', barbershop_email text, barbershop_phone text, barbershop_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 ('Classic Haircut', 'A clean, tailored haircut finished with professional styling.', 45, 35), ('Skin Fade', 'Sharp fade with detailed blending and a polished finish.', 60, 45), ('Beard Trim', 'Beard shaping, trimming, and line-up for a clean look.', 30, 25), ('Haircut & Beard', 'Complete grooming package with haircut, beard trim, and styling.', 75, 65), ('Hot Towel Shave', 'Traditional straight razor shave with hot towel treatment.', 45, 40), ('Kids Haircut', 'Simple and clean haircut for younger clients.', 30, 25); insert into business_hours (weekday, is_open, start_time, end_time) values (0, false, null, null), (1, true, '09:00', '18:00'), (2, true, '09:00', '18:00'), (3, true, '09:00', '18:00'), (4, true, '09:00', '18:00'), (5, true, '09:00', '19:00'), (6, true, '10:00', '17:00'); insert into barbershop_settings (barbershop_name, barbershop_email, barbershop_phone, barbershop_address, slot_interval_minutes, booking_notice_hours) values ('Luxe Barber Studio', 'hello@luxebarber.com', '+1 555 345 7890', '128 Brooklyn 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 barbershop_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 barbershop settings" on barbershop_settings for select to anon, authenticated using (true); create policy "Admins can manage barbershop settings" on barbershop_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 admin

Inserisci il tuo user ID di Supabase Auth

Configurazione SQL passo dopo passo (opzionale)

Creare le tabelle del database

Esegui queste query SQL dentro il SQL Editor di Supabase.

Tabella dei servizi

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

Tabella appuntamenti

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

Tabella orari del business

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

Tabella date bloccate

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

Tabella delle impostazioni

create table barbershop_settings ( id uuid primary key default gen_random_uuid(), barbershop_name text not null default 'Luxe Barber Studio', barbershop_email text, barbershop_phone text, barbershop_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() );

Aggiungere i dati iniziali

Esegui queste query iniziali.

Inserire i servizi iniziali

insert into services (name, description, duration_minutes, price) values ('Classic Haircut', 'A clean, tailored haircut finished with professional styling.', 45, 35), ('Skin Fade', 'Sharp fade with detailed blending and a polished finish.', 60, 45), ('Beard Trim', 'Beard shaping, trimming, and line-up for a clean look.', 30, 25), ('Haircut & Beard', 'Complete grooming package with haircut, beard trim, and styling.', 75, 65), ('Hot Towel Shave', 'Traditional straight razor shave with hot towel treatment.', 45, 40), ('Kids Haircut', 'Simple and clean haircut for younger clients.', 30, 25);

Inserire gli orari del business

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

Inserisci le impostazioni

insert into barbershop_settings (barbershop_name, barbershop_email, barbershop_phone, barbershop_address, slot_interval_minutes, booking_notice_hours) values ('Luxe Barber Studio', 'hello@luxebarber.com', '+1 555 345 7890', '128 Brooklyn Avenue, New York, NY', 30, 2);

Mettere in sicurezza la dashboard admin

1. Crea la tabella di accesso admin Crea una tabella che definisce quali utenti autenticati possono accedere e gestire la dashboard admin.

Tabella 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. Abilita Row Level Security Attiva RLS sulle tabelle che devono essere protette dagli utenti normali.

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

3. Aggiungi le policy admin Permetti agli utenti pubblici di leggere solo ciò che serve al sito di prenotazione e consenti solo agli utenti admin di gestire i dati protetti.

Policy 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 barbershop settings" on barbershop_settings for select to anon, authenticated using (true); create policy "Admins can manage barbershop settings" on barbershop_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. Aggiungi il tuo utente admin Crea prima il tuo account admin dalla schermata di login dell'app, poi inserisci il tuo user ID autenticato nella tabella admin_users.

Inserire il tuo utente admin

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

Usa il Prompt 1 per costruire il progetto

Prompt 1: Costruire il progetto completo di barberia

Crea un sito di barberia moderno e premium con un vero sistema di prenotazione…

You are a world-class full-stack product builder, creative director, and UI/UX designer. Build a premium modern barbershop 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 ================================================ 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 ================================================ 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 barbershop_settings: - id - barbershop_name - barbershop_email - barbershop_phone - barbershop_address - slot_interval_minutes - booking_notice_hours - created_at admin_users: - id - user_id - created_at Important: - Use barbershop_settings, not salon_settings - Use barbershop_settings, not clinic_settings - Use barbershop_name, barbershop_email, barbershop_phone, and barbershop_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 barbershop booking website where visitors can: - view barbershop 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 barbershop owner can manage: - appointments - services - business hours - blocked dates - barbershop 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 - masculine - sharp - stylish - refined - confident - trustworthy - polished - realistic for a premium local barbershop The dashboard should feel: - premium - clean - modern - product-like - organized - smooth - easy for a barbershop owner or 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 ================================================ VISUAL DESIGN SYSTEM ================================================ Use a premium barbershop visual style: - deep charcoal / near-black backgrounds - warm cream or off-white contrast sections - bronze, copper, tan, amber, or muted gold accents - espresso / dark brown tones - sharp typography - confident visual hierarchy - refined borders - soft shadows - layered visuals - depth - subtle gradients - dramatic but tasteful lighting - premium contrast - polished cards - strong CTA buttons - tasteful barber imagery or grooming visual elements Use depth, gradients, lighting, and layered visuals where appropriate. Avoid flat backgrounds. Create strong contrast and hierarchy. Make the interface feel intentionally designed, not assembled from default components. Typography: - improve hierarchy and readability - make headings expressive and premium - use elegant, strong, modern 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 barbershop 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 barbershop photography - cinematic lighting - warm contrast - dark charcoal, bronze, tan, espresso, cream tones - masculine and refined - modern but not flashy - realistic and professional - clean composition - strong lighting - good cropping - consistent visual style across the website Good image subjects: - barber cutting hair - fade haircut detail - beard trimming - hot towel shave - straight razor detail - barber tools - barber chair - premium barbershop interior - grooming products - close-up craftsmanship shots Do not use: - dental or medical imagery - beauty salon imagery that feels too feminine - nail salon images - spa imagery - generic office imagery - random model portraits unrelated to barbering - low-resolution images - awkward stock photos - broken image links 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 barbershop brand, improve trust, and make the section feel more premium. ================================================ BRAND DIRECTION ================================================ Use barbershop-specific language: - Barbershop - Barber - Grooming - Client - Appointment - Service - Haircut - Fade - Beard Trim - Shave - Line-up - Book your cut - Reserve your chair Do not use: - salon - stylist - clinic - patient - dental - dentist - doctor - medical - healthcare - teeth The website should feel like a premium barbershop brand, not: - a hair salon website - a dental clinic - a medical website - a generic SaaS landing page - a fashion magazine - a random beauty 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 barbershop_settings for barbershop name, email, phone, and address when available - Make the booking section polished and easy to follow - Use strong barbershop-specific imagery throughout the public website - The site should look like a real premium barbershop 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 barbershop visual - use cinematic barbershop imagery, barber tools, haircut/fade detail, grooming, or a premium barbershop interior - use image overlays, gradients, lighting, or layered composition for depth - maintain strong text readability - strong headline hierarchy - elegant supporting text - polished CTA buttons - not generic - not flat - not basic Services: - should not look like a plain list - make services feel premium 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: - Classic Haircut: barber cutting hair - Skin Fade: close-up fade haircut detail - Beard Trim: beard grooming or razor detail - Haircut & Beard: barber styling a client - Hot Towel Shave: towel, shave, or straight razor visual - Kids Haircut: clean friendly haircut visual, if used Keep service images consistent in crop, quality, and style. Do not use random unrelated beauty images. About: - confident, warm, and intentional - visually balanced - should reinforce craftsmanship, precision, care, and style - include a strong barbershop-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 barbershop settings where relevant ================================================ BOOKING FLOW ================================================ Step 1: Select a barbershop 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 - barbershop_settings.slot_interval_minutes - barbershop_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. Barbershop 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. Barbershop Settings: Allow editing: - barbershop_name - barbershop_email - barbershop_phone - barbershop_address - slot_interval_minutes - booking_notice_hours Updated barbershop 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 - Barbershop settings editing working - Public website uses high-quality barbershop-specific imagery - Hero section includes a strong relevant barbershop visual - Services section includes relevant niche-specific visual treatment or images - About section includes authentic barbershop 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 barbershop 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 barbershop booking platform with a high-end public website, strong niche-specific imagery, and a polished admin dashboard.

Opzionale: Parti da un progetto pronto

Sito di prenotazione barberia

Inizia più velocemente con il progetto pronto

PROJECT

https://profitstudio.app/template/barbershop-booking-website

Aggiungere le variabili di ambiente Supabase

Aggiungi il Supabase Project URL e la Publishable Key in un file .env.local per i test locali.

Installare Git

Assicurati che Git sia installato sul tuo computer prima di caricare il progetto su GitHub.

Scarica Git

https://git-scm.com/

Collegare VS Code a GitHub

Accedi al tuo account GitHub all'interno di VS Code.

Creare un repository GitHub

Crea un nuovo repository GitHub privato e copia l'URL del repository.

Caricare il progetto su GitHub

Apri Claude Code in VS Code, incolla il Prompt sicuro per il push su GitHub e aggiungi l'URL del tuo repository GitHub. Dopo che Claude ha preparato il progetto, apri Source Control in VS Code, poi esegui il commit e sincronizza le modifiche.

Prompt sicuro per il push su GitHub

Aggiungi l'URL del tuo repository GitHub qui sotto, poi usa il prompt personalizzato in Claude Code.

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

URL del repository GitHub

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

Creare un'app Node.js su Hostinger

Apri Hostinger, crea una nuova app Node.js e scegli il tuo dominio.

Apri Hostinger

Pubblica questo progetto con la stessa configurazione mostrata nel video.

RECOMMENDED

https://www.hostg.xyz/SHJe0

Importare il repository e distribuire

Importa il tuo repository GitHub, aggiungi le variabili d'ambiente richieste, poi clicca su Distribuisci.

VITE_SUPABASE_URL VITE_SUPABASE_ANON_KEY

VITE_SUPABASE_URL

URL del progetto

VITE_SUPABASE_ANON_KEY

Chiave anon (pubblica)

Recupera questi valori da Supabase

Apri le impostazioni API

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

Invia automaticamente le e-mail degli appuntamenti

Rendi il sistema di prenotazione più professionale con e-mail automatiche per gli appuntamenti.

- Invia un'e-mail di nuova prenotazione all'amministratore

- Invia un'e-mail di conferma al paziente

Upgrade opzionale dopo il deploy.

Fai inviare e-mail automaticamente al tuo sito con IA (tutorial Supabase)

Guarda il tutorial

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

Invia SMS di appuntamento automaticamente

Rendi più professionale il tuo sistema di prenotazione con conferme SMS automatiche dopo ogni prenotazione.

- Invia una conferma SMS al cliente

- Notifica anche il proprietario dell'attività via SMS (opzionale)

Aggiungi notifiche SMS al tuo sito di prenotazione con IA

Guarda il tutorial

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