The .cursorrules I'd Actually Use for a Next.js E-Commerce Project

Most .cursorrules files are generic. "Use TypeScript." "Prefer functional components." "Write clean code." That's fine for a tutorial project. But when you're building something real, like an e-commerce app with payments, inventory, and SEO requirements, Cursor still doesn't know about Stripe webhook verification, cart race conditions, or product page metadata. I put together a .cursorrules file specifically for Next.js e-commerce projects. Key rules were tested with Cursor CLI to confirm they actually change the output. The rest are documented best practices that solve real e-commerce problems. Rule 1: Server Components for Product Pages The problem: Cursor puts 'use client' on everything. Product pages don't need it. They're read-heavy, SEO-critical, and benefit from server rendering. The rule: When building e-commerce product pages, category pages, or search results: - Default to React Server Components - Only use 'use client' for interactive elements: cart buttons, quantity selecto