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 सिर्फ़ इन्हीं पर चलते हैं: Business पर 5 तक, Cloud पर 10 तक।

अपने बिज़नेस का प्रकार चुनें

आपका काम। 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.

अपना प्रॉम्प्ट कस्टमाइज़ और कॉपी करें

आपका काम।

ऊपर दिए प्रॉम्प्ट पर Customize Prompt खोलें अपने बिज़नेस का नाम और शहर डालें — टाइम ज़ोन शुरू में आपका ही होता है, इसलिए इसे सिर्फ़ तब बदलें जब बिज़नेस कहीं और हो एक शैली दिशा चुनें — हर दिशा आपकी वेबसाइट को अलग रूप देती है प्रॉम्प्ट कॉपी करें — आप इसे चरण 2 में Claude को भेजेंगे

Warm editorial — एस्प्रेसो, कॉपर और क्रीम, एक सुरुचिपूर्ण सेरिफ़ फ़ॉन्ट और मैगज़ीन जैसे लेआउट

Modern minimal — लगभग-सफ़ेद और चारकोल, एक आत्मविश्वासी एक्सेंट रंग और सख़्त ग्रिड के साथ

Bold urban — गहरा काला, कंक्रीट ग्रे और एक चमकदार एक्सेंट रंग, तीखे कंट्रास्ट के साथ

Soft natural — सेज, सैंड और ब्लश, गोलाई वाले अक्षर, शांत और हवादार

Heritage modern — गर्म कागज़ पर बॉटल ग्रीन, ऑक्सब्लड और पीतल, क्लासिक, पर कभी दिखावटी नहीं

Industrial clean — काला, स्टील और कंक्रीट ग्रे, एक सिग्नल रंग और बड़े अंकों के साथ

Neighbourhood warm — क्रीम, टेराकोटा और इंक, दोस्ताना अक्षर और खुली-खुली स्पेसिंग

Quiet Nordic — गर्म सफ़ेद पर ओट, स्टोन और हल्का सेज, चौड़े मार्जिन और कोमल मोशन

Warm earth — क्ले, टेराकोटा और गहरा ऑलिव, गोलाई वाली हेडलाइन और प्राकृतिक आकार

Night calm — गहरा इंक ब्लू और मोमबत्ती जैसे गर्म रंग, मद्धम और आत्मीय

प्रॉम्प्ट Booking Engine को ठीक वर्ज़न 2.0.0-beta.1 पर इंस्टॉल करता है, यही वर्ज़न इस गाइड के साथ टेस्ट किया गया था। इसे latest में न बदलें।

एक खाली फ़ोल्डर खोलें

आपका काम।

Claude Desktop Code Local

अपनी वेबसाइट के लिए एक नया, खाली फ़ोल्डर बनाएँ, जैसे Documents में एक Local सेशन शुरू करें और वह फ़ोल्डर चुनें अगर Claude Desktop पूछे, तो फ़ोल्डर पर भरोसा करें

अपना प्रॉम्प्ट भेजें

Claude Code का काम — आप उसकी कार्रवाइयों को मंज़ूरी देते हैं और इंतज़ार करते हैं।

चरण 1 में कॉपी किया गया प्रॉम्प्ट पेस्ट करें और भेजें जब Claude कोई कमांड चलाने के लिए पूछे, तो Allow पर क्लिक करें इसे काम करने दें — पूरा बिल्ड एक लंबा सेशन होता है, इसलिए इसे खुला रखें

वेबसाइट प्रोजेक्ट बनाता है और 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.

Claude Desktop के Browser pane में प्रीव्यू देखें, या Claude का दिया पता अपने ब्राउज़र में खोलें डिज़ाइन को चौड़ी और संकरी, दोनों विंडो में जाँचें किसी Book बटन पर क्लिक करें: बुकिंग फ़्लो खुलता है और उस चरण तक पहुँचता है जो ईमेल कोड माँगता है /admin/ खोलें — इसे पते में जोड़ें, या Claude से खोलने को कहें: यह Connect your backend दिखाता है

ऊपर का बैनर Preview दिखाता है: यह सैंपल डेटा है, और अभी कोई बुकिंग सेव नहीं होती। बदलाव चाहिए? आगे बढ़ने से पहले उसी सेशन में Claude से कहें।

अपना Supabase प्रोजेक्ट बनाएँ

आपका काम — आपके Supabase अकाउंट में।

