THE LITTLE SKILL DEPOT

Best React and Next.js skills for Claude Code in 2026

React is where agents produce the most code and the most subtle mistakes: waterfalls in Server Components, effects that should be derived state, a boolean prop for every variant. The 137 React skills in our index range from Vercel's engineering handbook to one-paragraph reminders. These eight are the ones we would install, with numbers from the 2026-09-03 crawl.

Our picks

  1. #1

    • vercel-react-best-practices

      vercel-labs/agent-skills

      React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

    Why: About 687K installs. Vercel's own performance rules for React and Next.js, split into 76 files the agent reads on demand.

  2. #2

    • vercel-composition-patterns

      vercel-labs/agent-skills

      React Composition Patterns Composition patterns for building flexible, maintainable React components. Avoid boolean prop proliferation by using compound components, lifting state,

      400K installs 33KReact & Next.js

    Why: About 320K installs. Component composition over prop drilling and boolean flags; the companion to the performance skill.

  3. #3

    • emil-design-eng

      emilkowalski/skills

      This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

    Why: About 248K installs. Component polish for React: focus, loading states, animation restraint.

  4. #4

    • vercel-react-view-transitions

      vercel-labs/agent-skills

      Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.

    Why: About 113K installs. The one reference for React's View Transition API that is actually correct.

  5. #5

    • tailwind-design-system

      wshobson/agents

      Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.

    Why: About 62K installs. Tailwind v4 tokens and component library structure.

  6. #6

    • shadcn

      shadcn-ui/ui

      Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

    Why: About 43K installs, 123K stars. The official shadcn skill: adds, fixes and composes components using the CLI.

  7. #7

    • frontend-ui-engineering

      addyosmani/agent-skills

      Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.

      60K installs 108KDesign & UIReact & Next.js

    Why: About 33K installs. Accessible, responsive UI construction from Addy Osmani's collection.

  8. #8

    • Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Server Components.

      32K installs 41KReact & Next.jsData

    Why: About 29K installs. Server Components, streaming and parallel routes in a short, focused file.

A little help from the depot

How we chose

We sorted the React and Next.js tag by installs, dropped anything whose repository was last pushed before July 2026, and read the remaining SKILL.md files. A skill stayed if its advice would still be right on React 19 and Next.js 15 or later, if it says something a senior React engineer would not consider obvious, and if the author is accountable for it, meaning a maintainer of the library or a named engineer with a public track record.

Three of the eight come from vercel-labs/agent-skills. That is the reality of this category: the company that maintains Next.js also writes the most careful skills for it. We balanced with the shadcn team, Emil Kowalski, Addy Osmani and wshobson's larger collection.

1. vercel-react-best-practices (vercel-labs/agent-skills)

What it does: performance rules from Vercel Engineering, organised by impact: eliminate request waterfalls, keep the client bundle small, avoid re-render storms, use the right caching layer. The entry file is 7.3 KB and points to 76 rule files the agent opens only when relevant. About 687K installs, 30.8K stars, updated 2026-08-28, no scripts.

When to use it: writing or reviewing any React or Next.js code. It is the closest thing to a default. The catch: some rules assume deployment on Vercel (edge caching, image optimisation) and will nudge you toward that platform if you are on something else.

npx skills add vercel-labs/agent-skills@vercel-react-best-practices -g -y

2. vercel-composition-patterns (vercel-labs/agent-skills)

What it does: teaches compound components, render-as-children, context scoping and the other ways to avoid a component with eleven boolean props. 14 files, 2.9 KB entry. About 320K installs, updated 2026-08-28.

When to use it: designing a shared component library or refactoring one that grew flags. The catch: in our crawl its frontmatter description is empty, which means the agent has less to match against and may not load it on its own. Invoke it by name when you need it.

npx skills add vercel-labs/agent-skills@vercel-composition-patterns -g -y

3. emil-design-eng (emilkowalski/skills)

What it does: the component-level details a design engineer sweats over: focus visibility, disabled and loading states, optical alignment, when a transition helps and when it is noise. React examples throughout. About 248K installs, 35K stars, updated 2026-08-21, 27 KB.

When to use it: any interactive component. The catch: 27 KB is a long file, and it overlaps with vercel-react-best-practices on nothing, so keep both; but do not add a third opinion on component polish on top.

