أنشئ موقع حجز فاخرًا باستخدام Claude Code

Claude Desktop

يبني Claude Code موقعك في التطبيق المكتبي. البناء الكامل جلسة طويلة، لذا استخدم باقة Claude مدفوعة فيها متسع كافٍ.

نزّل Claude Desktop

https://claude.ai/download

Node.js

نزّل إصدار LTS. يستخدمه Claude لبناء موقعك وفحصه.

نزّل Node.js

https://nodejs.org/en/download

حساب GitHub

مجاني. تُحفظ شيفرة موقعك هنا، ومنه ينشر Hostinger موقعك.

أنشئ حساب GitHub

https://github.com/signup

حساب Supabase

الباقة المجانية تكفي. وهي تسمح بمشروعين نشطين — إذا كان لديك مشروعان بالفعل، فأوقف مؤقتًا مشروعًا لا تستخدمه. تحفظ خدماتك وساعات العمل والحجوزات وتسجيل دخولك إلى لوحة التحكم.

أنشئ حساب Supabase

https://supabase.link/r4gdwhi

حساب Resend

ترسل الباقة المجانية 100 رسالة في اليوم و3,000 في الشهر. ويرسل كل حجز عدة رسائل: الرمز، واستلام الطلب، وتنبيهك، والتأكيد.

أنشئ حساب Resend

https://resend.com/signup

نطاقك الخاص

يعمل موقعك عليه، ومنه تُرسل رسائل الحجز. لا يمكن لعنوان مجاني مثل Gmail إرسالها. هل ستشتري النطاق مع باقة Hostinger؟ احصل على الباقة قبل الخطوة 3.

استضافة Hostinger

تحتاج إلى الاستضافة في الخطوة 5، عندما يصبح موقعك مباشرًا.

اختر باقة Hostinger

استخدم باقة Business (Unlimited) أو باقة Cloud — فهما وحدهما تشغّلان Node.js Web Apps: حتى 5 على Business و10 على Cloud.

اختر نوع نشاطك التجاري

دورك. Booking Engine هو نفسه للأنواع الثلاثة — أما التصميم والنصوص والخدمات النموذجية فمصمَّمة للنوع الذي تختاره.

ما نوع نشاطك التجاري؟

صالون شعر

قص وصبغ وتصفيف، مع خدمات الصالون الجاهزة في المحرك.