इस चरण के तीन हिस्से हैं: Supabase, फिर ईमेल, फिर एक प्रॉम्प्ट जो सब कुछ कनेक्ट करता है। आप जो मान डालते हैं, वे इस गाइड में सेव होते हैं और चरण 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 Domains खोलें

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 की को सीक्रेट रखें

इसे सिर्फ़ Supabase के Edge Function सीक्रेट में पेस्ट करें। इसे कभी Claude को न भेजें, कभी किसी वेबसाइट फ़ाइल या प्रॉम्प्ट में न डालें, और कभी Hostinger में न जोड़ें।

Claude से सब कुछ कनेक्ट करने को कहें

Claude Code का काम — जब भी कोई काम आपका हो, वह रुक जाता है।

उसी Claude सेशन में यह प्रॉम्प्ट कॉपी करें और भेजें:

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 से कहें।

एक Private GitHub रिपॉज़िटरी बनाएँ

आपका काम — आपके GitHub अकाउंट में।

आपकी वेबसाइट आपके कंप्यूटर पर काम करती है। अब यह ऑनलाइन जाती है: GitHub कोड रखता है, और Hostinger इसे बिल्ड करके सर्व करता है — उसी Supabase डेटा के साथ जिसे आपने अभी टेस्ट किया।

GitHub रिपॉज़िटरी बनाएँ

https://github.com/new

इसे अपने बिज़नेस के नाम पर रखें और Private चुनें README, .gitignore और license बंद रहने दें, ताकि रिपॉज़िटरी खाली रहे Create repository पर क्लिक करें और इसका पता कॉपी करें

अपनी वेबसाइट GitHub पर पुश करें

Claude Code का काम — आप पुश को मंज़ूरी देते हैं।

मेरी वेबसाइट GitHub पर पुश करो

जाँचता है कि कोई सीक्रेट शामिल नहीं है, आपकी वेबसाइट कमिट करता है और उसे आपकी नई रिपॉज़िटरी में पुश करता है।

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 में।

Hostinger जो Vite सेटिंग्स पहचानता है, उन्हें वैसे ही रहने दें Node.js 22 या नया चुनें पक्का करें कि बिल्ड कमांड npm run build है और आउटपुट डायरेक्टरी dist है

डिप्लॉय करने से पहले Review build settings में Environment variables ढूँढें, Edit पर क्लिक करें और ये दोनों जोड़ें — चरण 3 के आपके मान, कॉपी करने के लिए तैयार। ये वेबसाइट में बिल्ट-इन होते हैं, इसलिए बाद में किसी एक को बदलने पर दोबारा डिप्लॉय करना होगा।

सिर्फ़ सार्वजनिक मान

यहाँ कभी Supabase Secret key या Resend की न जोड़ें। VITE_ से शुरू होने वाली हर चीज़ ब्राउज़र में दिखती है, और आपके ईमेल सीक्रेट Supabase में ही रहते हैं।

Finish, फिर Deploy पर क्लिक करें, और बिल्ड पूरा होने तक इंतज़ार करें

अगर बिल्ड रुक जाए और किसी वेरिएबल का नाम बताए, तो Hostinger में उस वेरिएबल का मान ठीक करें और दोबारा डिप्लॉय करें।

ओनर अलर्ट में अपना लाइव पता जोड़ें

Claude Code का काम।

अपनी लाइव वेबसाइट जाँचें

आपका काम।

अपना डोमेन खोलें — ताले का निशान दिखता है और कोई Preview बैनर नहीं है अपनी सेवाएँ, कीमतें और खुलने का समय जाँचें अपने फ़ोन पर एक टेस्ट अपॉइंटमेंट बुक करें और कोड डालें अपनी लाइव साइट पर /admin/ खोलें, साइन इन करें और अनुरोध कन्फ़र्म करें जाँचें कि अलर्ट और कन्फ़र्मेशन ईमेल, दोनों पहुँचे

अब से सेवाएँ, कीमतें, समय और अपनी वेबसाइट के शब्द और फ़ोटो डैशबोर्ड में बदलें — वे तुरंत लाइव हो जाते हैं। डिज़ाइन या कोड बदलावों के लिए Claude से कहें और पुश को मंज़ूरी दें: main पर हर पुश पर Hostinger आपकी साइट दोबारा बिल्ड करता है। सर्च इंजन नया पेज टाइटल या विवरण अगले बिल्ड के बाद देखते हैं।