Remix

Make your own version of VYROX Grooming

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

Original by Mahbeeristoji Mahbeer

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.

# BUILD VYROX — A COMPLETE, PRODUCTION-READY E-COMMERCE WEBSITE FROM SCRATCH

Act as an elite full-stack developer, UI/UX designer, backend engineer, and e-commerce security specialist. Build a complete, premium e-commerce website called **VYROX** from zero. Do not modify an existing website. Create the entire project, including the frontend, backend, database, authentication, admin dashboard, product catalog, shopping cart, checkout, and email notifications.

Do not build just a static mockup. All core functions must work using real integrations.

## 1. PREMIUM BRAND DESIGN

Brand: VYROX

Business: Men's skincare, fitness accessories, grooming products, and looksmaxxing accessories.

Design direction:
- Ultra-premium, modern, cinematic design.
- Black and white base with sophisticated accent colors.
- High-quality product imagery, smooth animations, premium typography, and elegant transitions.
- Professional desktop, tablet, and mobile layouts.
- Fast loading, responsive navigation, and accessible controls.
- Beautiful homepage with a hero section, featured products, categories, best sellers, offers, testimonials, and footer.
- Product pages with image galleries, descriptions, prices, stock status, quantity selector, and Add to Cart.
- Search, sorting, category filters, and a polished checkout experience.
- Never use fake testimonials, fake sales counters, or fake customer reviews.

## 2. REAL CONTACT INFORMATION

WhatsApp: 03173239453  
Admin email: mahbeerpanhwer17@gmail.com

Requirements:
- Add a floating WhatsApp button throughout the customer-facing website.
- Connect it to the real WhatsApp chat using the international number format +923173239453.
- Make the contact email clickable and configure a real contact form.
- Validate contact form fields and show success or error messages.
- Protect the contact form against spam.
- Do not expose private API keys or credentials.

## 3. CUSTOMER ACCOUNTS AND ADMIN AUTHENTICATION

Build secure authentication with separate customer and administrator permissions.

Administrator email: mahbeerpanhwer17@gmail.com

Admin features:
- Secure admin login.
- Forgot Password link.
- Real password-reset email sent to the administrator's email address.
- Use a secure, single-use, expiring reset link or verification code.
- Never reveal whether an arbitrary email address has an account.
- Rate-limit login and password-reset attempts.
- Hash passwords securely if passwords are stored by the application.
- Protect admin routes and API endpoints on the server.
- Never allow public users to register as administrators.
- Create the initial admin account through a secure setup process or a trusted authentication provider.
- Do not hardcode an admin password or store secrets in frontend code.

IMPORTANT: The admin email alone must not automatically grant access. Verify ownership securely during the initial setup. Do not claim that password-reset emails work until the email provider has been configured and delivery has been tested.

## 4. COMPLETE ADMIN DASHBOARD

Create a premium, private admin dashboard with a sidebar and overview cards.

Dashboard sections:
1. Overview
2. Products
3. Categories
4. Orders
5. Customers
6. Inventory
7. Discounts
8. Email notifications
9. Store settings
10. Logout

Display real database information, not hardcoded sample numbers.

Product management:
- Add, edit, and delete products.
- Upload product images.
- Set product name, description, price, sale price, SKU, category, and inventory.
- Mark products as active or unavailable.
- Validate prices and inventory on the server.

Order management:
- Display all real orders in a searchable, filterable table.
- Show order number, order date, items, quantities, totals, payment method, payment status, and fulfillment status.
- Open an order to view its full details.
- Update fulfillment status.
- Support pending, confirmed, processing, shipped, delivered, and cancelled statuses.
- Keep an accurate order history.
- Never create fake customer orders.

## 5. FULLY FUNCTIONAL SHOPPING CART

Build a real cart system:
- Add products to cart.
- Remove products.
- Increase or decrease quantities.
- Display product image, name, price, quantity, subtotal, shipping, and final total.
- Recalculate totals correctly.
- Persist cart items across page refreshes.
- Show a clear empty-cart state.
- Validate inventory, prices, and totals on the backend.
- Prevent invalid quantities and overselling.
- Make the checkout button work.

## 6. REAL CHECKOUT AND ORDER CREATION

