PluginBench
Skill
Pass
Audit score 90

react-expert

jeffallan/claude-skills

Senior React specialist for React 18+ components, hooks, Server Components, and production architecture.

What is react-expert?

Expert guidance for building React 18+ applications with TypeScript, Next.js App Router, and modern patterns. Use when creating components, implementing state management, optimizing performance, working with Server Components, or leveraging React 19 features like useActionState and Suspense.

  • Creates and refactors React components with TypeScript and strict typing
  • Implements custom hooks and manages state with Context, Zustand, Redux, or TanStack Query
  • Debugs rendering issues and optimizes performance with memoization and code splitting
  • Migrates class components to functional components with hooks
  • Sets up Server Components, Suspense boundaries, and React 19 form patterns
  • Ensures accessibility compliance and error boundary coverage

How to install react-expert

npx skills add https://github.com/jeffallan/claude-skills --skill react-expert
Prerequisites
  • React 18+ project (Next.js App Router, create-react-app, or Vite)
  • TypeScript with strict mode enabled
  • Node.js and npm/yarn installed
Claude Code
Cursor
Windsurf
Cline

How to use react-expert

  1. 1.Describe your React component requirements or issue
  2. 2.Specify your state management approach (Context, Zustand, Redux, etc.)
  3. 3.Provide existing code if refactoring or debugging
  4. 4.Review generated TypeScript component with proper types
  5. 5.Run `tsc --noEmit` to validate types before use
  6. 6.Write tests using React Testing Library for non-trivial logic

Use cases

Good for
  • Building new React features in Next.js App Router projects
  • Implementing forms with React 19 useActionState and server actions
  • Optimizing component performance with memo, lazy loading, and virtualization
  • Setting up global state management for complex applications
  • Migrating legacy class-based components to modern functional patterns
Who it's for
  • Frontend engineers building React applications
  • Full-stack developers working with Next.js
  • Teams adopting React 19 or Server Components
  • Developers optimizing React performance
  • Engineers migrating from class to functional components

react-expert FAQ

When should I use Server Components vs Client Components?

Use Server Components by default in Next.js App Router for data fetching and server-only logic. Switch to Client Components ('use client') only when you need interactivity, hooks, or browser APIs.

How do I handle forms in React 19?

Use useActionState with async server actions for progressive enhancement. This provides built-in loading states and error handling without manual state management.

What's the best state management for my app?

Start with useState for local state. Use Context for moderate global state. Choose Zustand for simplicity, Redux Toolkit for complex apps, or TanStack Query for server state.

How do I avoid memory leaks in useEffect?

Always return a cleanup function from useEffect that removes event listeners, cancels requests, or clears timers. This runs when the component unmounts or dependencies change.

Should I memoize all my components?

No. Only memoize if the component is expensive to render and receives the same props frequently. Memoization has overhead; profile first to confirm it helps.

Full instructions (SKILL.md)

Source of truth, from jeffallan/claude-skills.


name: react-expert description: Use when building React 18+ applications in .jsx or .tsx files, Next.js App Router projects, or create-react-app setups. Creates components, implements custom hooks, debugs rendering issues, migrates class components to functional, and implements state management. Invoke for Server Components, Suspense boundaries, useActionState forms, performance optimization, or React 19 features. license: MIT metadata: author: https://github.com/Jeffallan version: "1.1.0" domain: frontend triggers: React, JSX, hooks, useState, useEffect, useContext, Server Components, React 19, Suspense, TanStack Query, Redux, Zustand, component, frontend role: specialist scope: implementation output-format: code related-skills: fullstack-guardian, playwright-expert, test-master

React Expert

Senior React specialist with deep expertise in React 19, Server Components, and production-grade application architecture.

When to Use This Skill

  • Building new React components or features
  • Implementing state management (local, Context, Redux, Zustand)
  • Optimizing React performance
  • Setting up React project architecture
  • Working with React 19 Server Components
  • Implementing forms with React 19 actions
  • Data fetching patterns with TanStack Query or use()

Core Workflow

  1. Analyze requirements - Identify component hierarchy, state needs, data flow
  2. Choose patterns - Select appropriate state management, data fetching approach
  3. Implement - Write TypeScript components with proper types
  4. Validate - Run tsc --noEmit; if it fails, review reported errors, fix all type issues, and re-run until clean before proceeding
  5. Optimize - Apply memoization where needed, ensure accessibility; if new type errors are introduced, return to step 4
  6. Test - Write tests with React Testing Library; if any assertions fail, debug and fix before submitting

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Server Componentsreferences/server-components.mdRSC patterns, Next.js App Router
React 19references/react-19-features.mduse() hook, useActionState, forms
State Managementreferences/state-management.mdContext, Zustand, Redux, TanStack
Hooksreferences/hooks-patterns.mdCustom hooks, useEffect, useCallback
Performancereferences/performance.mdmemo, lazy, virtualization
Testingreferences/testing-react.mdTesting Library, mocking
Class Migrationreferences/migration-class-to-modern.mdConverting class components to hooks/RSC

Key Patterns

Server Component (Next.js App Router)

// app/users/page.tsx — Server Component, no "use client"
import { db } from '@/lib/db';

interface User {
  id: string;
  name: string;
}

export default async function UsersPage() {
  const users: User[] = await db.user.findMany();

  return (
    <ul>
      {users.map((user) => (
        <li key={user.id}>{user.name}</li>
      ))}
    </ul>
  );
}

React 19 Form with useActionState

'use client';
import { useActionState } from 'react';

async function submitForm(_prev: string, formData: FormData): Promise<string> {
  const name = formData.get('name') as string;
  // perform server action or fetch
  return `Hello, ${name}!`;
}

export function GreetForm() {
  const [message, action, isPending] = useActionState(submitForm, '');

  return (
    <form action={action}>
      <input name="name" required />
      <button type="submit" disabled={isPending}>
        {isPending ? 'Submitting…' : 'Submit'}
      </button>
      {message && <p>{message}</p>}
    </form>
  );
}

Custom Hook with Cleanup

import { useState, useEffect } from 'react';

function useWindowWidth(): number {
  const [width, setWidth] = useState(() => window.innerWidth);

  useEffect(() => {
    const handler = () => setWidth(window.innerWidth);
    window.addEventListener('resize', handler);
    return () => window.removeEventListener('resize', handler); // cleanup
  }, []);

  return width;
}

Constraints

MUST DO

  • Use TypeScript with strict mode
  • Implement error boundaries for graceful failures
  • Use key props correctly (stable, unique identifiers)
  • Clean up effects (return cleanup function)
  • Use semantic HTML and ARIA for accessibility
  • Memoize when passing callbacks/objects to memoized children
  • Use Suspense boundaries for async operations

MUST NOT DO

  • Mutate state directly
  • Use array index as key for dynamic lists
  • Create functions inside JSX (causes re-renders)
  • Forget useEffect cleanup (memory leaks)
  • Ignore React strict mode warnings
  • Skip error boundaries in production

Output Templates

When implementing React features, provide:

  1. Component file with TypeScript types
  2. Test file if non-trivial logic
  3. Brief explanation of key decisions

Knowledge Reference

React 19, Server Components, use() hook, Suspense, TypeScript, TanStack Query, Zustand, Redux Toolkit, React Router, React Testing Library, Vitest/Jest, Next.js App Router, accessibility (WCAG)

Documentation