AIでスパの予約サイトを作る

プロジェクトの種類を選ぶ

スパの予約サイト

歯科クリニックの予約サイト

ヘアサロンの予約サイト

バーバーショップの予約サイト

スパの予約サイト

パーソナルトレーナーの予約サイト

コーチングの予約サイト

レストラン予約サイト

美容サロンの予約サイト

マッサージの予約サイト

ネイルサロンの予約サイト

写真撮影の予約サイト

ペットトリミングの予約サイト

ヨガスタジオの予約サイト

タトゥースタジオの予約サイト

ダンス教室の予約サイト

フィットネスクラスの予約サイト

セラピー・カウンセリングの予約サイト

カイロプラクティックの予約サイト

理学療法の予約サイト

カーディテーリングの予約サイト

自動車整備の予約サイト

ハウスクリーニングの予約サイト

住宅修繕の予約サイト

芝生メンテナンスの予約サイト

イベントプランナーの予約サイト

ウェディングプランナーの予約サイト

メイクアップアーティストの予約サイト

エステティシャンの予約サイト

家庭教師の予約サイト

自動車教習所の予約サイト

内見予約サイト

不動産エージェントの予約サイト

予約フローのプレビュー

- サービスを選択

- 日付を選択

- 時間を選択

- 予約を確定する

受け取ったお客様情報

- 氏名

- メールアドレス

- 電話番号

- 備考（任意）

Supabaseプロジェクトを作成する

予約システムのバックエンド用に、新しいSupabaseプロジェクトを作成します。

