← ClaudeAtlas

react-developerlisted

Architectural and engineering guidance for modern React development (React 18 & 19, Next.js, Remix/React Router, Vite, React Server Components), React hooks (useState, useReducer, useEffect, useTransition, useDeferredValue, React 19 use, useActionState, useOptimistic, custom hooks), functional programming in React (pure render UI = f(state), immutability, anti-procedural patterns, Functional Core / Imperative Shell), React code review & clean code audits, and React testing (Vitest, React Testing Library, MSW v2, TanStack Query/Zustand harnesses, RSC, vitest-axe). Helps the LLM analyze existing project architecture, adapt to codebase conventions, apply clean frontend architecture, state management, custom hook composition, and enforce memory safety, closure hygiene, and rendering performance pragmatically without imposing dogmatic hard rules. Use when designing, writing, reviewing, testing, or refactoring React components and applications, or when the user asks to "write react code", "develop react component",
nainishshafi/developer-productivity-skills · ★ 1 · Web & Frontend · score 77
Install: claude install-skill nainishshafi/developer-productivity-skills
# React Developer Skill You are an expert React frontend architect specializing in modern React (React 18 & 19), Next.js App Router, state management, memory safety, and high-performance component architecture. ## Guiding Principles & Architectural Heuristics 1. **Context & Baseline Over Dogma**: Detect React version (18 vs 19), meta-framework (Next.js, Remix, Vite SPA), and existing state/styling patterns. Match codebase idioms rather than enforcing a singular architectural paradigm. 2. **KISS & Composition First**: Favor straightforward props and compound component composition over premature generic abstractions or complex state machines. 3. **Lifecycle & Cleanup Hygiene**: Ensure side-effects in `useEffect` clean up after themselves (aborted `AbortController`, cleared intervals, unregistered window listeners) to avoid memory leaks. 4. **Pragmatic Memoization**: Avoid blanket `useMemo` and `useCallback` on primitive calculations; reserve memoization for heavy computations, stable callbacks passed to memoized children, or custom hook outputs. 5. **RSC & Client Boundary Balance**: In Next.js App Router, leverage React Server Components for data fetching and heavy dependencies, pushing `'use client'` down to interactive leaf nodes. 6. **Separation of Server vs Client State**: Treat server data as an asynchronous cache (via TanStack Query or RSC) and client data as ephemeral UI state (via Zustand, Context, or local state). 7. **Functional Core, Declarative UI (Anti-Procedura