- Home
- Skills
- Vudovn
- Antigravity Kit
- Nextjs React Expert
nextjs-react-expert_skill
- TypeScript
5.7k
GitHub Stars
9
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill vudovn/antigravity-kit --skill nextjs-react-expert- 1-async-eliminating-waterfalls.md7.6 KB
- 2-bundle-bundle-size-optimization.md6.1 KB
- 3-server-server-side-performance.md12.6 KB
- 4-client-client-side-data-fetching.md6.7 KB
- 5-rerender-re-render-optimization.md15.5 KB
- 6-rendering-rendering-performance.md10.1 KB
- 7-js-javascript-performance.md17.0 KB
- 8-advanced-advanced-patterns.md3.6 KB
- SKILL.md9.6 KB
Overview
This skill provides React and Next.js performance optimization guidance distilled from Vercel Engineering. It prioritizes fixes by impact and offers 57 concrete rules across eight categories to eliminate waterfalls, reduce bundle size, and improve server- and client-side performance. Use it as a checklist and decision tree during development, reviews, and debugging.
How this skill works
The skill inspects common performance bottlenecks and recommends prioritized actions: eliminate sequential data fetching, optimize bundles, and then refine server/client rendering and JavaScript hot paths. It surfaces a quick decision tree, a validation checklist, and targeted rules for critical areas like waterfalls and bundle trimming, plus practical anti-patterns to avoid. Follow the impact-priority guide to apply fixes in the order that yields the largest gains.
When to use it
- Building new pages or features and wanting to prevent regressions
- Conducting a performance review before shipping to production
- Debugging slow page loads, long TTI, or LCP issues
- Reducing large bundle sizes or eliminating unnecessary code shipping
- Addressing server-side slowness or SSR waterfalls
Best practices
- Measure first with DevTools and React Profiler before changing code
- Fix CRITICAL items first: eliminate waterfalls and reduce main bundle size
- Fetch independent resources in parallel (Promise.all) and use Suspense boundaries
- Prefer server components when appropriate to reduce client JS
- Use dynamic imports for large components and avoid barrel exports in app code
Example use cases
- Performance review: run checklist to find waterfall API calls and large imports
- Feature implementation: keep main bundle under 200KB and use dynamic imports for heavy libs
- SSR optimization: parallelize server fetches and add streaming or Suspense boundaries
- UI lag fix: apply memoization, useMemo/useCallback, and virtualize long lists
- Client data fetching: enable SWR deduplication and cache frequently used responses
FAQ
Start with eliminating waterfalls and then reduce bundle size; these yield the largest improvements.
Is memoization always necessary?
No. Measure to identify hot paths; memoize expensive computations or frequently re-rendered components only when it provides measurable benefit.