Build a complete, premium booking website for **{{BUSINESS_NAME}}**, a hair salon in {{CITY}}, in this empty folder. The booking system is an installed package — the **Profit Studio Booking Engine**. It owns availability, bookings, booking emails and the owner's dashboard. You design and build the public website around it, and nothing the engine provides. ## 1. Set up 1. Scaffold a Vite + React + TypeScript app **in the current folder**: `npm create vite@latest . -- --template react-ts --no-interactive`, then `npm install`. create-vite stops without an error when the folder is not empty — a `.DS_Store` or a `.claude/` folder is enough — so check that `package.json` now exists. If it does not, scaffold into a new subfolder the same way, move all of its files (dotfiles included) up into this folder without overwriting or deleting anything already here, and remove the empty subfolder. Remove the template's demo content. 2. `npm install --save-exact @profitstudio/booking-engine@2.0.0-beta.1`, then `npx booking-engine init --preset hair-salon`. 3. Read `node_modules/@profitstudio/booking-engine/docs/BUILD-A-SITE.md` once: it has every file to wire, the booking API and the error table. Open `docs/INTEGRATION.md` only at a section it names, and nothing else in the package. 4. Wire the engine as BUILD-A-SITE §1 shows, with the engine's `hairSalonPreset` as `preview.preset`; in `preview.business` use `{{BUSINESS_NAME}}`, the time zone `{{TIMEZONE}}` and a plausible placeholder `contact` in {{CITY}}. The dashboard on `/admin/` mounts `<BookingAdmin engine={engine} siteUrl="/" content={siteContent} />` and gets only your brand accent (light and dark) in `src/admin-theme.css`. One public page (sections and an in-page booking flow), no client-side routes. No backend yet: no Supabase project, no `supabase` commands, no `.env.local` — the site runs in preview mode with a visible “Preview — sample data, bookings are not saved” banner. ## 2. Design — the creative part Make it feel like a real, distinctive hair salon, not a template: - **Style direction:** {{STYLE_DIRECTION}} - **Audience:** Local clients, mostly 25–55, booking cuts, color and styling — most of them on a phone, often in a hurry. - **Tone:** Confident, warm and expert. Never clinical, never luxury cliché. - **Sections:** - Hero with the salon's personality and one clear “Book an appointment” action - Services and prices loaded from the engine (duration, price, “from” prices), grouped sensibly — with the owner's optional service photos (cut, colour, styling work) shown in the site's own style when a service has one, and a complete typeset menu without them - The team / stylists — placeholder bios and names the owner will edit, clearly marked - The salon space and approach (what makes this salon different) - Testimonials — clearly marked as placeholder examples, never presented as real reviews - Opening hours (from the engine) and location / contact (from the engine's business contact) - The booking flow - Footer with a discreet “Staff login” link to /admin/ - **Booking experience:** - Service first, then the date and time together, then details, then the email code, then confirmation - A real month calendar with month and year navigation that shows each day's status from the engine — open, only a few times left, fully booked, closed or past — loaded with one getAvailability call per visible month (INTEGRATION.md §8 and the calendar helpers in §9); on phones a week strip with the same statuses and a “Month” view - Times grouped as Morning / Afternoon / Evening (a segmented switch with counts when there are many); the chosen time continues inline (“1:30 PM — Continue”), and a “soonest time” shortcut comes from data already loaded - Keep the chosen service, duration, price, date and time visible at every step — a summary beside the calendar on wide screens, a sticky bar on phones - The code step feels like part of the salon's flow: the masked address the code went to, one large code field, “Send a new code”, “Choose another time”, and a reminder to check spam - Designed states, not error dumps: times loading, times that could not load (Try again), a time just taken by someone else (fresh times), a fully booked day (the next available day), a closed day, and online booking switched off (contact details) - Pending wording: “Request received — we'll confirm your appointment shortly.” Confirmed wording: “You're booked.” - **Imagery:** Real, coherent photography is part of the design, not an extra: the hero, the salon space, details of the work (hands, tools, colour, texture) and the storefront, all in one photographic direction. Show hair and craft, never posed stock smiles. Never present a photographed person as one of the salon's stylists: sample team cards show work, not faces, and stay labelled as samples until the owner adds real portraits. Motifs (scissor, comb, hair-texture curves) frame the photos; they do not replace them. Service photos are the owner's (added per service in the dashboard): present them as part of the menu's design, never as stock fillers. - **Avoid:** - A generic SaaS landing page look, purple gradients, glassmorphism everywhere - Invented awards, certifications, review counts or ratings - Medical or clinical styling - Hard-coded services, prices or opening hours (they come from the engine) - **Words:** call customers “clients” and bookings “appointments”. How: - **Identity first.** A short `DESIGN.md`: the concept in one sentence, a display face with character and a readable text face (both self-hosted with `@fontsource`), colour tokens with every text/background pair at 4.5:1 or better, a type and spacing scale, how motion behaves. Every value lives in one CSS file of custom properties. Two businesses in this niche with different style directions must not look like the same layout recoloured. Plain CSS, no UI kit. - **Composition.** Varied rhythm — full-bleed moments, asymmetric grids, one focal point per screen; designed for phones first, from 320 px to wide screens; keyboard-accessible with visible focus; motion of 150–600 ms with a purpose, off under `prefers-reduced-motion`. - **Engine data, never hard-coded:** services, prices, opening hours, contact details and availability (BUILD-A-SITE §3). “Open now” lines come from `getOpeningTimes`. Show each service's optional `image` in your own style when it has one, and make the services section complete with none. - **Owner-editable copy.** Declare the texts, photos, logo, brand colours and heading style the owner may change in `src/content/site.ts` (BUILD-A-SITE §2), with your copy and photos as defaults, render the page from it as text, and bake it in with the Vite plugin. - **Photos.** Free, properly licensed photographs (Unsplash or Pexels licence), at most six, downloaded into `photos/source/` and recorded in `PHOTOS.md` — never hot-linked, never a photographed person presented as staff (sample team cards show the work and say “Sample photo”; content-list images cannot have defaults, so sample cards may be text-only or share one site image). Search terms that work: “hair salon interior”, “hairdresser cutting hair close up”, “hair colour bowl brush”, “salon chair mirror”. Prepare them with `npx booking-engine photos` (BUILD-A-SITE §5): AVIF + WebP at two or three widths, `width`/`height` on every `<img>`, fixed `aspect-ratio` frames with `object-fit: cover`, the hero eager with `fetchpriority="high"`, everything else lazy. When no fitting photo exists, design the frame without one. - **The booking flow** follows BUILD-A-SITE §4 with the calendar helpers: server slots only, the business time zone, the two steps (`requestBooking`, then the code and `verifyBooking`), every error in the table, contact details when online booking is off, success only after `verifyBooking` returned `ok: true`. On a phone: the step's name always visible, the choice and price in view, 44 px targets, the right input types, inline validation, a loading state on the control that waits, a code field that accepts a pasted code, focus on each new step's heading. - **Every “Book” button always answers.** Whatever the booking section is showing — loading, the flow, online booking off, no services, a calendar that failed to load — each Book/CTA button on the page scrolls to the booking section and moves focus to its heading, so the visitor sees that state's message and the shop's contact details. Never route a CTA only through the flow component (it is not on the page in those states), and never leave a click that does nothing. Check it with online booking off as well as on. ## 3. Work efficiently The viewer's Claude plan pays for every step, so keep the session lean: - Read BUILD-A-SITE.md once; don't re-read files you wrote or explore the package. - Photos: start from the leads above or spend at most about ten minutes searching; judge candidates on one contact sheet of small thumbnails, not one by one at full size. - Screenshots: about eight in all — desktop and a 390 px phone (device emulation), downscaled to at most 1280 px wide. Don't capture very long pages at full resolution. - Don't simulate the engine's error answers to see every state: build each state from the error table and check it in the code. - `npm run build` and `npx booking-engine doctor --dist dist` once midway and once at the end; afterwards fix and rerun only what failed. ## 4. Finish - `CLAUDE.md` in the project root: the engine's boundaries (from `BOOKING_ENGINE.md`), where the design lives, and that new booking features need a new engine version, never custom database code. - Done when: `npm run build` and `npx booking-engine doctor --dist dist` pass; every field in `src/content/site.ts` is used and the page looks as designed with the defaults; the key sections show real photos (`PHOTOS.md`, AVIF/WebP with dimensions; `DESIGN.md` matches the tokens); `npm run dev` serves `/` with the preview banner and a booking flow that reaches the code step and the honest preview message, and `/admin/` shows “Connect your backend”. Stop the dev server. - End with a short summary: what you built, the design choices, and anything in the engine's documentation that was unclear or wrong.

محل حلاقة

قص وتدريج وتهذيب لحية وحلاقة، تُحجز بسرعة من الهاتف.

Build a complete, premium booking website for **{{BUSINESS_NAME}}**, a barbershop in {{CITY}}, in this empty folder. The booking system is an installed package — the **Profit Studio Booking Engine**. It owns availability, bookings, booking emails and the owner's dashboard. You design and build the public website around it, and nothing the engine provides. ## 1. Set up 1. Scaffold a Vite + React + TypeScript app **in the current folder**: `npm create vite@latest . -- --template react-ts --no-interactive`, then `npm install`. create-vite stops without an error when the folder is not empty — a `.DS_Store` or a `.claude/` folder is enough — so check that `package.json` now exists. If it does not, scaffold into a new subfolder the same way, move all of its files (dotfiles included) up into this folder without overwriting or deleting anything already here, and remove the empty subfolder. Remove the template's demo content. 2. `npm install --save-exact @profitstudio/booking-engine@2.0.0-beta.1`, then `npx booking-engine init`. 3. Read `node_modules/@profitstudio/booking-engine/docs/BUILD-A-SITE.md` once: it has every file to wire, the booking API and the error table. Open `docs/INTEGRATION.md` only at a section it names, and nothing else in the package. 4. Wire the engine as BUILD-A-SITE §1 shows, with this site's own preset as `preview.preset` — write it in `src/lib/preset.ts` and export it as `sitePreset` (BUILD-A-SITE §1) with the words “clients” and “appointments”; in `preview.business` use `{{BUSINESS_NAME}}`, the time zone `{{TIMEZONE}}` and a plausible placeholder `contact` in {{CITY}}. - Write `sitePreset` from this sample data (prices are US dollars: use the local currency at a plausible local price level; `id` "barbershop", `label` "Barbershop"): - Classic Cut · 30 min (+10 min buffer) · 40 · “Scissor or clipper cut, styled and finished with a neck shave.” - Skin Fade · 45 min (+10 min buffer) · 45 · “Tight fade blended to the skin, shaped on top, sharp line-up.” - Beard Trim & Line-up · 20 min (+5 min buffer) · 25 · “Shape, trim and a hot-towel line-up for the beard.” - Cut & Beard · 60 min (+10 min buffer) · 60 · “A full haircut and beard shape in one sitting.” - Hot Towel Shave · 40 min (+10 min buffer) · 45 · “Straight-razor shave with hot towels and a cool finish.” - Buzz Cut · 20 min (+5 min buffer) · 25 · “One length all over, cleaned up at the neck and ears.” - Kids Cut (under 12) · 30 min (+10 min buffer) · 28 · “A patient, quick cut for younger clients.” - Opening hours: Tuesday to Friday 10:00–19:00, Saturday 09:00–17:00; closed Sunday and Monday - Policies: 15-minute slot interval, at least 1 hour's notice, up to 30 days ahead, the owner confirms each request, a phone number is required; every other policy as in BUILD-A-SITE §1 The dashboard on `/admin/` mounts `<BookingAdmin engine={engine} siteUrl="/" content={siteContent} presets={[sitePreset]} />` and gets only your brand accent (light and dark) in `src/admin-theme.css`. One public page (sections and an in-page booking flow), no client-side routes. No backend yet: no Supabase project, no `supabase` commands, no `.env.local` — the site runs in preview mode with a visible “Preview — sample data, bookings are not saved” banner. ## 2. Design — the creative part Make it feel like a real, distinctive barbershop, not a template: - **Style direction:** {{STYLE_DIRECTION}} - **Audience:** Neighbourhood regulars and newcomers, mostly 18–50, who book a cut every three to five weeks — almost always on a phone, often the same day. - **Tone:** Easygoing, sharp and confident; plain-spoken and welcoming to everyone. No macho bravado, no “gentlemen's club” clichés. - **Sections:** - Hero with the shop's character and one clear “Book a chair” action, plus the soonest open time for the first service on the menu (named) when it is known - The menu: services, durations and prices loaded from the engine, readable at a glance like a board on the wall — with the owner's optional service photos (cuts, fades, beard work) shown in the site's own style when a service has one, and a complete menu without them - The barbers — placeholder names and short bios the owner will edit, clearly marked as samples (portraits come later from the owner) - The shop: the chairs, the music, the routine of a visit — what a first-timer can expect - Kind words — clearly marked as placeholder examples, never presented as real reviews - Opening hours (from the engine) and location / contact (from the engine's business contact), with directions - The booking flow - Footer with a discreet “Staff login” link to /admin/ - **Booking experience:** - Service first, then the date and time together, then details, then the email code, then confirmation — fast enough to finish standing in line for coffee - Make the soonest time obvious: a “Next open: today 4:15 PM” shortcut from data already loaded, and a week view that opens on today — on a closed day, say so and offer the next open time - Short services mean many times: group them Morning / Afternoon / Evening with counts, and keep the list scannable on a phone - There is one shared calendar: never offer “choose your barber” or show staff availability — the engine does not book per barber - Keep the chosen service, duration, price, date and time visible at every step — a summary beside the times on wide screens, a sticky bar on phones - The code step stays in the shop's voice: where the code went (masked), one large code field that accepts a pasted code, “Send a new code”, “Choose another time”, and a reminder to check spam - Designed states: times loading, times that could not load (Try again), a time just taken (fresh times), a fully booked day (the next open day), a closed day, and online booking switched off (call or message the shop) - Pending wording: “Request received — we'll confirm your chair shortly.” Confirmed wording: “You're booked. See you in the chair.” - **Imagery:** Real photography of the craft is part of the design: clippers and straight razors, the chair, the lather, the line-up, a door, window or street at dusk (no other shop's name, no barber pole, no identifiable people; if no such licensed photo exists, a designed frame such as a painted window sign) — one coherent photographic direction. Never present a photographed person as one of the shop's barbers: sample barber cards show tools or work, not faces, and stay labelled as samples until the owner adds real portraits. Graphic motifs (rules, numerals, signage lettering) frame the photos; they do not replace them. Service photos are the owner's (added per service in the dashboard): present them as part of the menu's design, never as stock fillers. - **Avoid:** - Barber-pole stripes, skulls, mustache icons and other stock barbershop clichés - A generic SaaS landing page look, purple gradients, glassmorphism - Invented awards, review counts, ratings or “best in town” claims - A “choose your barber” step or per-barber availability (not supported by the engine) - Hard-coded services, prices or opening hours (they come from the engine) - **Words:** call customers “clients” and bookings “appointments”. How: - **Identity first.** A short `DESIGN.md`: the concept in one sentence, a display face with character and a readable text face (both self-hosted with `@fontsource`), colour tokens with every text/background pair at 4.5:1 or better, a type and spacing scale, how motion behaves. Every value lives in one CSS file of custom properties. Two businesses in this niche with different style directions must not look like the same layout recoloured. Plain CSS, no UI kit. - **Composition.** Varied rhythm — full-bleed moments, asymmetric grids, one focal point per screen; designed for phones first, from 320 px to wide screens; keyboard-accessible with visible focus; motion of 150–600 ms with a purpose, off under `prefers-reduced-motion`. - **Engine data, never hard-coded:** services, prices, opening hours, contact details and availability (BUILD-A-SITE §3). “Open now” lines come from `getOpeningTimes`. Show each service's optional `image` in your own style when it has one, and make the services section complete with none. - **Owner-editable copy.** Declare the texts, photos, logo, brand colours and heading style the owner may change in `src/content/site.ts` (BUILD-A-SITE §2), with your copy and photos as defaults, render the page from it as text, and bake it in with the Vite plugin. - **Photos.** Free, properly licensed photographs (Unsplash or Pexels licence), at most six, downloaded into `photos/source/` and recorded in `PHOTOS.md` — never hot-linked, never a photographed person presented as staff (sample team cards show the work and say “Sample photo”; content-list images cannot have defaults, so sample cards may be text-only or share one site image). Free photos already checked for this niche, to start from (confirm the licence on each page; replace any): https://www.pexels.com/photo/barber-perfecting-a-fade-haircut-close-up-39559270/ (a fade being cut, close up (hero)); https://www.pexels.com/photo/vintage-barber-shop-interior-with-classic-chairs-37764947/ (a row of classic barber chairs); https://www.pexels.com/photo/customer-at-barber-16553361/ (a lathered shave in progress); https://www.pexels.com/photo/tools-at-barbershop-7697712/ (clippers and tools on a counter); https://www.pexels.com/photo/hairdresser-scissors-and-tools-10317439/ (scissors and combs); https://www.pexels.com/photo/gray-hand-tool-1319459/ (a brass shaving bowl and razors). Search terms that work: “barber fade close up”, “barbershop interior chairs”, “straight razor shave”, “barber tools clippers”. Prepare them with `npx booking-engine photos` (BUILD-A-SITE §5): AVIF + WebP at two or three widths, `width`/`height` on every `<img>`, fixed `aspect-ratio` frames with `object-fit: cover`, the hero eager with `fetchpriority="high"`, everything else lazy. When no fitting photo exists, design the frame without one. - **The booking flow** follows BUILD-A-SITE §4 with the calendar helpers: server slots only, the business time zone, the two steps (`requestBooking`, then the code and `verifyBooking`), every error in the table, contact details when online booking is off, success only after `verifyBooking` returned `ok: true`. On a phone: the step's name always visible, the choice and price in view, 44 px targets, the right input types, inline validation, a loading state on the control that waits, a code field that accepts a pasted code, focus on each new step's heading. - **Every “Book” button always answers.** Whatever the booking section is showing — loading, the flow, online booking off, no services, a calendar that failed to load — each Book/CTA button on the page scrolls to the booking section and moves focus to its heading, so the visitor sees that state's message and the shop's contact details. Never route a CTA only through the flow component (it is not on the page in those states), and never leave a click that does nothing. Check it with online booking off as well as on. ## 3. Work efficiently The viewer's Claude plan pays for every step, so keep the session lean: - Read BUILD-A-SITE.md once; don't re-read files you wrote or explore the package. - Photos: start from the leads above or spend at most about ten minutes searching; judge candidates on one contact sheet of small thumbnails, not one by one at full size. - Screenshots: about eight in all — desktop and a 390 px phone (device emulation), downscaled to at most 1280 px wide. Don't capture very long pages at full resolution. - Don't simulate the engine's error answers to see every state: build each state from the error table and check it in the code. - `npm run build` and `npx booking-engine doctor --dist dist` once midway and once at the end; afterwards fix and rerun only what failed. ## 4. Finish - `CLAUDE.md` in the project root: the engine's boundaries (from `BOOKING_ENGINE.md`), where the design lives, and that new booking features need a new engine version, never custom database code. - Done when: `npm run build` and `npx booking-engine doctor --dist dist` pass; every field in `src/content/site.ts` is used and the page looks as designed with the defaults; the key sections show real photos (`PHOTOS.md`, AVIF/WebP with dimensions; `DESIGN.md` matches the tokens); `npm run dev` serves `/` with the preview banner and a booking flow that reaches the code step and the honest preview message, and `/admin/` shows “Connect your backend”. Stop the dev server. - End with a short summary: what you built, the design choices, and anything in the engine's documentation that was unclear or wrong.

استوديو مساج وعافية

جلسات مساج وعلاجات، مع تجربة حجز هادئة.

Build a complete, premium booking website for **{{BUSINESS_NAME}}**, a massage & wellness studio in {{CITY}}, in this empty folder. The booking system is an installed package — the **Profit Studio Booking Engine**. It owns availability, bookings, booking emails and the owner's dashboard. You design and build the public website around it, and nothing the engine provides. ## 1. Set up 1. Scaffold a Vite + React + TypeScript app **in the current folder**: `npm create vite@latest . -- --template react-ts --no-interactive`, then `npm install`. create-vite stops without an error when the folder is not empty — a `.DS_Store` or a `.claude/` folder is enough — so check that `package.json` now exists. If it does not, scaffold into a new subfolder the same way, move all of its files (dotfiles included) up into this folder without overwriting or deleting anything already here, and remove the empty subfolder. Remove the template's demo content. 2. `npm install --save-exact @profitstudio/booking-engine@2.0.0-beta.1`, then `npx booking-engine init`. 3. Read `node_modules/@profitstudio/booking-engine/docs/BUILD-A-SITE.md` once: it has every file to wire, the booking API and the error table. Open `docs/INTEGRATION.md` only at a section it names, and nothing else in the package. 4. Wire the engine as BUILD-A-SITE §1 shows, with this site's own preset as `preview.preset` — write it in `src/lib/preset.ts` and export it as `sitePreset` (BUILD-A-SITE §1) with the words “guests” and “sessions”; in `preview.business` use `{{BUSINESS_NAME}}`, the time zone `{{TIMEZONE}}` and a plausible placeholder `contact` in {{CITY}}. - Write `sitePreset` from this sample data (prices are US dollars: use the local currency at a plausible local price level; `id` "massage-studio", `label` "Massage & Wellness Studio"): - Swedish Massage — 60 min · 60 min (+15 min buffer) · 95 · “Long, flowing strokes to ease tension and settle the mind.” - Swedish Massage — 90 min · 90 min (+15 min buffer) · 135 · “The full-body Swedish session with time for slower, deeper work.” - Deep Tissue — 60 min · 60 min (+15 min buffer) · 105 · “Firm, focused pressure for tight shoulders, back and legs.” - Deep Tissue — 90 min · 90 min (+15 min buffer) · 150 · “Unhurried deep work on the areas you choose.” - Hot Stone — 75 min · 75 min (+20 min buffer) · 125 · “Warm basalt stones and long strokes to release and soften.” - Pregnancy Massage — 60 min · 60 min (+15 min buffer) · 100 · “Side-lying comfort and gentle pressure, from the second trimester.” - Reflexology — 45 min · 45 min (+15 min buffer) · 70 · “Pressure-point work on the feet in a reclined chair.” - Opening hours: Monday to Friday 10:00–20:00, Saturday 09:00–17:00, Sunday 10:00–16:00 - Policies: 15-minute slot interval, at least 4 hours' notice, up to 60 days ahead, the owner confirms each request, a phone number is required; every other policy as in BUILD-A-SITE §1 The dashboard on `/admin/` mounts `<BookingAdmin engine={engine} siteUrl="/" content={siteContent} presets={[sitePreset]} />` and gets only your brand accent (light and dark) in `src/admin-theme.css`. One public page (sections and an in-page booking flow), no client-side routes. No backend yet: no Supabase project, no `supabase` commands, no `.env.local` — the site runs in preview mode with a visible “Preview — sample data, bookings are not saved” banner. ## 2. Design — the creative part Make it feel like a real, distinctive massage & wellness studio, not a template: - **Style direction:** {{STYLE_DIRECTION}} - **Audience:** Adults 25–65 looking for relief from everyday tension or simply an hour of quiet — often booking in the evening on a phone, sometimes for the first time. - **Tone:** Calm, warm and reassuring; clear and practical. Never clinical, never mystical, and never promise health outcomes. - **Sections:** - Hero that slows the visitor down, with one clear “Book a session” action - Treatments loaded from the engine — each length is its own service (e.g. 60 and 90 minutes), shown as a calm, readable list with durations and prices — with the owner's optional service photos in the site's own style when a service has one, and complete without them - What to expect: arriving, the room, comfort and pressure, privacy — written for a first-timer - The therapists — placeholder names and short bios the owner will edit, clearly marked as samples - Questions (what to wear, arriving early, cancelling) as plain text the owner can edit - Opening hours (from the engine) and location / contact (from the engine's business contact) - The booking flow - Footer with a discreet “Staff login” link to /admin/ - **Booking experience:** - Treatment and length first, then the date and time together, then details, then the email code, then confirmation - A calm calendar: the next open days first, times grouped Morning / Afternoon / Evening; never a countdown or scarcity pressure - There is one shared calendar: never offer “choose your therapist” or show per-therapist availability - The note field is optional and invites preferences (pressure, areas to avoid) — never ask for medical history or health details in the form - Keep the chosen treatment, length, price, date and time visible at every step - The code step is gentle and clear: where the code went (masked), one large code field that accepts a pasted code, “Send a new code”, “Choose another time”, a reminder to check spam - Designed states: loading, could not load (Try again), a time just taken, a fully booked day (the next open day), a closed day, online booking switched off (call or email the studio) - Pending wording: “Request received — we'll confirm your session shortly.” Confirmed wording: “Your session is booked.” - **Imagery:** Quiet, tactile photography: hands at work, linen, warm stones, oil, soft light across a treatment room — one coherent direction, little colour, lots of air. Never present a photographed person as one of the studio's therapists: sample therapist cards show the room or hands, not faces, and stay labelled as samples. No before/after imagery. Service photos are the owner's (added per service in the dashboard): present them as part of the design, never as stock fillers. - **Avoid:** - Spa clichés: orchids, Buddha statues, stacked stones, lotus icons - Medical claims, diagnoses, “cures” or before/after promises - Countdown timers, scarcity pressure or pushy upsells - A “choose your therapist” step or per-therapist availability (not supported by the engine) - Hard-coded services, prices or opening hours (they come from the engine) - **Words:** call customers “guests” and bookings “sessions”. How: - **Identity first.** A short `DESIGN.md`: the concept in one sentence, a display face with character and a readable text face (both self-hosted with `@fontsource`), colour tokens with every text/background pair at 4.5:1 or better, a type and spacing scale, how motion behaves. Every value lives in one CSS file of custom properties. Two businesses in this niche with different style directions must not look like the same layout recoloured. Plain CSS, no UI kit. - **Composition.** Varied rhythm — full-bleed moments, asymmetric grids, one focal point per screen; designed for phones first, from 320 px to wide screens; keyboard-accessible with visible focus; motion of 150–600 ms with a purpose, off under `prefers-reduced-motion`. - **Engine data, never hard-coded:** services, prices, opening hours, contact details and availability (BUILD-A-SITE §3). “Open now” lines come from `getOpeningTimes`. Show each service's optional `image` in your own style when it has one, and make the services section complete with none. - **Owner-editable copy.** Declare the texts, photos, logo, brand colours and heading style the owner may change in `src/content/site.ts` (BUILD-A-SITE §2), with your copy and photos as defaults, render the page from it as text, and bake it in with the Vite plugin. - **Photos.** Free, properly licensed photographs (Unsplash or Pexels licence), at most six, downloaded into `photos/source/` and recorded in `PHOTOS.md` — never hot-linked, never a photographed person presented as staff (sample team cards show the work and say “Sample photo”; content-list images cannot have defaults, so sample cards may be text-only or share one site image). Free photos already checked for this niche, to start from (confirm the licence on each page; replace any): https://unsplash.com/photos/massage-on-leg-with-white-towel-yBLLzNcA6GU (hands at work over a white towel (hero)); https://www.pexels.com/photo/settee-by-the-window-6628520/ (a treatment table by a tall window); https://unsplash.com/photos/hands-massaging-a-persons-forearm-with-gentle-pressure-YBfzGCJjLuI (hands working on a forearm). Search terms that work: “massage hands towel”, “treatment room window”, “spa linen stones”. Prepare them with `npx booking-engine photos` (BUILD-A-SITE §5): AVIF + WebP at two or three widths, `width`/`height` on every `<img>`, fixed `aspect-ratio` frames with `object-fit: cover`, the hero eager with `fetchpriority="high"`, everything else lazy. When no fitting photo exists, design the frame without one. - **The booking flow** follows BUILD-A-SITE §4 with the calendar helpers: server slots only, the business time zone, the two steps (`requestBooking`, then the code and `verifyBooking`), every error in the table, contact details when online booking is off, success only after `verifyBooking` returned `ok: true`. On a phone: the step's name always visible, the choice and price in view, 44 px targets, the right input types, inline validation, a loading state on the control that waits, a code field that accepts a pasted code, focus on each new step's heading. - **Every “Book” button always answers.** Whatever the booking section is showing — loading, the flow, online booking off, no services, a calendar that failed to load — each Book/CTA button on the page scrolls to the booking section and moves focus to its heading, so the visitor sees that state's message and the shop's contact details. Never route a CTA only through the flow component (it is not on the page in those states), and never leave a click that does nothing. Check it with online booking off as well as on. ## 3. Work efficiently The viewer's Claude plan pays for every step, so keep the session lean: - Read BUILD-A-SITE.md once; don't re-read files you wrote or explore the package. - Photos: start from the leads above or spend at most about ten minutes searching; judge candidates on one contact sheet of small thumbnails, not one by one at full size. - Screenshots: about eight in all — desktop and a 390 px phone (device emulation), downscaled to at most 1280 px wide. Don't capture very long pages at full resolution. - Don't simulate the engine's error answers to see every state: build each state from the error table and check it in the code. - `npm run build` and `npx booking-engine doctor --dist dist` once midway and once at the end; afterwards fix and rerun only what failed. ## 4. Finish - `CLAUDE.md` in the project root: the engine's boundaries (from `BOOKING_ENGINE.md`), where the design lives, and that new booking features need a new engine version, never custom database code. - Done when: `npm run build` and `npx booking-engine doctor --dist dist` pass; every field in `src/content/site.ts` is used and the page looks as designed with the defaults; the key sections show real photos (`PHOTOS.md`, AVIF/WebP with dimensions; `DESIGN.md` matches the tokens); `npm run dev` serves `/` with the preview banner and a booking flow that reaches the code step and the honest preview message, and `/admin/` shows “Connect your backend”. Stop the dev server. - End with a short summary: what you built, the design choices, and anything in the engine's documentation that was unclear or wrong.

خصّص الـ Prompt وانسخه

دورك.

افتح Customize Prompt في الـ Prompt أعلاه أدخل اسم نشاطك ومدينتك — تبدأ المنطقة الزمنية بمنطقتك أنت، فلا تغيّرها إلا إذا كان النشاط في مكان آخر اختر اتجاه أسلوب — كل اتجاه يمنح موقعك مظهرًا مختلفًا انسخ الـ Prompt — سترسله إلى Claude في الخطوة 2

Warm editorial — درجات الإسبريسو والنحاس والكريمي، وخط مذيَّل أنيق وتخطيطات تشبه المجلات

Modern minimal — أبيض شبه ناصع ورمادي فحمي مع لون مميز واحد واثق وشبكة صارمة

Bold urban — أسود عميق ودرجات رمادي إسمنتي ولون مميز واحد نابض، مع تباين قوي

Soft natural — أخضر المريمية والرملي والوردي الخفيف، وخطوط مستديرة، هادئ وفسيح

Heritage modern — أخضر القنينة والأحمر القاني والنحاس الأصفر على ورق دافئ، كلاسيكي دون أي مبالغة مسرحية

Industrial clean — أسود وفولاذي ودرجات رمادي إسمنتي مع لون إشارة واحد وأرقام كبيرة

Neighbourhood warm — كريمي وتيراكوتا وحبري، وخطوط ودودة ومسافات مريحة

Quiet Nordic — لون الشوفان والحجر وأخضر المريمية الناعم على أبيض دافئ، وهوامش واسعة وحركة لطيفة

Warm earth — طيني وتيراكوتا وزيتوني داكن، وعناوين مستديرة وأشكال عضوية

Night calm — أزرق حبري داكن ودرجات دافئة كضوء الشموع، خافت وحميم

يثبّت الـ Prompt Booking Engine بالإصدار 2.0.0-beta.1 تحديدًا، وهو الإصدار الذي اختُبر عليه هذا الدليل. لا تغيّره إلى latest.

افتح مجلدًا فارغًا

دورك.

Claude Desktop Code Local

أنشئ مجلدًا جديدًا فارغًا لموقعك، مثلًا في Documents ابدأ جلسة Local واختر ذلك المجلد إذا سألك Claude Desktop، فاختر الوثوق بالمجلد

أرسل الـ Prompt

دور Claude Code — أنت توافق على إجراءاته وتنتظر.

الصق الـ Prompt الذي نسخته في الخطوة 1 وأرسله انقر على Allow عندما يطلب Claude تشغيل أمر اتركه يعمل — البناء الكامل جلسة طويلة، فأبقِها مفتوحة

ينشئ مشروع الموقع ويثبّت Booking Engine

يصمّم الموقع: الخطوط والألوان والتخطيط والنصوص الخاصة بنشاطك

يجد صورًا مجانية ومرخّصة ويجهّزها للويب

يبني مسار الحجز وصفحة لوحة تحكم المالك

يفحص كل شيء باستخدام npm run build وnpx booking-engine doctor

إذا توقف Claude لأنك بلغت حد الاستخدام، فانتظر حتى يُعاد ضبطه، ثم اكتب continue في الجلسة نفسها.

ألقِ نظرة على موقعك

دور Claude Code، ثم دورك — هو يشغّل المعاينة، وأنت تلقي نظرة.

اعرض لي موقعي

يشغّل موقعك على جهازك ويعطيك عنوانه.

Start the website's dev server with npm run dev and open it in the Browser pane. Then give me its local address. Don't change any files.

اطّلع على المعاينة في Browser pane داخل Claude Desktop، أو افتح العنوان الذي يعطيك إياه Claude في متصفحك تحقّق من التصميم في نافذة عريضة وأخرى ضيقة انقر على زر Book: يُفتح مسار الحجز ويصل إلى الخطوة التي تطلب رمز البريد الإلكتروني افتح /admin/ — أضفه إلى العنوان، أو اطلب من Claude فتحه: تظهر عبارة Connect your backend

يعرض الشريط في الأعلى Preview: هذه بيانات نموذجية، ولا يُحفظ أي حجز بعد. هل تريد تغييرات؟ اطلبها من Claude في الجلسة نفسها قبل أن تتابع.

أنشئ مشروع Supabase الخاص بك

دورك — في حساب Supabase الخاص بك.

لهذه الخطوة ثلاثة أجزاء: Supabase، ثم البريد، ثم Prompt واحد يربط كل شيء. تُحفظ القيم التي تدخلها في هذا الدليل ويُعاد استخدامها في الخطوة 5، فتكتب كل قيمة مرة واحدة فقط.

افتح لوحة تحكم Supabase

https://supabase.com/dashboard

انقر على New project، واختر منطقة قريبة من نشاطك والباقة Free احفظ كلمة مرور قاعدة البيانات في مدير كلمات المرور — لا ترسلها إلى Claude أبدًا عندما يصبح المشروع جاهزًا، انقر على Connect والصق Project URL وPublishable key أدناه

أنشئ بيانات دخولك إلى لوحة التحكم

دورك — في حساب Supabase الخاص بك.

Supabase Authentication Users

انقر على Add user، ثم على Create new user أدخل بريدك الإلكتروني وكلمة مرور قوية اترك Auto Confirm User محددًا وأنشئ المستخدم

Supabase Authentication Sign In / Providers

أوقف Allow new users to sign up واحفظ — أنت وحدك من يسجّل الدخول إلى لوحة التحكم

سجّل الدخول إلى Supabase CLI

دورك — مرة واحدة، قبل الربط.

انقر على Terminal في شريط عنوان جلستك شغّل الأمر أدناه وافِق على تسجيل الدخول في نافذة المتصفح التي تُفتح

npx supabase@2 login

إذا طلب منك Claude ربط المشروع بنفسك، فشغّل الأمر الذي يعطيك إياه هنا واكتب كلمة مرور قاعدة البيانات في Terminal — وليس في المحادثة أبدًا.

تحقّق من نطاق الإرسال الخاص بك

دورك — في Resend وفي إعدادات DNS لنطاقك.

تُرسل رسائل الحجز من نطاقك الخاص — النطاق نفسه الذي سيستخدمه موقعك في الخطوة 5. لا تملك نطاقًا بعد؟ اشترِ واحدًا من Hostinger، ثم عُد إلى هنا:

Hostinger Domains

افتح نطاقات Resend

https://resend.com/domains

انقر على Add domain وأدخل نطاق الإرسال الظاهر أعلاه اختر المنطقة الأقرب إلى عملائك أبقِ الصفحة التي تعرض سجلات DNS مفتوحة

Hostinger Domains DNS / Nameservers

اختر نطاقك وأضف كل سجل يعرضه Resend، بالنوع والقيمة نفسيهما عُد إلى Resend وانقر على Verify DNS records

يستغرق التحقق عادةً أقل من 15 دقيقة، وقد يصل إلى 72 ساعة. تابع الخطوات التالية أثناء الانتظار. هل تدير نطاقك في مكان آخر؟ أضف السجلات نفسها هناك، واحتفظ بسجلات البريد الحالية.

أضف أسرار البريد إلى Supabase

دورك — يذهب المفتاح إلى Supabase فقط، ولا يدخل المحادثة أبدًا.

في Resend، افتح API Keys وانقر على Create API key اختر Sending access ونطاقك الذي تم التحقق منه، ثم انسخ المفتاح — يعرضه Resend مرة واحدة فقط في Supabase، افتح Edge Functions، ثم Secrets، وأضف هذين السرّين

RESEND_API_KEY

أبقِ مفتاح Resend سرّيًا

الصقه فقط في أسرار Edge Function في Supabase. لا ترسله إلى Claude أبدًا، ولا تضعه في ملف من ملفات الموقع أو في Prompt، ولا تضفه إلى Hostinger أبدًا.

اطلب من Claude ربط كل شيء

دور Claude Code — يتوقف كلما كان هناك شيء عليك فعله.

في جلسة Claude نفسها، انسخ هذا الـ Prompt وأرسله:

يسألك Claude قبل كل إجراء — انقر على Allow. ويتوقف عندما يحين دورك.

تنتهي عندما يعرض Claude عبارة Connected. تبدأ رسائل الحجز بمجرد أن يعرض Resend نطاقك بحالة Verified — وتؤكد ذلك رسالة الاختبار في الخطوة 4.

افتح لوحة التحكم

دور Claude Code، ثم دورك — هو يشغّل الموقع، وأنت تسجّل الدخول.

شغّل موقعي المتصل

يشغّل موقعك، المتصل الآن بـ Supabase، ويعطيك عنواني الموقع ولوحة التحكم.

Stop any dev server that is still running, so the new .env.local is read. Then start the website with npm run dev, open /admin/ in the Browser pane, and give me two addresses: the website and its /admin/ dashboard. Don't change any files.

افتح لوحة التحكم وسجّل الدخول ببيانات الدخول التي أنشأتها في الخطوة 3. لا يزال موقعك يعمل على حاسوبك، لكن كل شيء هنا حقيقي بالفعل: لوحة التحكم والحجوزات ورسائل البريد تستخدم مشروع Supabase الخاص بك، وموقعك المباشر في الخطوة 5 يستخدم البيانات نفسها.

أكمل الإعداد

دورك — في لوحة التحكم.

اختر أولًا وجهة تنبيهات الطلبات الجديدة

بدون عنوان للتنبيهات، لن يُبلَّغ أحد بالطلبات الجديدة، ولا يمكن تفعيل الحجز عبر الإنترنت.

اتبع Finish setting up في أعلى لوحة التحكم — يرشدك خطوة بخطوة عبر بيانات نشاطك والخدمات وساعات العمل والبريد في Email & online booking، اضبط Send new-request alerts to على بريدك الخاص، ثم انقر على Send test email وتحقّق من وصول الرسالة

قبل تفعيل الحجوزات، انقر على كل زر Book في موقعك: يجب أن ينتقل إلى قسم الحجز ويعرض بيانات التواصل الخاصة بك. الزر الذي لا يفعل شيئًا خلل — اطلب من Claude إصلاحه.

فعّل الحجز عبر الإنترنت

احجز موعدًا تجريبيًا

دورك — كعميل أولًا، ثم كمالك.

على موقعك، احجز خدمة باستخدام بريدك الإلكتروني الخاص. ثم ضع علامة على كل بند عندما تراه يحدث:

وصل الرمز المكوّن من 6 أرقام، وأظهر الموقع أنه تم استلام طلبك

وصل تنبيه الطلب الجديد إلى عنوان التنبيهات

نقرت على Confirm request في لوحة التحكم، ووصلت رسالة التأكيد

لم يعد الموعد نفسه معروضًا على موقعك

لم تصلك رسالة؟ تحقّق من مجلد البريد العشوائي أولًا، ثم افتح Email & online booking في لوحة التحكم: يعرض حالة كل رسالة وما يجب إصلاحه.

غيّر نصوص موقعك وصوره

دورك — في لوحة التحكم، دون شيفرة.

افتح Website في لوحة التحكم غيّر العنوان الرئيسي أو الصورة الرئيسية انقر على Preview للتحقق منه، ثم على Publish حدّث صفحة موقعك — التغيير موجود

صمّم Claude الموقع؛ وتعدّل لوحة التحكم النصوص والصور وألوان العلامة التجارية التي جعلها قابلة للتعديل. لقسم جديد أو تخطيط مختلف، اطلب من Claude.

أنشئ مستودع GitHub خاصًا

دورك — في حساب GitHub الخاص بك.

يعمل موقعك على حاسوبك. الآن ينتقل إلى الإنترنت: يحفظ GitHub الشيفرة، ويبنيه Hostinger ويقدّمه — مع بيانات Supabase نفسها التي اختبرتها للتو.

أنشئ مستودع GitHub

https://github.com/new

سمّه باسم نشاطك واختر Private اترك README و.gitignore وlicense غير مفعّلة، ليبقى المستودع فارغًا انقر على Create repository وانسخ عنوانه

ادفع موقعك إلى GitHub

دور Claude Code — أنت توافق على عملية الـ push.

ادفع موقعي إلى GitHub

يتأكد من عدم تضمين أي سر، وينفّذ commit لموقعك ويدفعه إلى مستودعك الجديد.

Put this website on GitHub at {{REPOSITORY_URL}}, on the main branch. Stop the dev server first. Before committing, check that .gitignore keeps node_modules, dist, .env, .env.local and supabase/.temp/ out of Git, and run npx booking-engine doctor. Show me the list of files you will commit and make sure no secret, key or password is in any of them. Then initialise Git if needed, commit everything with a clear message and push it to main. Never push to any other repository. If GitHub needs me to sign in, tell me exactly what to do, and never ask me to paste a password or token into the chat. When it's done, tell me the commit you pushed.

عنوان مستودعك

https://github.com/your-name/your-booking-website

أنشئ Web App الخاص بك

دورك — في Hostinger. لا تملك استضافة بعد؟ احصل على باقة من قسم المتطلبات.

Hostinger Websites Create site Web App

إذا عرضت عليك Hostinger اختيار نطاق، فاختر نطاقك الخاص — وإلا فسيبدأ تطبيقك على نطاق مؤقت اختر Import Git Repository امنح GitHub الإذن واختر المستودع الذي دفعه Claude للتو

اضبط الإعدادات وانشر

دورك — في Hostinger.

أبقِ إعدادات Vite التي يكتشفها Hostinger اختر Node.js 22 أو أحدث تأكد من أن أمر البناء هو npm run build وأن مجلد الإخراج هو dist

قبل النشر، ابحث عن Environment variables ضمن Review build settings، وانقر على Edit وأضف هذين المتغيرين — قيمك من الخطوة 3، جاهزة للنسخ. هما مدمجتان في الموقع، لذا يتطلب تغيير إحداهما لاحقًا إعادة النشر.

قيم عامة فقط

لا تضف هنا أبدًا Secret key الخاص بـ Supabase أو مفتاح Resend. كل ما يبدأ بـ VITE_ يكون مرئيًا في المتصفح، وتبقى أسرار البريد في Supabase.

انقر على Finish، ثم Deploy، وانتظر حتى ينتهي البناء

إذا توقف البناء وذكر اسم متغير، فصحّح قيمة ذلك المتغير في Hostinger وانشر مرة أخرى.

أضف عنوانك المباشر إلى تنبيهات المالك

دور Claude Code.

تحقّق من موقعك المباشر

دورك.

افتح نطاقك — يظهر رمز القفل ولا يوجد شريط Preview تحقّق من خدماتك وأسعارك وساعات العمل على هاتفك، احجز موعدًا تجريبيًا وأدخل الرمز افتح /admin/ على موقعك المباشر، وسجّل الدخول وأكّد الطلب تحقّق من وصول التنبيه ورسالة التأكيد كليهما

من الآن فصاعدًا، غيّر الخدمات والأسعار وساعات العمل ونصوص موقعك وصوره من لوحة التحكم — تظهر التغييرات على الموقع فورًا. لتغييرات التصميم أو الشيفرة، اطلب من Claude ووافق على الـ push: يعيد Hostinger بناء موقعك مع كل push إلى main. ترى محركات البحث العنوان أو الوصف الجديد للصفحة بعد البناء التالي.