001 multi tenant ecommerce

[rezwana-karim]

Description

Why

Fixes #
Related to #

What

Type of Change

Please check the relevant option(s):

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📝 Documentation update
• 🎨 Style/UI change
• ♻️ Code refactoring (no functional changes)
• ⚡ Performance improvement
• ✅ Test addition or update
• 🔧 Configuration change
• 🏗️ Infrastructure change

Checklist

Please ensure your PR meets the following requirements:

Code Quality

• Code follows the project's TypeScript and code style guidelines
• Code is properly formatted (ran npm run format)
• Code passes linting (ran npm run lint)
• TypeScript compiles without errors (ran npm run type-check)
• No any types used (except for documented third-party library interfaces)
• File size limits respected (max 300 lines per file, 50 lines per function)

Testing

• All existing tests pass (ran npm run test)
• New tests have been added for new features or bug fixes
• Test coverage meets requirements:
  • Business logic: minimum 80% coverage
  • Utility functions: 100% coverage
  • API routes: integration tests added
  • Critical paths: E2E tests added (if applicable)
• Tests follow AAA pattern (Arrange, Act, Assert)

Security & Best Practices

• Authentication checks are in place for protected routes
• Multi-tenant isolation is enforced (storeId filtering)
• Input validation is implemented using Zod schemas
• No secrets or sensitive data in code (using environment variables)
• SQL injection prevention (using Prisma, no raw SQL)
• XSS prevention (proper input sanitization)

Documentation

• Documentation has been updated (if applicable)
• JSDoc comments added for complex functions
• API documentation updated (if API changes were made)
• README.md updated (if needed)
• Specification documents updated (if architectural changes were made)

Database (if applicable)

• Database migration created (if schema changes were made)
• Migration tested on local database
• Seed data updated (if needed)
• Indexes added for new query patterns
• Soft delete pattern followed for user-facing data

Accessibility (if UI changes were made)

• Meets WCAG 2.1 Level AA standards
• Keyboard navigation works properly
• ARIA labels added where necessary
• Color contrast ratios meet requirements (≥ 4.5:1)
• Focus indicators are visible
• Alt text provided for images
• Tested with screen reader (if major UI changes)

Performance (if applicable)

• Page load time within budget (< 2.0s LCP desktop, < 2.5s mobile)
• API response time within budget (< 500ms p95)
• Database queries optimized (no N+1 queries)
• Images optimized (using Next.js Image component)
• Bundle size within limits (< 200KB initial load)

Build & Deployment

• Build succeeds locally (ran npm run build)
• No console errors or warnings
• Environment variables documented (if new ones added)
• Works in both development and production modes

Screenshots (if applicable)

Before

After

Additional Context

Reviewer Notes

---

By submitting this pull request, I confirm that:

• I have read and agree to follow the Code of Conduct
• I have read the Contributing Guidelines
• My contribution is original work or properly attributed
• I agree to license my contribution under the project's MIT License

[Copilot]

Pull Request Overview

This PR updates the MCP (Model Context Protocol) server configuration for shadcn/ui components by changing the package name from @upstash/mcp-server-shadcn to shadcn-mcp-server in .mcp.json. However, the PR description is completely empty, providing no context for why this change was made or what issue it addresses.

Key Changes

• Modified shadcn MCP server package reference in .mcp.json

Comments suppressed due to low confidence (1)

.mcp.json:1

• The PR description is completely empty (only the template is present). According to the project's CONTRIBUTING.md guidelines, all PRs must include a description explaining the 'Why' (the problem being solved) and 'What' (the changes made). Please fill out the PR template with information about why this package name change is necessary and what issue it resolves.

{