Create a checkout form that collects only necessary information:
- Customer name.
- Email.
- Phone number.
- Delivery address.
- City and postal code where applicable.
- Selected supported payment method.

Payment requirements:
- Offer Cash on Delivery only when the merchant's shipping arrangement supports it.
- Integrate a legitimate payment provider only after its credentials and account are configured.
- Never claim an online payment succeeded without verified payment confirmation.
- Never store raw card numbers or security codes.
- Validate orders and prices on the server.
- Create each order exactly once, even if the customer refreshes the page or retries a request.
- Show a proper order confirmation page with an order reference.

Do not invent a shipping company, supplier, payment provider, or delivery capability. Make these configurable in the admin settings.

## 7. INSTANT NEW-ORDER EMAIL NOTIFICATIONS

Send an actual email to:

**mahbeerpanhwer17@gmail.com**

Whenever a real order is successfully created, send an email with:
- Subject: NEW VYROX ORDER — #[ORDER NUMBER]
- Order number and date.
- Products and quantities.
- Item prices and total.
- Payment method and payment status.
- Customer's submitted name, phone, and shipping details.
- A secure link to open the order in the admin dashboard.

Technical requirements:
- Use a backend email integration such as a properly configured transactional email provider.
- Store API keys securely in server-side environment variables.
- Trigger notifications after successful order creation.
- Prevent duplicate notifications using idempotency or an order-notification record.
- Record delivery failures and provide a retry mechanism.
- Do not include passwords, reset tokens, or payment secrets in notification emails.
- Test delivery to the specified admin email.

Also implement customer order-confirmation emails when a valid email address is provided.

If an email provider requires an API key, domain verification, or sender verification, tell me exactly what I must configure. Do not pretend the integration works before testing it.

## 8. DATABASE AND BACKEND

Use a suitable, persistent database and a secure backend.

Create appropriate data models for:
- Products.
- Categories.
- Customers.
- Orders.
- Order items.
- Inventory.
- Admin permissions.
- Password-reset or authentication records, if managed by the application.
- Email notification status.
- Store settings.

Requirements:
- Persist real data across reloads and deployments.
- Validate all inputs on the server.
- Use secure authentication sessions or a trusted authentication service.
- Apply role-based access control.
- Protect private endpoints.
- Use transactions or equivalent safeguards for order creation and stock changes.
- Add appropriate error handling, logging, and database migrations.
- Do not use browser local storage as the only database for orders or admin accounts.

Choose a practical, supported full-stack technology stack for this environment. Explain any required services and environment variables.

## 9. MOBILE-FIRST USER EXPERIENCE

Make the complete store work smoothly on phones, tablets, and computers.

Include:
- Mobile navigation.
- Product search.
- Product filters.
- Cart drawer or cart page.
- Checkout form.
- Order confirmation.
- WhatsApp contact button.
- Responsive admin dashboard.
- Loading states, empty states, validation errors, and success messages.

Prioritize performance, security, accessibility, and a polished premium appearance.

## 10. TEST THE ENTIRE SYSTEM

Before declaring completion, verify:
- Homepage and product pages load.
- Products can be added, edited, and removed by the admin.
- Cart quantities and totals are correct.
- Orders are persisted in the database.
- A new order appears in the admin dashboard.
- The administrator receives a real order-notification email.
- Forgot Password sends a working reset email.
- Password reset tokens expire and cannot be reused.
- Unauthenticated users cannot access private admin routes.
- Ordinary customers cannot modify products or view other customers' orders.
- Inventory cannot become negative through concurrent orders.
- WhatsApp opens the correct contact.
- Mobile and desktop layouts work.

Use test mode for payment testing and clearly distinguish test orders from real orders.

## FINAL INSTRUCTION

Start by creating the actual complete project from scratch. Implement the design and functionality, connect the database and required services, and run the available tests. Do not stop after generating a homepage or a design preview.

At the end, provide:
1. What has actually been implemented.
2. The database and authentication setup steps.
3. The email setup steps.
4. How to create and secure the first administrator account.
5. Any API keys or external services I must configure.
6. Any features that remain incomplete or untested.

Be honest about limitations. Never claim that a feature is functional unless it has been implemented and verified.

Start fresh from this prompt

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