Remix

Make your own version of Global Care

Get an exact, working copy in your account, then change anything with chat.

Original by abiyaalini

What would you change?

Start free with 40 credits. No card needed.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.

# GLOBAL CARE — COMPLETE MASTER BUILD PROMPT FOR BOLT.NEW

Build **Global Care**, a premium, secure, international healthcare discovery and medical-travel platform, using my reference website: https://sites.google.com/view/globalcarecoimbatore/home

## 1. NON-NEGOTIABLE BUILD AND CREDIT RULES
First inspect the existing project, files, framework, integrations, and current progress. Preserve working code. Do not regenerate the entire project or duplicate existing features. Use the fewest possible prompts, files, dependencies, API calls, and build steps. Prefer free/open-source tools, existing components, and eligible free hosting. Avoid paid APIs and unnecessary packages. Never spend credits on cosmetic rewrites when a targeted fix works. Build in clear phases, test after each phase, and prioritise a functioning secure foundation over unfinished extras. Never claim a feature is complete unless it works. Clearly list anything requiring paid services, credentials, backend setup, or additional credits.

## 2. TWO COMPLETELY SEPARATE WEBSITES
Create and deploy two independent applications with separate deployment URLs:

**A. Public Global Care website:** public-facing healthcare discovery, skincare AI, enquiries, membership and customer dashboard.

**B. Global Care Admin:** a separate admin application, separately deployed, with independent authentication. Never expose admin pages in public navigation. Do not rely on hiding a link for security. Both apps may use the same backend only through secure, authenticated, role-restricted APIs. Give the actual deployment URLs only after successful deployment.

## 3. PREMIUM DESIGN
Use midnight navy, teal, ivory, white and restrained champagne-gold accents; refined typography, spacious layouts, subtle animations, polished cards, professional healthcare photography and elegant hospital/hotel imagery. Ensure excellent mobile, tablet and desktop layouts, accessibility, readable contrast, clear navigation and fast loading. Use appropriately licensed images or clearly label conceptual imagery. No misleading medical imagery.

## 4. PUBLIC WEBSITE FEATURES
Build a complete responsive homepage, about page, services, hospital/clinic directory, verified doctor/dermatologist directory, treatment discovery, treatment cost estimates, international-patient assistance, consultation enquiries, booking requests, hotel discovery, transport/travel coordination, contact page, FAQ, privacy/terms/consent pages, customer sign-up/login, profile and dashboard, enquiry/booking status, and multilingual-ready structure. Include search, filters, detail pages and clear calls to action. Distinguish enquiries, requests, confirmed bookings and completed transactions.

Display both contact options wherever appropriate:
- WhatsApp: +91 63817 28826 — https://wa.me/916381728826
- WhatsApp: +91 76395 02307 — https://wa.me/917639502307

Provide separate chat buttons. Never promise 24/7 support or automatically send sensitive health details through WhatsApp.

## 5. REAL DATA ONLY — ABSOLUTELY NO FABRICATION
Use traceable information from official hospital/clinic/doctor websites, government registries, recognised medical sources, and authorised integrations. Verify details against the original source and retain source URL, verification status, and last-checked date. Never invent providers, doctors, credentials, affiliations, partnerships, prices, ratings, reviews, product ingredients, availability, statistics, appointments or bookings. Do not scrape or republish data contrary to source terms. Do not present sample/demo records as real. If reliable information is unavailable, show “Not verified,” “Information unavailable,” or “Request a quotation.” Clearly label estimates and explain that actual treatment costs require provider confirmation. Do not claim a provider partners with Global Care without documented authorisation. Provide a secure admin verification workflow.

## 6. ADVANCED AI SKINCARE
Create a skincare AI experience where users can optionally upload a skin photo and describe concerns. Provide cautious observations of visible features, general educational guidance, personalised but non-diagnostic AM/PM routines, explanations of verified skincare ingredients, and genuine product comparisons using verified ingredients, source links and user-selected budgets. Clearly state limitations and uncertainty. Never guarantee results, diagnose disease, prescribe medication, or replace a qualified dermatologist. Recommend professional assessment when appropriate; provide extra safeguards for minors. Do not invent products or ingredients. Use an authorised AI/API provider only when configured. If unavailable, provide a clear non-AI fallback rather than fake AI results.