管理者ユーザーを作成する

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 spa_settings ( id uuid primary key default gen_random_uuid(), spa_name text not null default 'Serenity Spa Studio', spa_email text, spa_phone text, spa_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 ('Relaxation Massage', 'A calming full-body massage designed to release tension and restore balance.', 60, 90), ('Deep Tissue Massage', 'Focused therapeutic massage for muscle tension, stress relief, and recovery.', 75, 120), ('Aromatherapy Massage', 'A soothing massage experience using essential oils for relaxation and wellness.', 60, 105), ('Signature Facial', 'A personalized facial treatment to cleanse, hydrate, and refresh the skin.', 60, 85), ('Body Scrub Treatment', 'A gentle exfoliating body treatment for smoother, softer, refreshed skin.', 45, 70), ('Hot Stone Therapy', 'A warm stone massage experience designed for deep relaxation and comfort.', 75, 130); 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 spa_settings (spa_name, spa_email, spa_phone, spa_address, slot_interval_minutes, booking_notice_hours) values ('Serenity Spa Studio', 'hello@serenityspa.com', '+1 555 456 7890', '320 Wellness 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 spa_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 spa settings" on spa_settings for select to anon, authenticated using (true); create policy "Admins can manage spa settings" on spa_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 spa_settings ( id uuid primary key default gen_random_uuid(), spa_name text not null default 'Serenity Spa Studio', spa_email text, spa_phone text, spa_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 ('Relaxation Massage', 'A calming full-body massage designed to release tension and restore balance.', 60, 90), ('Deep Tissue Massage', 'Focused therapeutic massage for muscle tension, stress relief, and recovery.', 75, 120), ('Aromatherapy Massage', 'A soothing massage experience using essential oils for relaxation and wellness.', 60, 105), ('Signature Facial', 'A personalized facial treatment to cleanse, hydrate, and refresh the skin.', 60, 85), ('Body Scrub Treatment', 'A gentle exfoliating body treatment for smoother, softer, refreshed skin.', 45, 70), ('Hot Stone Therapy', 'A warm stone massage experience designed for deep relaxation and comfort.', 75, 130);

営業時間を登録する

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 spa_settings (spa_name, spa_email, spa_phone, spa_address, slot_interval_minutes, booking_notice_hours) values ('Serenity Spa Studio', 'hello@serenityspa.com', '+1 555 456 7890', '320 Wellness 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 spa_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 spa settings" on spa_settings for select to anon, authenticated using (true); create policy "Admins can manage spa settings" on spa_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 spa website with a real booking system and a secure admin dashboard. The final result should feel like it was designed by a top-tier design agency and built as a real production-ready product. Do not create a generic template. Do not create a basic admin panel. Do not make small visual improvements. Create a complete, polished, premium experience from the first version. Tech stack: - React - TypeScript - Vite - Supabase for database, backend, and auth ================================================ SUPABASE CONNECTION ================================================ Use these Supabase credentials: VITE_SUPABASE_URL=PASTE_YOUR_SUPABASE_URL_HERE VITE_SUPABASE_ANON_KEY=PASTE_YOUR_PUBLISHABLE_KEY_HERE Rules: - Use these values as environment variables - Do not hardcode them inside components - Create the Supabase client in src/lib/supabase.ts - Use import.meta.env.VITE_SUPABASE_URL and import.meta.env.VITE_SUPABASE_ANON_KEY ================================================ DATABASE SCHEMA ================================================ Use this exact schema. Do not rename fields or invent new ones. services: - id - name - description - duration_minutes - price - is_active - created_at appointments: - id - full_name - email - phone - service_id - appointment_date - start_time - end_time - status - notes - created_at business_hours: - id - weekday - is_open - start_time - end_time blocked_dates: - id - blocked_date - reason - created_at spa_settings: - id - spa_name - spa_email - spa_phone - spa_address - slot_interval_minutes - booking_notice_hours - created_at admin_users: - id - user_id - created_at Important: - Use spa_settings, not salon_settings - Use spa_settings, not barbershop_settings - Use spa_settings, not clinic_settings - Use spa_name, spa_email, spa_phone, and spa_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 spa booking website where visitors can: - view spa 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 spa owner can manage: - appointments - services - business hours - blocked dates - spa 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 - calming - modern - elegant - serene - warm - soft - refined - luxurious - trustworthy - polished - realistic for a premium local spa The dashboard should feel: - premium - clean - modern - product-like - organized - smooth - easy for a spa 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 spa visual style: - warm off-white and soft cream backgrounds - sage green, clay, sand, beige, champagne, stone, and soft gold accents - deep olive, warm charcoal, or espresso text - calm natural tones - refined borders - soft shadows - layered visuals - depth - subtle gradients - soft lighting - premium contrast - rounded polished cards - calm CTA buttons - tasteful wellness imagery or spa visual elements Use depth, gradients, lighting, and layered visuals where appropriate. Avoid flat backgrounds. Create calm contrast and clear hierarchy. Make the interface feel intentionally designed, not assembled from default components. Typography: - improve hierarchy and readability - make headings expressive, soft, and premium - use elegant, modern, readable typography - public website can use a refined display style for headings - dashboard should stay clean, readable, and product-like Layout: - improve spacing and composition - use dynamic, modern layouts - introduce tasteful asymmetry where appropriate - avoid overly rigid or boring sections - every section should feel intentionally designed Interactions: - add smooth animations and micro-interactions - enhance hover effects and transitions - make the experience feel polished and alive - keep interactions calm and elegant, not distracting ================================================ IMAGE AND VISUAL STORYTELLING REQUIREMENTS ================================================ The public website must use strong, high-quality, niche-specific spa 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, calming, trustworthy, and premium. Image style: - premium spa and wellness photography - soft natural lighting - warm contrast - cream, beige, sage, clay, stone, champagne, and soft gold tones - serene and refined - modern but not flashy - realistic and professional - clean composition - soft depth of field where appropriate - good cropping - consistent visual style across the website Good image subjects: - spa massage therapy - facial treatment - aromatherapy oils - hot stones - spa towels - candles - wellness products - peaceful treatment room - body scrub or skincare treatment - calm spa interior - close-up wellness craftsmanship shots Do not use: - barbershop imagery - hair salon imagery - dental or medical imagery - generic office imagery - random model portraits unrelated to spa/wellness - low-resolution images - awkward stock photos - broken image links - overly clinical medical treatment images 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 spa brand, improve trust, and make the section feel more premium. ================================================ BRAND DIRECTION ================================================ Use spa-specific language: - Spa - Wellness - Therapist - Client - Appointment - Service - Massage - Facial - Aromatherapy - Body Treatment - Relaxation - Rejuvenation - Book your treatment - Reserve your session Do not use: - barbershop - barber - haircut - fade - beard trim - shave - salon - stylist - clinic - patient - dental - dentist - doctor - medical - healthcare - teeth The website should feel like a premium spa brand, not: - a barbershop website - 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 spa_settings for spa name, email, phone, and address when available - Make the booking section polished and easy to follow - Use strong spa-specific imagery throughout the public website - The site should look like a real premium spa website, not a simple template ================================================ PUBLIC WEBSITE QUALITY EXPECTATIONS ================================================ Navbar: - refined and premium - calm brand presence - elegant spacing - polished booking CTA Hero: - visually striking and premium - must include a strong, relevant spa visual - use spa imagery such as massage therapy, spa interior, aromatherapy, towels, hot stones, facial treatment, or calm wellness visuals - use image overlays, soft 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, calming, 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: - Relaxation Massage: calm massage therapy visual - Deep Tissue Massage: therapist working on back or shoulder tension - Aromatherapy Massage: essential oils, candles, or calming treatment detail - Signature Facial: facial treatment or skincare visual - Body Scrub Treatment: spa towels, products, or exfoliation visual - Hot Stone Therapy: hot stones and spa treatment visual Keep service images consistent in crop, quality, and style. Do not use random unrelated beauty or medical images. About: - serene, warm, and intentional - visually balanced - should reinforce care, wellness, relaxation, trust, and premium service - include a strong spa-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 spa settings where relevant ================================================ BOOKING FLOW ================================================ Step 1: Select a spa 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 - spa_settings.slot_interval_minutes - spa_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. Spa 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. Spa Settings: Allow editing: - spa_name - spa_email - spa_phone - spa_address - slot_interval_minutes - booking_notice_hours Updated spa 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 - Spa settings editing working - Public website uses high-quality spa-specific imagery - Hero section includes a strong relevant spa visual - Services section includes relevant niche-specific visual treatment or images - About section includes authentic spa 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 spa 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 spa booking platform with a high-end public website, strong niche-specific imagery, and a polished admin dashboard.

Supabaseの環境変数を追加する

Google AI Studioから環境変数を聞かれたら、SupabaseのProject URLとPublishable Keyを入力します。

プロジェクトを改善・修正する（任意）

修正・改善用の追加プロンプト

プロンプト2：予約ロジックを調整する

既存のSupabaseスキーマをそのまま使い、公開予約のロジックを慎重に実装してください…

Implement the public booking logic very carefully using the existing Supabase schema exactly. ================================================ IMPORTANT ================================================ Do NOT invent, rename, or guess any field names. Use the real Supabase schema exactly as provided. Only use these fields: business_hours: - weekday - is_open - start_time - end_time blocked_dates: - blocked_date appointments: - appointment_date - start_time - end_time - status - service_id - full_name - email - phone - notes services: - id - duration_minutes - is_active spa_settings: - slot_interval_minutes - booking_notice_hours Do NOT use any alternative field names. ================================================ GOAL =============================================== Make the public booking logic fully stable, accurate, and production-style. When a user: - selects a service - selects a date the app must calculate real available time slots for that exact date. When a user submits the booking form: - the appointment must be inserted correctly into Supabase - the new appointment must use the exact schema - the selected slot must stop appearing as available ================================================ BOOKING LOGIC RULES ================================================ 1. The user selects a service 2. The user selects a date 3. The app calculates available slots for that exact date 4. Slots must be generated only inside business hours 5. Slots must respect the selected service duration 6. Slots must respect spa_settings.slot_interval_minutes 7. Slots must be excluded if the selected date exists in blocked_dates 8. Slots must be excluded if they overlap with existing appointments 9. Appointments with status = "cancelled" must NOT block slots 10. Slots that violate spa_settings.booking_notice_hours must be excluded 11. Only active services should be bookable 12. New appointments must be inserted with status = "pending" ================================================ OVERLAP RULE ================================================ A new slot conflicts if: new_start < existing_end AND new_end > existing_start Use this exact overlap rule consistently everywhere. ================================================ SLOT STRUCTURE (VERY IMPORTANT) ================================================ Normalize all generated available slots into this exact frontend shape: { start: Date, end: Date, label: string } Requirements: - start must be a real Date object - end must be a real Date object - label is for display only - use label directly in the UI - avoid rebuilding labels repeatedly during render ================================================ TIME SAFETY RULES (PREVENT CRASHES) ================================================ - Only call format(...) on real Date objects - Never pass invalid strings into parseISO or format - Never use literal strings like "yyyy-MM-ddT10:30:00" - Always combine the real selected date with the time correctly - Do not rely on unsafe manual string formatting for dates ================================================ STATE RULES ================================================ - selectedService must exist before calculating slots - selectedDate must exist before calculating slots - recalculate available slots whenever selectedService changes - recalculate available slots whenever selectedDate changes - reset availableSlots when selectedService changes - reset selectedTime when service changes - reset selectedTime when date changes - do not calculate slots if required inputs are missing ================================================ BOOKING INSERT RULES ================================================ When creating a new appointment, insert using the exact schema: - full_name - email - phone - service_id - appointment_date - start_time - end_time - status - notes Requirements: - service_id must come from the selected service - appointment_date must match the selected date - start_time and end_time must come from the selected normalized slot - status must be "pending" - notes can be null or the provided optional notes ================================================ ERROR SAFETY ================================================ Add robust error protection: - if slot generation fails, log the real reason clearly - do not crash the whole component - return a safe empty state if calculation fails - render a fallback "No availability" message if no slots exist - if booking insert fails, show a clear user-friendly error message - if booking succeeds, move safely to the success state ================================================ FINAL RESULT ================================================ The final public booking logic should: - use the exact Supabase schema - generate correct real available slots - prevent overlapping bookings - ignore cancelled bookings - respect blocked dates - respect notice period rules - avoid "Invalid time value" errors - avoid UI crashes - insert appointments correctly - remove newly booked slots from availability - behave like a real production booking system

プロンプト3：管理ダッシュボードを作る

既存のSupabaseスキーマをそのまま使って管理ダッシュボードを作ってください…

Build the admin dashboard using the existing Supabase schema exactly. ================================================ IMPORTANT ================================================ Do NOT rename any fields. Do NOT invent any alternative field names. Do NOT create fake local-only dashboard data. Use Supabase as the single source of truth. This prompt is for the admin dashboard only. The admin dashboard must work with the existing project structure and existing public booking flow. ================================================ STRICT SCHEMA USAGE ================================================ Use only the real schema fields below. appointments: - id - full_name - email - phone - service_id - appointment_date - start_time - end_time - status - notes - created_at services: - id - name - description - duration_minutes - price - is_active - created_at business_hours: - weekday - is_open - start_time - end_time blocked_dates: - blocked_date - reason spa_settings: - spa_name - spa_email - spa_phone - spa_address - slot_interval_minutes - booking_notice_hours Do NOT use any alternative field names. ================================================ GOAL ================================================ Create a real production-style admin dashboard for managing the business. The dashboard must manage: - appointments - services - business hours - blocked dates - settings The dashboard should use Supabase as the source of truth for all reads and writes. ================================================ ACCESS AND SECURITY ================================================ The admin dashboard must be treated as a protected admin area. Requirements: - non-admin users must not be able to access admin dashboard actions - dashboard reads and writes must respect the existing project security setup - do not bypass Supabase security rules - do not use fake client-side admin protection only ================================================ DASHBOARD SECTIONS ================================================ 1. Dashboard Overview 2. Appointments 3. Services 4. Business Hours 5. Blocked Dates 6. Spa Settings ================================================ 1. DASHBOARD OVERVIEW ================================================ Show real data from Supabase for: - today's appointments - pending requests - upcoming confirmed appointments - completed appointments Use live calculated data, not placeholder metrics. ================================================ 2. APPOINTMENTS ================================================ Requirements: - list all appointments - show: - customer full_name - email - phone - service name - appointment date - appointment time - status - notes - allow filtering by: - status - date - allow changing status to: - pending - confirmed - cancelled - completed Important: - status changes must update Supabase immediately - the UI must reflect the updated status clearly - use the real service relationship to display service name - keep the appointments list in sync after status changes - do not show stale records after updates ================================================ 3. SERVICES =============================================== Requirements: - list services - create service - edit service - delete service - toggle active / inactive Use these fields: - name - description - duration_minutes - price - is_active Important: - when a new service is added in the dashboard, it must appear automatically in the public booking page if is_active = true - when is_active = false, it should not appear in the public booking flow - service updates must be reflected in the UI immediately - delete behavior must update the UI safely after success ================================================ 4. BUSINESS HOURS ================================================ Allow editing weekday rows using: - weekday - is_open - start_time - end_time Important: - business hours changes must affect booking availability correctly - do not invent different field names - saving business hours must update Supabase correctly - the UI must refresh safely after updates ================================================ 5. BLOCKED DATES ================================================ Allow: - create blocked date - delete blocked date Use: - blocked_date - reason Important: - blocked dates must affect booking availability correctly - blocked date changes must update Supabase correctly - the UI must stay in sync after create or delete ================================================ 6. SPA SETTINGS ================================================ Allow editing: - spa_name - spa_email - spa_phone - spa_address - slot_interval_minutes - booking_notice_hours Important: - settings changes must update Supabase correctly - booking-related settings should affect booking logic correctly - the settings form should load real current values from Supabase ================================================ DATA RULES ================================================ - Supabase is the single source of truth - no fake data - no local-only dashboard records - no schema guessing - use real inserts, updates, deletes, and reads - use safe re-fetching or state synchronization after mutations - avoid stale UI after create / update / delete operations ================================================ UI / BEHAVIOR REQUIREMENTS ================================================ - dashboard must feel structured, clean, and production-style - tables must be readable - forms must be clear - status controls must be understandable - destructive actions must be handled carefully - updates must be reflected in the UI after mutation - avoid stale data after create / update / delete operations - include loading states where needed - include empty states where needed - include simple error states where needed ================================================ FINAL RESULT ================================================ The final admin dashboard should: - use the exact Supabase schema - manage all core clinic data - update Supabase correctly - reflect updates in the UI - show real appointments and services - affect the public booking flow correctly - respect the existing admin security setup - behave like a real production admin dashboard

プロンプト4：QAと安定化を実行する

プロジェクト全体について、整合性・QA・安定性・セキュリティ面の総点検を行ってください…

Do a full consistency, QA, stabilization, and security-aware validation pass across the entire project. ================================================ GOAL ================================================ Verify that the whole app is stable, clean, consistent with the real Supabase schema, aware of the existing security setup, and ready for real use. The result should be: - stable - production-style - schema-consistent - security-aware - free from obvious logic and formatting bugs ================================================ IMPORTANT ================================================ Check everything against the real Supabase schema only. Do NOT invent or rename fields. Do NOT leave mismatched schema references. Do NOT leave obvious placeholder bugs. Do NOT bypass the existing Supabase security setup. ================================================ STRICT SCHEMA VALIDATION ================================================ Verify all code uses the real schema exactly. services: - id - name - description - duration_minutes - price - is_active - created_at appointments: - id - full_name - email - phone - service_id - appointment_date - start_time - end_time - status - notes - created_at business_hours: - weekday - is_open - start_time - end_time blocked_dates: - blocked_date - reason spa_settings: - spa_name - spa_email - spa_phone - spa_address - slot_interval_minutes - booking_notice_hours ================================================ REMOVE INVALID FIELD REFERENCES ================================================ Search the entire codebase and remove any incorrect references to: - day_of_week - open_time - close_time - date (when blocked_date should be used) - customer_name - customer_email - customer_phone Only the real field names should remain. ================================================ BOOKING FLOW QA ================================================ Verify the full booking flow works end-to-end: 1. choose service 2. choose date 3. available times appear correctly 4. choose time 5. submit appointment 6. appointment is inserted into Supabase 7. booked slot disappears from availability 8. overlapping bookings are prevented 9. cancelled bookings do not block availability Also verify: - blocked dates prevent booking correctly - business hours affect availability correctly

プロジェクトをGitHubに保存する

Hostingerでデプロイする

Hostingerを開く

動画と同じ構成でこのプロジェクトを公開します。

RECOMMENDED

https://www.hostg.xyz/SHJK3

Node.js Webアプリを作成する

GitHubリポジトリをインポートする

必要な環境変数を追加する

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