npx skills add emilkowalski/skills@emil-design-eng -g -y

4. vercel-react-view-transitions (vercel-labs/agent-skills)

What it does: a correct guide to the ViewTransition component, addTransitionType and the CSS side of view transitions in React. About 113K installs, 9 files, 14.4 KB, updated 2026-08-28.

When to use it: page and list transitions in an App Router project. The catch: the API is still marked experimental in React, so pin your React version and reread the skill when you upgrade; an agent following last quarter's guidance can ship a deprecated call.

npx skills add vercel-labs/agent-skills@vercel-react-view-transitions -y

5. tailwind-design-system and 8. nextjs-app-router-patterns (wshobson/agents)

tailwind-design-system covers Tailwind v4 design tokens, component variants and responsive conventions in 5.3 KB. About 62K installs, updated 2026-09-01. Use it when starting a component library on Tailwind. The catch: it is a summary, not a spec; for shadcn projects the shadcn skill below is more specific.

nextjs-app-router-patterns is 3.7 KB on Server Components, streaming, parallel and intercepting routes and data fetching. About 29K installs. Use it when the agent keeps adding "use client" to everything. The catch: the description says Next.js 14+, and it does not mention the newer caching directives, so pair it with the Vercel skill rather than relying on it alone.

npx skills add wshobson/agents@nextjs-app-router-patterns -y

6. shadcn (shadcn-ui/ui)

What it does: the official skill from the shadcn repository. It teaches the agent to add and search components with the CLI, fix broken installs, style with the token system and compose larger patterns like chat interfaces. About 43K installs, 123K stars, 15 files, 19.5 KB, updated 2026-09-03.

When to use it: any project on shadcn/ui. The catch: the install count is modest because the skill is recent, while the 123K stars belong to the whole library; judge it by the author, not the numbers. It also assumes the shadcn CLI is available in the project.

npx skills add shadcn-ui/ui@shadcn -y

7. frontend-ui-engineering (addyosmani/agent-skills)

What it does: a construction checklist for accessible, responsive interfaces: semantic HTML first, keyboard paths, layout that survives long text and small screens. About 33K installs, 92K stars, 10.7 KB, updated 2026-09-03.

When to use it: when accessibility is a requirement, not a nice-to-have. The catch: it is framework-neutral, so it will not tell you how to do any of this in React specifically; it sets the bar and the Vercel skills supply the mechanics.

npx skills add addyosmani/agent-skills@frontend-ui-engineering -g -y

What we excluded and why

vercel-react-native-skills (about 202K installs) is React Native, which deserves its own list. web-artifacts-builder from Anthropic (about 98K) builds claude.ai artifacts, not apps, and ships scripts. vercel-optimize (about 64K) has 156 files and scripts and needs a Vercel account to read metrics. minimalist-ui is a design preset our tagger caught on the word "grid". ask-sonner and animate from Emil's repository are good but narrow; they belong on the animation list.

A working set

Globally: vercel-react-best-practices, vercel-composition-patterns and emil-design-eng. Per project: shadcn if you use it, view-transitions if you animate routes, nextjs-app-router-patterns for a team new to the App Router. That is under 60 KB of instructions in total, and none of it loads until a request touches React.

npx skills add vercel-labs/agent-skills@vercel-react-best-practices -g -y
npx skills add vercel-labs/agent-skills@vercel-composition-patterns -g -y
npx skills add emilkowalski/skills@emil-design-eng -g -y

Frequently asked questions

Do I still need these if I already have a CLAUDE.md with React rules?

A CLAUDE.md is read every turn; a skill is read only when the task matches. Move the long, situational rules into skills and keep CLAUDE.md for the handful that always apply.

Will the Vercel skills push me toward Vercel hosting?

A few rules mention Vercel-specific caching and image handling. On another host, tell the agent where you deploy; the rest of the advice is plain React.

Do these work in Cursor and Codex?

Yes. All eight are Markdown-only skills. Use --agent cursor or --agent codex on the install command.

What about Vue, Svelte or Solid?

This list is React only. antfu/skills has Vue and Vitest skills; search the directory for the framework name.

Content last reviewed: