react

Run the review-performance workflow: detect the stack from package.json and next.config, then walk the rule categories in impact order—async waterfalls, bundle, server, client fetching, re-render. Report each finding with a file:line reference, a rule id, and a concrete fix.

The 'use client' directive is contagious downward: every module the file imports becomes client code, opting the entire route out of server rendering. Data fetching moves to the browser and cannot start until the JavaScript downloads and hydrates. Push the directive to the smallest interactive leaf instead.

No. Only Server Components may be async; an async function in a file marked 'use client' fails at runtime. The fix is to await data in a Server Component parent and pass the resolved value to the client child as a serializable prop.

Most rules apply to React 19 and Next.js 15/16 generally, but the make-route-instant workflow and Cache Components guidance require Next.js 16.3+ with cacheComponents enabled. On older versions the skill says so and suggests upgrading via the official codemod.

Run npx shadcn@latest info --json first to read the project's aliases, icon library, and Tailwind version, then npx shadcn@latest docs <component> before writing code. Never recall component APIs from memory, and never choose a registry the user did not name.

It excludes visual and UX design decisions, Vue/Svelte/Astro, React Native and Expo, Pages Router feature work, test-runner and CI configuration, and server-side Node frameworks like Fastify or NestJS. Those belong to other dedicated skills.