Claude Codeで美容サロンの予約サイトを作る

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

美容サロンの予約サイト

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

ヘアサロンの予約サイト

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

スパの予約サイト

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

コーチングの予約サイト

レストラン予約サイト

美容サロンの予約サイト

マッサージの予約サイト

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

写真撮影の予約サイト

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

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

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

ダンス教室の予約サイト

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

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

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

理学療法の予約サイト

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

自動車整備の予約サイト

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

住宅修繕の予約サイト

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

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

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

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

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

家庭教師の予約サイト

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

内見予約サイト

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

予約フローのプレビュー

- サービスを選択

- 日付を選択

- 時間を選択

- 予約を確定する

受け取ったお客様情報

- 氏名

- メールアドレス

- 電話番号

- 備考（任意）

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

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

Supabaseを開く

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

セットアップ用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 business_settings ( id uuid primary key default gen_random_uuid(), business_name text not null default 'Elegance Beauty Salon', business_email text, business_phone text, business_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 ('Signature Facial', 'Treat your skin with our signature deep cleansing and hydration facial.', 60, 85), ('Full Makeup Session', 'Professional makeup application for any special occasion or event.', 45, 65), ('Brow Shaping & Tint', 'Expert brow shaping combined with a custom tint for a polished look.', 30, 40), ('Lash Lift & Tint', 'Lift and darken your natural lashes for a beautiful, effortless look.', 60, 75), ('Bridal Consultation', 'A specialized consultation to plan your perfect bridal beauty look.', 45, 50); 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', '16:00'); insert into business_settings (business_name, business_email, business_phone, business_address, slot_interval_minutes, booking_notice_hours) values ('Lumina Beauty Studio', 'hello@luminabeauty.com', '+1 555 123 4567', '123 Elegance St, Beverly Hills, CA', 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 business_settings enable row level security; create policy "Anyone can read active services" on services for select to anon, authenticated using (is_active = true); create policy "Admins can manage services" on services for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can create appointments" on appointments for insert to anon, authenticated with check (true); create policy "Admins can read appointments" on appointments for select to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Admins can update appointments" on appointments for update to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can read business hours" on business_hours for select to anon, authenticated using (true); create policy "Admins can manage business hours" on business_hours for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can read blocked dates" on blocked_dates for select to anon, authenticated using (true); create policy "Admins can manage blocked dates" on blocked_dates for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Anyone can read settings" on business_settings for select to anon, authenticated using (true); create policy "Admins can manage settings" on business_settings for all to authenticated using ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ) with check ( exists ( select 1 from admin_users where admin_users.user_id = auth.uid() ) ); create policy "Users can read their own admin row" on admin_users for select to authenticated using (auth.uid() = user_id); insert into admin_users (user_id) values ('PASTE_YOUR_AUTH_USER_ID_HERE');

管理者ユーザーID

Supabaseの認証ユーザーIDを入力

プロンプト1 — 美容サロンの予約サイト

プロンプト1 — 美容サロンの予約サイト

あなたは世界トップクラスのフルスタック開発者であり、クリエイティブディレクター、UI/UXデザイナーです…

You are a world-class full-stack product builder, creative director, and UI/UX designer. Build a premium modern beauty salon website with a real booking system and a secure admin dashboard. The final result should feel like it was designed by a top-tier beauty and lifestyle 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 beauty salon booking experience from the first version. Tech stack: - React - TypeScript - Vite - Supabase for database, backend, and auth ================================================ SUPABASE CONNECTION ================================================ Create a .env.local file in your project root with your Supabase credentials: VITE_SUPABASE_URL=PASTE_YOUR_SUPABASE_URL_HERE VITE_SUPABASE_ANON_KEY=PASTE_YOUR_PUBLISHABLE_KEY_HERE Rules: - Use these values as environment variables - Do not hardcode them inside components - Create the Supabase client in src/lib/supabase.ts - Use import.meta.env.VITE_SUPABASE_URL and import.meta.env.VITE_SUPABASE_ANON_KEY - Use the official Supabase client with normal browser session persistence - Do not manually clear or remove the Supabase session - Do not sign the admin out automatically unless the user clicks a sign out button ================================================ DATABASE SCHEMA ================================================ Use this exact schema. Do not rename fields or invent new ones. services: - id - name - description - duration_minutes - price - is_active - created_at appointments: - id - full_name - email - phone - service_id - appointment_date - start_time - end_time - status - notes - created_at business_hours: - id - weekday - is_open - start_time - end_time blocked_dates: - id - blocked_date - reason - created_at business_settings: - id - business_name - business_email - business_phone - business_address - slot_interval_minutes - booking_notice_hours - created_at admin_users: - id - user_id - created_at Important: - Use business_settings for salon business information. - Use business_name, business_email, business_phone, and business_address. - Do not use clinic_settings. - Do not use clinic_name, clinic_email, clinic_phone, or clinic_address. - Do not use salon_settings. - Do not use salon_name, salon_email, salon_phone, or salon_address. - Do not use dental_settings. - Do not use barbershop_settings. - Do not use spa_settings. - Do not use trainer_settings. - Do not use coaching_settings. - Do not rename any table or field. - Use admin_users.user_id to check admin access. - Do not check admin access by email. - Do not check admin_users.id for authorization. - Do not use fake local authentication. - Do not use fake local data. ================================================ PROJECT GOAL ================================================ Create a complete beauty salon booking website where visitors can: - view beauty services - select a service - select a date - see available time slots - enter their details - submit a real appointment request - see a success confirmation Create a secure admin dashboard where the salon owner or beauty studio manager can manage: - appointments - services - business hours - blocked dates - business settings Everything in the dashboard should be useful and editable, not just displayed. ================================================ CREATIVE DIRECTION ================================================ This project must look premium from the first version. Think like a world-class beauty and lifestyle creative director. The public website should feel: - premium - modern - elegant - soft - polished - calm - refined - stylish - trustworthy - professional - client-friendly - realistic for a premium local beauty salon The dashboard should feel: - premium - clean - modern - product-like - organized - smooth - easy for a salon manager to use - visually polished, not basic Design quality expectations: - Avoid generic or template-like design - Avoid flat and empty layouts - Avoid boring sections - Avoid weak spacing - Avoid basic AI-generated landing page patterns - Do not make the public website look like a simple template - Do not make the admin dashboard look like a basic starter dashboard - Keep the design beauty-focused, elegant, premium, and professional - Do not make it look like a dental clinic, hospital, restaurant, gym, coaching website, or generic SaaS landing page ================================================ VISUAL DESIGN SYSTEM ================================================ Use a premium beauty salon visual style: - soft ivory, warm white, blush, champagne, nude, beige, rose, and soft taupe backgrounds - refined rose-gold, muted pink, soft plum, warm brown, and elegant neutral accents - deep charcoal or espresso text - elegant beauty-inspired contrast - polished service cards - refined borders - soft shadows - layered visuals - subtle gradients - soft lighting effects - calm depth - premium buttons - elegant icons - high-quality beauty salon imagery Use depth, gradients, lighting, and layered visuals where appropriate. Avoid flat backgrounds. Create clear contrast and strong hierarchy. Make the interface feel intentionally designed, not assembled from default components. Typography: - improve hierarchy and readability - make headings strong, elegant, premium, and trustworthy - use modern, elegant, readable typography - avoid overly decorative fonts - dashboard should stay clean, readable, and product-like Layout: - improve spacing and composition - use modern section layouts - introduce tasteful asymmetry where appropriate - avoid rigid boring sections - every section should feel intentionally designed Interactions: - add smooth animations and micro-interactions - enhance hover effects and transitions - make the experience feel polished and alive - keep interactions calm and elegant, not distracting ================================================ IMAGE AND VISUAL STORYTELLING REQUIREMENTS ================================================ The public website must use strong, high-quality, niche-specific beauty salon 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, elegant, and premium. Image style: - premium beauty salon photography - clean modern beauty studio environment - soft natural or studio lighting - calm professional mood - elegant treatment room - professional makeup session - brow or lash service shown tastefully - polished hair styling moment - beauty consultation - client-friendly atmosphere - refined and realistic - good cropping - consistent visual style across the website Good image subjects: - modern beauty salon interior - beauty professional consulting with a client - makeup artist working with a client - elegant salon treatment room - brow or lash styling scene - refined beauty tools shown tastefully - salon reception or waiting area - polished hair styling moment - calm beauty consultation - premium vanity or beauty product details Do not use: - dental imagery - dentist imagery - medical clinic imagery - hospital imagery - graphic skin procedure imagery - uncomfortable treatment closeups - barbershop imagery - restaurant imagery - fitness imagery - coaching imagery - low-resolution images - awkward stock photos - broken image links - random model portraits unrelated to beauty services Implementation: - Use reliable external image URLs if needed. - Prefer high-quality Unsplash-style imagery or other stable image sources. - Make sure image links actually load. - Use descriptive alt text. - Use object-fit: cover and intentional cropping. - Keep the layout responsive. - If an image fails, the layout should still look good. - Keep images easy to replace later by storing image URLs in a clear data structure, config object, or component-level constants. Every image should support the beauty salon brand, improve trust, and make the section feel more premium. ================================================ BRAND DIRECTION ================================================ Use beauty salon-specific language: - Beauty Salon - Beauty Studio - Beauty Services - Client - Appointment - Service - Facial - Makeup - Brow Shaping - Lash Lift - Hair Styling - Bridal Beauty - Beauty Consultation - Personal Care - Professional Beauty - Book your appointment - Schedule your visit - Reserve your beauty session Do not use: - dental - dentist - dental care - patient - oral health - checkup - teeth cleaning - filling - tooth - medical - healthcare - coaching - trainer - workout - barbershop - barber - restaurant - reservation - table Avoid unrealistic beauty claims. Do not promise guaranteed results. Do not use manipulative or insecurity-based messaging. Focus on confidence, care, elegance, relaxation, personal attention, professional service, and a polished client experience. ================================================ PUBLIC WEBSITE ================================================ Create: - Navbar - Hero section - Services section - About section - Booking section - Success confirmation screen - Footer Public website requirements: - Load real services from the services table. - Only show active services on the public website. - Use business_settings for salon name, email, phone, and address when available. - Use business_name as the salon name. - Use business_email as the salon email. - Use business_phone as the salon phone. - Use business_address as the salon address. - Make the booking section polished and easy to follow. - Use strong beauty salon-specific imagery throughout the public website. - The site should look like a real premium beauty salon website, not a simple template. ================================================ PUBLIC WEBSITE QUALITY EXPECTATIONS ================================================ Navbar: - refined and premium - clean beauty studio brand presence - elegant spacing - polished booking CTA Hero: - visually striking and premium - must include a strong, relevant beauty salon visual - use imagery such as modern salon interior, beauty consultation, makeup session, elegant treatment room, or refined beauty studio atmosphere - use image overlays, gradients, lighting, or layered composition for depth - maintain strong text readability - strong headline hierarchy - calm and elegant supporting text - polished CTA buttons - not generic - not flat - not basic Services: - should not look like a plain list - make services feel premium, elegant, clean, and visually engaging - use strong layout, refined typography, beautiful spacing, and polished cards or premium list design - include relevant visual treatment for services - service cards should include niche-relevant images or image areas where appropriate - show service name, description, duration, price, and booking affordance - services should be dynamic from Supabase Suggested image direction for services: - Signature Facial: calm facial treatment or elegant treatment room - Makeup Session: makeup artist working with a client - Brow Shaping: refined brow styling or beauty tools - Lash Lift: elegant lash or beauty detail, not uncomfortable - Hair Styling: polished hair styling moment - Bridal Beauty Consultation: elegant bridal beauty mood or consultation setting Keep service images consistent in crop, quality, and style. Do not use medical, dental, or uncomfortable procedure images. About: - calm, elegant, professional, and intentional - visually balanced - should reinforce trust, care, experience, cleanliness, personal attention, and professional beauty service - include a strong beauty salon-related image or layered visual - avoid awkward empty layouts Booking: - polished and product-like - easy to follow - clear steps - strong selected states - premium time slot UI - clean client details form - clear appointment summary - elegant success state - may include subtle supporting imagery or visual accents, but do not make the booking form harder to use Footer: - refined - premium - consistent with the brand - use business_settings where relevant ================================================ BOOKING FLOW ================================================ Step 1: Select a beauty service Step 2: Select a date and available time Step 3: Enter: - full name - email - phone - optional notes Step 4: Show a success confirmation with appointment summary Booking UI should include: - clear step indicator - nice selected states - clean date selection - polished time slots - appointment summary - strong CTA buttons Use client-focused language in the booking flow. Do not use patient-focused language. ================================================ AVAILABILITY LOGIC ================================================ Available time slots must be generated using: - business_hours - services.duration_minutes - business_settings.slot_interval_minutes - business_settings.booking_notice_hours - blocked_dates - existing appointments Rules: - Only show slots inside working hours - Skip blocked dates - Skip overlapping appointments - Ignore cancelled appointments - Respect booking notice time - Use the selected service duration to calculate end_time - New active services added from the dashboard must work in the booking flow Overlap rule: new_start < existing_end AND new_end > existing_start All slots should be normalized as: { start: Date, end: Date, label: string } Time safety: - Only format real Date objects - Never pass invalid strings to format() - Never use strings like "yyyy-MM-ddT10:30:00" - Always combine the selected date and time correctly - Save appointment_date as a Supabase-compatible date - Save start_time and end_time as Supabase-compatible time values Important booking insert rule: - When creating an appointment, do not use .insert(...).select() or .insert(...).select().single(). - Public users are allowed to insert appointments, but they are not allowed to read all appointments. - Use insert only, then show the success screen from the local booking data already available in the form. - Do not add a public SELECT policy for appointments. - Do not insert id manually. - Do not insert created_at manually. - service_id must be the selected service id from the services table. ================================================ ADMIN AUTH ================================================ Create a real admin login using Supabase Auth. Admin login flow: 1. Admin enters email and password. 2. Sign in with supabase.auth.signInWithPassword(). 3. If login fails, show a clear error message. 4. After successful sign in, get the authenticated user. 5. Use the authenticated user's id. 6. Check if user.id exists in admin_users.user_id. 7. If the user exists in admin_users, allow access to dashboard. 8. If the user is authenticated but not found in admin_users, show: "You are signed in, but you are not authorized as an admin." 9. Add a loading state while checking session and admin access. 10. Do not redirect back to login before the admin check finishes. Important admin session rules: - On admin route load, call supabase.auth.getSession(). - If there is no session, stop loading and show the login form. - If there is a session, get the current user with supabase.auth.getUser(). - Query admin_users where user_id equals user.id. - Use maybeSingle(), not single(), when checking admin_users. - If a matching row exists, set isAdmin to true and show the dashboard. - If no matching row exists, set isAdmin to false and show the unauthorized message. - Always stop the loading state in a finally block. - The UI must never stay stuck on "Verifying access..." forever. - Use supabase.auth.onAuthStateChange to respond to sign in, sign out, token refresh, and session changes. - Do not sign the admin out automatically because of a temporary query error. - Do not clear local storage or remove the Supabase session manually. - Keep the admin logged in as long as Supabase has a valid session. - If a token refresh event happens, keep the dashboard available and re-check admin access if needed. Rules: - Protect all admin routes. - Public website should stay accessible without login. - Do not check admin access by email. - Do not check admin_users.id. - Do not use fake local authentication. - Do not rely only on hiding buttons. - Do not use business_settings for admin authentication. - Do not use services or appointments for admin authentication. - Admin access is only controlled by admin_users.user_id. Important: - The admin_users table contains user_id values from Supabase Auth. - The login email and password belong to a Supabase Auth user. - After login, always compare auth.user.id with admin_users.user_id. - Do not compare user.email with anything in admin_users. ================================================ ADMIN DASHBOARD ================================================ Create a complete dashboard with these pages: 1. Overview 2. Appointments 3. Services 4. Business Hours 5. Blocked Dates 6. Business Settings The dashboard must feel like a polished premium product dashboard, not a basic admin template. Dashboard visual requirements: - refined sidebar - polished page headers - beautiful cards - clean tables - premium forms - clear modals or drawers - elegant buttons - refined badges - smooth hover states - good empty states - strong spacing and hierarchy - consistent design system 1. Overview: - show useful stats - upcoming appointments - pending appointments - completed appointments - active services - use polished metric cards and useful layout 2. Appointments: - show all appointments from Supabase - show client name, service, date, time, phone, email, status, and notes - allow filtering by status - allow updating status: - pending - confirmed - cancelled - completed - make appointment tables/cards clean, readable, and premium 3. Services: This page must be fully manageable, not read-only. The admin must be able to: - add new services - edit existing services - activate services - deactivate services Each service row should have clear actions. Service fields: - name - description - duration_minutes - price - is_active Important: - Existing services must have an Edit action. - Editing should open a polished pre-filled form, modal, drawer, or panel. - Saving should update the service in Supabase. - Inactive services should stay visible in the admin dashboard. - Inactive services should not appear on the public booking page. - Prefer deactivate instead of hard delete because appointments can reference services. - New or updated active services must appear automatically in the booking flow. 4. Business Hours: - allow editing each weekday - allow open/closed days - allow editing start_time and end_time - changes must affect available booking slots - make the editor clear and easy to use 5. Blocked Dates: - allow adding blocked dates - allow removing blocked dates - show reason - blocked dates must prevent bookings - make the interface simple and polished 6. Business Settings: Allow editing: - business_name - business_email - business_phone - business_address - slot_interval_minutes - booking_notice_hours In the UI, these fields can be labeled as: - Salon Name - Salon Email - Salon Phone - Salon Address - Slot Interval - Booking Notice Important: - Save updates back to business_settings. - Updated business settings should appear on the public website where relevant. ================================================ QUALITY REQUIREMENTS ================================================ - Full working app - Clean code structure - Supabase fully connected - Booking flow working - Appointment insert works without requiring public appointment read access - Admin login working - Admin session handling working - Admin verification never gets stuck forever - Protected dashboard working - Services management fully working - Appointments management working - Business hours editing working - Blocked dates working - Business settings editing working using business_settings - Public website uses high-quality beauty salon-specific imagery - Hero section includes a strong relevant beauty salon visual - Services section includes relevant niche-specific visual treatment or images - About section includes authentic beauty salon 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 beauty salon visual direction from the start - Public website should feel top-tier, not template-like - Dashboard should feel like a polished premium product - Admin auth must work using Supabase Auth user.id and admin_users.user_id - Keep functionality and visual quality strong from the first version FINAL RESULT: Create a complete, working, premium beauty salon booking platform with a high-end public website, strong niche-specific imagery, working admin login, stable session handling, real appointment booking, and a polished admin dashboard.

任意：用意されたプロジェクトから始める

美容サロンの予約サイト

用意されたプロジェクトで手早く始める

PROJECT

https://profitstudio.app/template/beauty-salon-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 Webアプリを作成して、ドメインを選びます。

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