react-nextjs
Vercel React Best Practices
Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Contains 45 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.
When to Apply
Reference these guidelines when:
- Writing new React components or Next.js pages
- Implementing data fetching (client or server-side)
- Reviewing code for performance issues
- Refactoring existing React/Next.js code
- Optimizing bundle size or load times
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Eliminating Waterfalls | CRITICAL | async- |
More from kienhaminh/anti-chaotic
business-analysis
Use for deep requirements analysis, technical specifications, agile documentation, or architecture/design reviews.
77qa-tester
Use when planning tests, creating test cases, reporting bugs, or executing Unit/E2E/Security/Performance tests.
26backend-developer
Use when designing APIs, Architecture, Security, or Scalability for Node, Python, Go, or Java backend systems.
21lead-architect
Use for high-stakes technical decisions, system design (Microservices/Monolith), cloud infrastructure, or generating ADRs/RFCs.
11frontend-developer
Use when implementing frontend code, optimizing performance, or ensuring strict adherence to documentation/references.
11blockchain-engineer
Use when architecturalizing protocols, developing smart contracts, or auditing security for blockchain systems.
11