Obtain informed consent before image processing. Secure uploads, restrict access, minimise retention, provide deletion controls, avoid unnecessary storage, and never use health photos for model training without separate appropriate consent. Do not expose photos or sensitive health data in logs, analytics, URLs or public storage.

## 7. SKIN AI MEMBERSHIP PAGE
Create `/skin-ai-membership` with Free, Premium and Advanced tiers. Let authorised admins configure prices, billing intervals, usage limits and features without code edits or redeployment. Do not invent prices, entitlements or working usage limits: mark unconfigured options clearly. Show a transparent comparison, subscription status, usage, invoices, upgrade/downgrade and cancellation controls where supported. Separate AI digital membership charges from consultations, treatment, medicine, hotel and travel expenses. Never imply membership includes medical care.

## 8. RAZORPAY AND BILLING
Integrate Razorpay only through secure server-side APIs and environment secrets. Create orders on the server, verify signatures server-side, validate webhooks, prevent duplicate processing, and activate paid access only after verified payment. Handle failures, pending payments, cancellations and refunds where supported. Use Test Mode before launch. Never store card details or expose secret keys in frontend code. Support recurring subscriptions only if the account, plan and integration genuinely support them. Never simulate a successful payment. If credentials or backend are missing, show setup instructions and a safe unavailable state. Keep payment records and invoices accurate.

## 9. SEPARATE ADMIN WEBSITE
Build a professional admin dashboard with role-based permissions and protected server-side routes/APIs. Include:
- User accounts and access management
- Hospital, clinic, doctor and hotel records
- Verification status, source URLs and last-checked dates
- Treatment information and quotation management
- Enquiries, consultation requests and booking status
- AI membership plans, prices, features and usage limits
- Payments, subscription status and supported refund workflows
- Content, contact details and integration settings
- Reports based only on real recorded data
- Audit logs for important admin actions

Validate inputs, prevent unauthorised changes, protect personal/medical/payment data, and require strong authentication. Do not allow ordinary users to access admin data. Record who changed prices and when. Preserve historical invoices and apply subscription price changes transparently; never silently alter existing customers’ agreed prices. Never expose secrets in the dashboard.

## 10. BACKEND, SECURITY AND PRIVACY
Use the existing compatible backend if available; otherwise recommend the lowest-cost suitable option, such as an eligible free-tier database/authentication service. Use persistent storage, validated APIs, secure authentication, least-privilege permissions, rate limiting where appropriate, error handling, backups where supported, and environment variables. Do not use browser-only storage as the sole database for important bookings or payments. Collect only necessary data, provide deletion/retention controls, and document relevant privacy, consent and legal requirements for the jurisdictions served. Do not claim legal compliance without review.

## 11. DEPLOYMENT AND FINAL TESTING
Deploy the public website and admin application independently. Test signup/login, role restrictions, mobile layouts, search, source verification, enquiry submission, booking status, membership configuration, payment verification and error states. Check that no secret keys or private records appear publicly. Test with clearly labelled test records and Razorpay Test Mode; remove test data before launch. Verify that each deployed URL actually works. Provide setup steps, required environment variables (names only, never secrets), integrations needing credentials, free-tier limitations, and a list of unfinished items.

## 12. BUILD ORDER — SAVE CREDITS
Phase 1: inspect project and create a concise implementation plan.
Phase 2: finish the shared design system and essential public pages.
Phase 3: implement secure backend, authentication, database and real-data verification.
Phase 4: implement the separately deployed admin app and permissions.
Phase 5: implement skincare AI and privacy protections.
Phase 6: implement membership and Razorpay securely.
Phase 7: test, fix critical bugs, and deploy both apps separately.

Start by inspecting the existing project. Then implement the highest-priority working foundation without unnecessary questions or a full rewrite. Keep a concise checklist of completed, blocked and remaining features. If a requirement cannot be implemented with the available tools or free tier, explain the exact limitation and provide the safest practical alternative. **Accuracy, privacy, security, genuine functionality and minimal credit use are more important than pretending everything is finished.**

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.