Claude Code로 바버샵 예약 사이트 만들기

프로젝트 유형 선택하기

바버샵 예약 사이트

치과 예약 사이트

헤어살롱 예약 사이트

바버샵 예약 사이트

스파 예약 사이트

퍼스널 트레이너 예약 사이트

코칭 예약 사이트

레스토랑 예약 사이트

뷰티 살롱 예약 사이트

마사지 예약 사이트

네일샵 예약 사이트

사진 촬영 예약 사이트

반려동물 미용 예약 사이트

요가 스튜디오 예약 사이트

타투 스튜디오 예약 사이트

댄스 클래스 예약 사이트

피트니스 클래스 예약 사이트

심리 상담 예약 사이트

카이로프랙틱 예약 사이트

물리치료 예약 사이트

카 디테일링 예약 사이트

자동차 정비 예약 사이트

청소 서비스 예약 사이트

집수리 예약 사이트

잔디 관리 예약 사이트

이벤트 플래너 예약 사이트

웨딩 플래너 예약 사이트

메이크업 아티스트 예약 사이트

에스테틱 예약 사이트

과외 예약 사이트

운전학원 예약 사이트

매물 방문 예약 사이트

부동산 중개 예약 사이트

예약 흐름 미리보기

- 서비스 선택

- 날짜 선택

- 시간 선택

- 예약 확정

수집한 고객 정보

- 이름

- 이메일

- 전화번호

- 요청사항 (선택)

Supabase 프로젝트 만들기

예약 시스템 백엔드를 위한 새 Supabase 프로젝트를 만듭니다.

Supabase 열기

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

관리자 계정 만들기

Supabase Authentication에서 관리자 계정을 만든 뒤 사용자 ID를 복사합니다.

전체 설정 SQL 실행하기

관리자 사용자 ID를 붙여넣은 뒤, 이 SQL 코드를 Supabase SQL Editor에서 실행하세요. 테이블, 보안 정책, 관리자 접근 권한이 한 번에 설정됩니다.

전체 설정 SQL

create table services ( id uuid primary key default gen_random_uuid(), name text not null, description text, duration_minutes integer not null check (duration_minutes > 0), price numeric(10,2), is_active boolean not null default true, created_at timestamp with time zone default now() ); create table appointments ( id uuid primary key default gen_random_uuid(), full_name text not null, email text not null, phone text not null, service_id uuid not null references services(id) on delete restrict, appointment_date date not null, start_time time not null, end_time time not null, status text not null default 'pending' check (status in ('pending', 'confirmed', 'cancelled', 'completed')), notes text, created_at timestamp with time zone default now() ); create table business_hours ( id uuid primary key default gen_random_uuid(), weekday integer not null check (weekday between 0 and 6), is_open boolean not null default true, start_time time, end_time time ); create table blocked_dates ( id uuid primary key default gen_random_uuid(), blocked_date date not null unique, reason text, created_at timestamp with time zone default now() ); create table 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');

관리자 사용자 ID

Supabase 인증 사용자 ID 입력

단계별 SQL 설정 (선택)

데이터베이스 테이블 만들기

이 SQL 쿼리들을 Supabase SQL Editor에서 실행합니다.

서비스 테이블

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

초기 데이터 추가하기

이 초기 쿼리들을 실행합니다.

기본 서비스 등록하기

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', '17:00'), (2, true, '09:00', '17:00'), (3, true, '09:00', '17:00'), (4, true, '09:00', '17:00'), (5, true, '09:00', '17:00'), (6, true, '09:00', '13:00');

설정 등록하기

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

관리자 대시보드 보호하기

1. 관리자 접근 테이블 만들기 인증된 사용자 중 누가 관리자 대시보드에 접근하고 관리할 수 있는지 정의하는 테이블을 만듭니다.

관리자 사용자 테이블

create table admin_users ( id uuid primary key default gen_random_uuid(), user_id uuid not null unique references auth.users(id) on delete cascade, created_at timestamp with time zone default now() );

2. Row Level Security 켜기 일반 사용자로부터 보호해야 하는 테이블에 RLS를 켭니다.

RLS 켜기

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

3. 관리자 정책 추가하기 일반 사용자에게는 예약 사이트에 필요한 데이터만 읽을 수 있게 하고, 보호된 데이터는 관리자만 관리할 수 있게 합니다.

관리자 정책

create policy "Anyone can read active services" on services for select to anon, authenticated using (is_active = true); create policy "Admins can manage services" on services for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can create appointments" on appointments for insert to anon, authenticated with check (true); create policy "Admins can read appointments" on appointments for select to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Admins can update appointments" on appointments for update to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can read business hours" on business_hours for select to anon, authenticated using (true); create policy "Admins can manage business hours" on business_hours for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can read blocked dates" on blocked_dates for select to anon, authenticated using (true); create policy "Admins can manage blocked dates" on blocked_dates for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can read 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. 관리자 계정 추가하기 먼저 앱 로그인 화면에서 관리자 계정을 만든 뒤, 인증된 사용자 ID를 admin_users 테이블에 넣습니다.

관리자 계정 등록하기

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

프롬프트 1로 프로젝트 만들기

프롬프트 1 : 바버샵 프로젝트 전체 만들기

실제 예약 기능을 갖춘 고급스럽고 모던한 바버샵 사이트를 만듭니다…

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.

선택: 준비된 프로젝트로 시작하기

바버샵 예약 사이트

준비된 프로젝트로 더 빠르게 시작하기

PROJECT

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

Supabase 환경 변수 추가하기

로컬 테스트를 위해 Supabase Project URL과 Publishable Key를 .env.local 파일에 추가합니다.

Git 설치하기

프로젝트를 GitHub에 푸시하기 전에 컴퓨터에 Git이 설치되어 있는지 확인하세요.

Git 다운로드하기

https://git-scm.com/

VS Code를 GitHub에 연결하기

VS Code 안에서 GitHub 계정에 로그인합니다.

GitHub 저장소 만들기

새 비공개 GitHub 저장소를 만들고 저장소 URL을 복사합니다.

프로젝트를 GitHub에 푸시하기

VS Code 안에서 Claude Code를 열고, 안전한 GitHub 푸시 프롬프트를 붙여넣은 뒤 GitHub 저장소 URL을 추가합니다. Claude가 프로젝트를 정리하면 VS Code에서 Source Control을 열고 변경 내용을 커밋한 뒤 동기화합니다.

안전한 GitHub 푸시 프롬프트

아래에 GitHub 저장소 URL을 입력한 뒤, 맞춤 설정된 프롬프트를 Claude Code에서 사용합니다.

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

GitHub 저장소 URL

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

Hostinger Node.js Web App 만들기

Hostinger를 열고 새 Node.js 웹 앱을 만든 뒤 도메인을 선택합니다.

Hostinger 열기

영상과 똑같은 구성으로 이 프로젝트를 공개합니다.

RECOMMENDED

https://www.hostg.xyz/SHJe0

저장소를 가져와 배포하기

GitHub 저장소를 가져오고 필요한 환경 변수를 추가한 뒤 Deploy를 클릭합니다.

VITE_SUPABASE_URL VITE_SUPABASE_ANON_KEY

VITE_SUPABASE_URL

프로젝트 URL

VITE_SUPABASE_ANON_KEY

anon(공개) 키

이 값들은 Supabase에서 확인하세요

API 설정 열기

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

예약 이메일 자동으로 보내기

예약 이메일 자동 발송으로 예약 시스템을 더 전문적으로 만듭니다.

- 관리자에게 신규 예약 이메일 보내기

- 환자에게 확인 이메일 보내기

배포한 뒤 선택적으로 추가하는 업그레이드입니다.

AI 사이트에서 이메일 자동 발송되게 만들기 (Supabase 튜토리얼)

튜토리얼 보기

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

예약 SMS 자동으로 보내기

예약이 들어올 때마다 자동으로 SMS 확인을 보내 예약 시스템을 더 전문적으로 만듭니다.

- 고객에게 확인 SMS 보내기

- 선택 시 사장님에게 SMS로 알림

AI 예약 사이트에 SMS 알림 추가하기

튜토리얼 보기

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