[WIP] You are a proficient AI developer tasked with building **“Daraz Clone”**, a full-featured, production-ready e-commerce platform. It must closely mirror Daraz’s architecture and user experience. Deliver both web and mobile clients plus the backend...

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original description:

You are a proficient AI developer tasked with building “Daraz Clone”, a full-featured, production-ready e-commerce platform. It must closely mirror Daraz’s architecture and user experience. Deliver both web and mobile clients plus the backend and operations pipeline.

---

1) Requirements Overview

• Multi-vendor marketplace: buyers, sellers, and admins.
• Platforms: Web (React/Vue) and Mobile (Flutter or React Native).
• Modular microservices: Catalog, Search, Cart, Orders, Payments, Recommendations, Users, Notifications.
• Scalable, deployable via Docker and Kubernetes or managed cloud services.

---

2) Features to Implement

A. Web & Mobile Frontend

• Homepage: Hero carousel, categories, flash deals, recommendations.
• Product Listing: Filters (brand, price, discount, category).
• Product Detail: Images, reviews, vendor info, stock status.
• Search: Text + visual suggestions, fast results.
• Cart & Checkout: Multi-step, address, payment method (cards, wallets, COD).
• User Account: Profile, orders dashboard, wishlist.
• Seller Dashboard: Product upload, inventory, orders, analytics.
• Admin Panel: Manage categories, vendors, promotions, site-wide settings.
• Localization: Language + currency switch per region.

B. Backend Services (Microservices)

• Auth (JWT, OAuth), User, Product, Search (Elasticsearch), Order, Cart, Payment, Notification (email/SMS), Recommendation (collaborative filtering).
• REST APIs (OpenAPI spec); GraphQL optional.
• Database: PostgreSQL for core relational data, Redis cache.
• Payments integration: Stripe, Razorpay, mobile wallets.
• Logistics: Order tracking, webhook integration.

C. AI/ML Features

• Personalized recommendations.
• Search auto-completion.
• Flash-sale optimizations (load-warnings, queue mechanisms).

D. DevOps & Infrastructure

• Docker + docker-compose; optional Kubernetes YAML.
• CI/CD pipelines (GitHub Actions) for test → staging → production.
• Monitoring: Prometheus + Grafana; logging and error alerts.
• CDN for static assets.

E. Scalability & Performance

• Database indexing, query optimization.
• Caching layers for products and sessions.
• Rate limiting and circuit breakers during high traffic (e.g., Super sale events).
• Automatic scaling policies.

F. Security

• CSRF protection, input validation, HTTPS enforcement.
• Secure file uploads, WAF rules.
• Logging and audit trails.

G. Admin & Analytics

• Export sales, vendor, and order reports.
• Dashboard with metrics: GMV, bounce rate, conversion ratio.

---

3) Deliverables

1. Web Frontend repository:

   • React (or Vue) SPA structure.
   • Routing, state management (Redux/Vuex), reusable components.

2. Mobile App repository:

   • Flutter or React Native full app with identical flows.

3. Backend Microservice repositories:

   • Each service with models, routes, controllers, tests.
   • OpenAPI/Swagger documentation.

4. Infrastructure:

   • Dockerfiles, docker-compose.yml.
   • Kubernetes manifests (optional).
   • CI workflows (lint, test, deploy).

5. AI Models:

   • Stub files for recommending engine (can be basic ranking logic).
   • Search index setup and update scripts.

6. DevOps & Release Assets:

   • Deployment scripts, staging vs production configs.
   • Domain, SSL certificate placeholders.
   • Monitoring dashboards and health check endpoints.

7. Documentation:

   • README for each repository.
   • API documentation, setup instructions, environment config.
   • Feature overview, architecture diagrams, user flow diagrams, and operational guides.

---

4) Output Format

Deliver as:

1. A high-level architecture diagram and summary.
2. Then, file-by-file code output (readable single-file per file blocks: path + content).
3. Then setup instructions, env file templates.
4. Then CI/CD and Docker configs.
5. Then watch for acceptance criteria: being able to register users, list products, place an order, and vendor/delivery flows.

Begin with architecture summary and module breakdown.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.