// may the 4th be with you⚔️
tag

react

127 indexed skills · max 10 per page

skills (127)

react-expert

jeffallan/claude-skills · Frontend

1

Expert React 18+ and React 19 component development with Server Components, hooks, and state management. \n \n Covers React 19 features including use() hook, useActionState forms, and Server Components in Next.js App Router \n Implements custom hooks, state management patterns (Context, Zustand, Redux), and data fetching with TanStack Query \n Enforces TypeScript strict mode, error boundaries, proper cleanup, and accessibility standards throughout \n Includes performance optimization via memoiza

react-hook-form-zod

jezweb/claude-skills · Frontend

1

Type-safe validated forms with React Hook Form v7 and Zod v4, single schema for client and server. \n \n Combines uncontrolled registration with Zod schema validation and full TypeScript inference via z.infer ; supports dynamic fields, multi-step wizards, and conditional validation patterns \n Includes resolver setup, error handling, useFieldArray for dynamic lists, and Controller integration for third-party components \n Documents 20 known issues and workarounds, including large-form performanc

react-patterns

davila7/claude-code-templates · Frontend

1

Principles for building production-ready React applications.

react-native-app

aj-geddes/useful-ai-prompts · Frontend

1

Create robust cross-platform mobile applications using React Native with modern development patterns including navigation, state management, API integration, and native module handling.

vite-react-best-practices

claudiocebpaz/vite-react-best-practices · Frontend

1

A senior-level guide for building production-ready React Single Page Applications (SPAs) with Vite.

react-best-practices

vercel-labs/vercel-plugin · Frontend

1

Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Contains 64 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.

react-native-expert

jeffallan/claude-skills · Frontend

1

Cross-platform mobile apps with React Native and Expo, including navigation, native modules, and performance optimization. \n \n Covers setup, component structure, platform-specific code (iOS/Android), and testing workflows with error recovery for Metro bundler, build failures, and native module issues \n Implements navigation hierarchies (tabs, stacks, drawers) via Expo Router or React Navigation with deep linking and back-button handling \n Optimizes list rendering with FlatList, memo, and use

react-native-testing

callstack/react-native-testing-library · Frontend

1

Write and review React Native component tests using Testing Library v13 and v14. \n \n Covers render patterns, screen queries (getBy/getAllBy/queryBy/findBy variants), Jest matchers, userEvent interactions, fireEvent, and async patterns with version-specific behavior \n Automatically detects your project's RNTL version (v13 for React 18, v14 for React 19+) and applies correct API signatures and sync/async rules \n Provides query priority guidance (getByRole first), interaction best practices (us

react-performance-optimization

nickcrew/claude-ctx-plugin · Frontend

1

Memoization, code splitting, and virtualization patterns for optimizing React application performance. \n \n Covers four core optimization techniques: memoization (React.memo, useMemo, useCallback), code splitting with lazy/Suspense, virtualization for large lists, and state management strategies to minimize render cascades \n Includes React 18+ concurrent features (useTransition, useDeferredValue) for improved responsiveness and perceived performance \n Provides profiling workflow using React D

react-best-practices

0xbigboss/claude-code · Frontend

1

React patterns for hooks, effects, refs, and component design with escape hatch guidance. \n \n Effects synchronize with external systems only (WebSocket, third-party libraries, browser APIs); most component logic should avoid Effects entirely \n Common anti-patterns: derived state, expensive calculations, prop-change resets, and event handling all belong outside Effects—use render calculations, useMemo, key props, and event handlers instead \n Effect dependencies must never be suppressed; use u

prevpage 2 / 13next